Open richb-hanover opened 1 week ago
Interesting, I haven't seen this before. Does the full log at /home/vscode/.npm/_logs/2024-10-19T22_57_39_755Z-debug-0.log
have anything interesting?
Does running whatever inner command is run based on spawnargs: [ 'build', '--target', 'nodejs', '--out-dir', 'dist/node', '--dev' ]
show anything?
Here's where it stops:
(Again, I apologize that I don't know much about the node compilation environment for prqlc. I'm happy to provide more info as needed...)
vscode ➜ .../prql/prqlc/bindings/js (freeze-at-86becc59) $ cd /workspaces/prql/prqlc/bindings/js
vscode ➜ .../prql/prqlc/bindings/js (freeze-at-86becc59) $ npm run build:node
> prqlc@0.13.3 build:node
> npx cross-env wasm-pack build --target nodejs --out-dir dist/node --${PROFILE} && rm dist/node/.gitignore
node:events:497
throw er; // Unhandled 'error' event
^
Error: spawn wasm-pack ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess._handle.onexit (node:internal/child_process:292:12)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn wasm-pack',
path: 'wasm-pack',
spawnargs: [ 'build', '--target', 'nodejs', '--out-dir', 'dist/node', '--' ]
}
Node.js v20.18.0
vscode ➜ .../prql/prqlc/bindings/js (freeze-at-86becc59) $
What happened?
Attempting to build Playground on M2 Mac in the Dev Container. Commit is 86becc59
When I run
task web:run-playground
I see the error below.What other diagnostic info could I provide? Thanks.
PRQL input
SQL output
Expected SQL output
MVCE confirmation
Anything else?