Running "wasp deploy" returns odd error
- 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
oh you are using
wasp-cli
instead of wasp
?
is that intentional?yes
from
cabal install --overwrite-policy=always
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
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)ouuh! my bad. sorry. I should've read that first. thx! i'll try again
np 👍
thanks! it works now. running the script and then
cabal run wasp-cli deploy --cabal-file=../waspc.cabal
works well.Wohooo @Deleted User, you just became a Waspeteer level 2!
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.