Error: spawnSync /Users/venkatesh/wasp/freelander/app/node_modules/vitest/node_modules/esbuild/bin/e
Hi,
I am on MacOS 14.4.1 (23E224), I get the above error when i try to run wasp db migrate-dev
Full error below:
[ Wasp !] npm error code 1
[ Wasp !] npm error path /Users/venkatesh/wasp/freelander/app/node_modules/vitest/node_modules/esbuild
[ Wasp !] npm error command failed
[ Wasp !] npm error command sh -c node install.js
[ Wasp !] npm error node:internal/child_process:1124
[ Wasp !] npm error result.error = new ErrnoException(result.error, 'spawnSync ' + options.file);
[ Wasp !] npm error ^
[ Wasp !] npm error
[ Wasp !] npm error <ref *1> Error: spawnSync /Users/user/wasp/freelander/app/node_modules/vitest/node_modules/esbuild/bin/esbuild Unknown system error -88
[ Wasp !] npm error at Object.spawnSync (node:internal/child_process:1124:20)
[ Wasp !] npm error at spawnSync (node:child_process:875:24)
[ Wasp !] npm error at Object.execFileSync (node:child_process:918:15)
[ Wasp !] npm error at validateBinaryVersion (/Users/user/wasp/freelander/app/node_modules/vitest/node_modules/esbuild/install.js:99:28)
[ Wasp !] npm error at /Users/venkatesh/wasp/freelander/app/node_modules/vitest/node_modules/esbuild/install.js:286:5 {
[ Wasp !] npm error errno: -88,
[ Wasp !] npm error code: 'Unknown system error -88',
[ Wasp !] npm error syscall: 'spawnSync /Users/user/wasp/freelander/app/node_modules/vitest/node_modules/esbuild/bin/esbuild',
[ Wasp !] npm error path: '/Users/user/wasp/freelander/app/node_modules/vitest/node_modules/esbuild/bin/esbuild',
[ Wasp !] npm error spawnargs: [ '--version' ],
4 Replies
Hi @amzu-superadmin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. The knowledge sources provided do not contain information about the specific error you're encountering with
esbuild and vitest when running wasp db migrate-dev.
However, it's worth noting that some users have resolved similar issues by running wasp clean before wasp db migrate-dev as suggested in this Discord thread (https://discord.com/channels/686873244791210014/1221144773834964992).
For more specific guidance, I recommend checking the Wasp documentation (https://wasp-lang.dev/docs/quick-start#requirements) or reaching out to the Wasp community directly.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @amzu-superadmin, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?yes
wasp clean helped to fix this issue.
Did you copy paste the whole project or modify the
node_modules in any way prior to this error? 🙂whole project, i didnt modify the node_modules, just did a wasp clean and it went away