Wasp•2y ago

Running "wasp deploy" returns odd error

$ ~/workspace/wasp/apple  wasp-cli new banana

:bee: --- Creating your project from the basic template... ---------------------------

Created new Wasp app in ./banana directory!
To run it, do:

    cd banana
    wasp start
 $  ~/workspace/wasp/apple  cd banana/
 $  ~/workspace/wasp/apple/banana  wasp-cli deploy
wasp-cli: npm: streamingProcess: chdir: invalid argument (Bad file descriptor)
 $  ~/workspace/wasp/apple/banana

$ ~/workspace/wasp/apple  wasp-cli new banana

:bee: --- Creating your project from the basic template... ---------------------------

Created new Wasp app in ./banana directory!
To run it, do:

    cd banana
    wasp start
 $  ~/workspace/wasp/apple  cd banana/
 $  ~/workspace/wasp/apple/banana  wasp-cli deploy
wasp-cli: npm: streamingProcess: chdir: invalid argument (Bad file descriptor)
 $  ~/workspace/wasp/apple/banana

- Locally built from Wasp's latest main branch. Hi, I'm testing out wasp deploy command out of curiosity. As shown above, I got an odd error. What did I do wrong and do I need to do an extra setup? At the very least, I expect for descriptive error from running wasp deploy.

9 Replies

shayne•2y ago

oh you are using wasp-cli instead of wasp? is that intentional?

Deleted UserOP•2y ago

yes from cabal install --overwrite-policy=always

shayne•2y ago

then check this out: https://github.com/wasp-lang/wasp/tree/main/waspc#typescript-packages

GitHub

wasp/waspc at main · wasp-lang/wasp

The fastest way to develop full-stack web apps with React & Node.js. - wasp/waspc at main · wasp-lang/wasp

shayne•2y ago

to run deploy via wasp-cli you first need to run ./tools/install_deploy_package_to_data_dir.sh that is the directory it thinks is missing (the tsc output that would normally be there for wasp but is not in your local dev setup)

Deleted UserOP•2y ago

ouuh! my bad. sorry. I should've read that first. thx! i'll try again

shayne•2y ago

np 👍

Deleted UserOP•2y ago

thanks! it works now. running the script and then cabal run wasp-cli deploy --cabal-file=../waspc.cabal works well.

MEE6•2y ago

Wohooo @Deleted User, you just became a Waspeteer level 2!

martinsos•2y ago

No worries, Wasp is a bit peculiar here as it uses Typescript for deploy scripts. So it requires an extra step during development which is easy to miss. I wonder if we could somehow add an error message in the codebase for this very specific situation, to help developer easily figure out what they forgot? Not sure hm. We could catch the situation when they never installed deploy packages to data dir, but much harder to detect when they did it before but not after updating typescript code.

Gaming

Programming

Running "wasp deploy" returns odd error

Did you find this page helpful?