Failure to deploy client with Wasp CLI
I'm trying to deploy my app via the Wasp CLI (
wasp deploy fly launch my-wasp-app mia), but the client always fails (see attached image). Only the server and db deploy successfully to Fly.io.
It looks like someone made a PR with the same issue: https://github.com/wasp-lang/open-saas/issues/77GitHub
Client build failing · Issue #77 · wasp-lang/open-saas
NOTE: If there is any template for issues please point me and happy to format the issue. Descrption Unable to build the "client/web app". Error or console log Environment OS : Mac OS 13.6...
8 Replies
Oh this is interesting, thanks for reporting it @manaphy !
@Vinny (@Wasp) @Filip @miho what do you think, what could be the cause of this?
Hey @manaphy, I'm investigating. I'll get back to you in a bit
Successfully reproduced the error. I think I know what's going on.
I'll publish the fix as soon as possible and continue the discussion both here and in the issue.
The new version of Wasp (0.12.4) that fixes this issue is now released. You can install it (as always) with:
@manaphy Let me know if that fixes your problem
Thanks guys! That worked 🙂
You're welcome!
Glad we could help 😀
The one-command hosting is something new I've never tried before, it's very cool
Question: I applied wasp previosuly but now its saying wasp isnt a command although i installed it all over again. Here is the error I recieve: Command 'wasp' not found, did you mean:
command 'asp' from deb asp (1.8-8build1)
command 'wash' from deb reaver (1.6.5-1)
command 'warp' from deb libghc-wai-app-static-dev (3.1.7.1-1build5.1)
command 'wamp' from deb python3-autobahn (21.11.1+dfsg1-2build1)
Try: sudo apt install <deb name>
Let me check the knowledge base for you. One moment! :books:
----------------------
It seems like the
wasp command is not recognized because the directory where the wasp binary is located is not included in your system's PATH environment variable.
To resolve this error, you can add the directory to your PATH. Here's how you can do it:
1. Open your shell configuration file:
- For Bash shell: Open ~/.bashrc or ~/.bash_profile
- For Zsh shell: Open ~/.zshrc
2. Add the following line at the end of the file:
This line adds the .local/bin directory located in your home directory to the beginning of the PATH variable.
3. Save the changes and close the file.
4. Reload the shell configuration by running the following command in your terminal:
- For Bash shell: source ~/.bashrc or source ~/.bash_profile
- For Zsh shell: source ~/.zshrc
After following these steps, the .local/bin directory should be added to your PATH, and you should be able to run the wasp command without encountering the "not on your PATH" error.
For more details, you can refer to this Discord support thread (https://discord.com/channels/686873244791210014/1214888257595121684).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @miho, 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?Yup, this answer from the bot is quite correct!
Can you try restarting your terminal?
What does your PATH look like?
What if you do
whereis wasp?
What was the output of wasp installation? You can just run the installation again to see what the output is, it won't hurt.