wasp: Fix error during `wasp start` after `wasp start` and failing `wasp build`

Version: 0.13.2. (probably post-0.12.0 and caused by https://github.com/wasp-lang/wasp/issues/1769#issuecomment-1952938100, doesn’t happen with 0.11.8). OS: Linux

How to reproduce:

  1. Run wasp new something && cd something.
  2. Run wasp start and wait for it to finish.
  3. Run wasp build and see it fail because of an inappropriate database (SQLLite).
  4. Run wasp start again and see the error.

Here’s how it looks in action:

$ wasp start

🐝 --- Starting compilation and setup phase. Hold tight... ------------------------


🐝 --- Compiling wasp project... --------------------------------------------------


✅ --- Successfully completed npm install. ----------------------------------------


🐝 --- Setting up database... -----------------------------------------------------


✅ --- Database successfully set up. ----------------------------------------------


🐝 --- Building SDK... ------------------------------------------------------------

wasp-bin: npx: streamingProcess: chdir: invalid argument (Bad file descriptor)

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Comments: 19 (9 by maintainers)

Most upvoted comments

Hey @Rotemoyal, thanks for letting us know!

It’s not ideal, but you should be able to fix it by running wasp clean after any command throws this error, and then rerunning the command.

wasp clean won’t delete anything important, it only cleans up the build artifacts, so no worries.

Hey @Rotemoyal, thanks for letting us know!

It’s not ideal, but you should be able to fix it by running wasp clean after any command throws this error, and then rerunning the command.

wasp clean won’t delete anything important, it only cleans up the build artifacts, so no worries.

This solved my issue, thanks. I ran this command first wasp clean . Then I ran wasp start

Had the same issue with Ubuntu 24.04 and node 18. For me it helped to upgrade node to 20 and doing a fresh wasp new.

maybe it worth checking if npm exists so the error message will be indicative?

Definitely! I just made a new issue to track it: https://github.com/wasp-lang/wasp/issues/2113

Thanks for letting us know 😃