Wasp not found after installing Wasp
I'm trying to start with the Open-SaaS but for some reason after I do "curl -sSL https://get.wasp.sh/installer.sh | sh" on WSL and then I type "wasp version" it then says "wasp: command not found".
What I'm I doing wrong here?
4 Replies
Hi @CYA Security. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
The issue you're experiencing—where Wasp is not found after installation—is likely because the directory where Wasp is installed (usually
~/.local/bin) is not included in your system's PATH environment variable. This means your terminal doesn't know where to look for the wasp executable.
To fix this, you need to add ~/.local/bin to your PATH. Here’s how you can do it:
1. Open your shell configuration file:
- For Bash: ~/.bashrc or ~/.bash_profile
- For Zsh: ~/.zshrc
2. Add this line at the end of the file:
3. Save the file and reload your shell configuration:
- For Bash: source ~/.bashrc or source ~/.bash_profile
- For Zsh: source ~/.zshrc
After doing this, try running wasp version again. It should now work as expected.
This is a common issue on Linux systems, and the solution is confirmed by the Wasp community and documentation Quick Start Installation and Discord support thread.
If you still encounter issues, make sure you installed Wasp using the correct script for Wasp (<https://get.wasp-lang.dev/installer.sh>), as the URL you mentioned (<https://get.wasp.sh/installer.sh>) does not match the official one. Use:
and then follow the steps above to update your PATH if needed.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @CYA Security, 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?Hey @CYA Security did you get it to work?
If you did install it successfully most likely it's PATH issues.
Adding it to PATH and then loading the shell should make it work, as said by bot above.
No I did not, yet
I put the correct path but still…
We have a whole blog post about it, it might help: https://wasp.sh/blog/2023/11/21/guide-windows-development-wasp-wsl
Are you sure you're running your command in the WSL? And that you edited
~/.profile?A Guide to Windows Development with Wasp & WSL | Wasp
<ImgWithCaption