Showing no such file or directory when I do wasp db migrate-dev
I copied my folder to WSL, and then opened that folder in WSL, and ran the command
21 Replies
Hi @|•°•|. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources, it seems like you might be encountering an issue with the path of your project directory. If your project directory's path contains white spaces, the
wasp db migrate-dev command might fail because it breaks on that white space. This issue was reported in a Github issue (https://github.com/wasp-lang/wasp/issues/1486) where the Wasp CLI command was not handling white spaces in the path while running the app.
To resolve this issue, you could try moving your project to a directory path that does not contain white spaces.
If the issue persists, it might be helpful to check if you have the necessary permissions set up properly, especially if you're using Docker. You can follow this Docker guide (https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) to manage Docker as a non-root user.
If you're using WSL, you might find this guide (https://wasp-lang.dev/blog/2023/11/21/guide-windows-development-wasp-wsl) helpful. It provides step-by-step instructions for developing with Wasp on Windows using WSL.
Remember to always run the wasp db migrate-dev command from the correct project directory.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @|•°•|, 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 @|•°•|, did you follow the guide the bot linked? https://wasp-lang.dev/blog/2023/11/21/guide-windows-development-wasp-wsl
I had referred to that link before I posted here, yet it didn't happen
For context, I am building that websockets-react & wasp voting
@kapa.ai What do you know about the
wasp-bin: no such file or directory error when using WSL?Let me check the knowledge base for you. One moment! :books:
----------------------
The
wasp-bin: no such file or directory error might occur due to a few reasons:
1. File changes not detected by wasp start in WSL2 when using the Windows filesystem: This is a known issue with WSL2 where wasp start does not automatically recompile and hot-reload the web page when making changes if the project is on a Windows file system. The recommended solution is to keep your source files of your Wasp project on the Linux file system, not the Windows file system. This issue has been documented in a Github issue (https://github.com/wasp-lang/wasp/issues/603).
2. Temporary files causing crashes: In some cases, certain editors like Webstorm or other IntelliJ editors create a temporary file on edit that wasp start picks up and then crashes when the buffer is saved. This issue was reported in a Github issue (https://github.com/wasp-lang/wasp/issues/187) and has been fixed.
3. Whitespace in the project directory path: If your project directory's path contains white spaces, the Wasp CLI command might fail because it breaks on that white space. This issue was reported in a Github issue (https://github.com/wasp-lang/wasp/issues/1486).
If you're encountering this error, ensure that your project files are on the Linux file system if you're using WSL2, avoid having white spaces in your project directory path, and ensure that your editor isn't creating temporary files that could interfere with wasp start.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @sodic, 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?Ok, that's definitely not right 😄
I don't have a windows system to test this out. @martinsos Does the error look familiar to you?
@Boris is also a great guy to ask about Windows related stuff
I'll verify if 0.13.2 works on my Windows machine and if it does, I'll suggest couple of steps to try out (IIRC it does normally, but I will verify soon)
check if you actually have wasp-bin at that location, then we can check the other things
@|•°•| another thing we can try: run
curl -sSL https://get.wasp-lang.dev/installer.sh | sh in your WSL again. This should (re)install Wasp on your system. It will also tell you where it installed wasp -> please copy those paths and paste them here, so we can confirm where it got installed. Finally, make sure to follow the instructions for adding wasp to PATH. Then we can see from here.I will do both of them once I reach home
Sorry for making you guys wait tho
@Boris, only data is present
my .profile file
Wohooo @|•°•|, you just became a Waspeteer level 1!
@kapa.ai why is there no wasp-bin file in WSl ~/.local/share/wasp-lang/0.13.2
Let me check the knowledge base for you. One moment! :books:
----------------------
The
wasp-bin file is the binary executable for the Wasp language. When you install Wasp, the installer script downloads the appropriate version of this binary and places it in the ~/.local/share/wasp-lang/<version>/ directory.
The wasp-bin file is the actual program that gets executed when you run wasp commands in your terminal. It's responsible for interpreting your Wasp code and executing the corresponding actions.
If you're seeing the wasp-bin file in the ~/.local/share/wasp-lang/0.13.2 directory, it means you have version 0.13.2 of Wasp installed on your system. If you want to switch to a different version, you can use the installer script with the -v option followed by the version number, as described in this Github issue (https://github.com/wasp-lang/wasp/issues/616). For example, to switch to version 1.2.3, you would run:
This will download version 1.2.3 of wasp-bin (if it's not already downloaded) and configure your system to use it when you run wasp commands.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @|•°•|, 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?I think that you have to reinstall the Wasp fully, delete the whole folder and try again. I am pretty sure that that is the issue
I did reinstall, but I couldn't delete the previous folder, so I just renamed it to 'folder', and then installed
It works
However, now there are now issues like '"dependencies" is an unexpected field', 'no package.json'
Hm you really have some weird stuff happening there!
When does it throw that error? Can you say which steps you did to get that error, and paste the exact error message + some output around it?