When i'm running this line - wasp db-migrate dev, Im getting this error
🐝 --- Compiling wasp project... --------------------------------------------------
wasp: /home/runner/.cabal/share/x86_64-linux-ghc-8.10.7/waspc-0.14.0/Generator/templates/react-app/README.md: openBinaryFile: does not exist (No such file or directory)
4 Replies
Hi @Mitu. 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 provided, it seems like you're encountering an issue where the Wasp compiler is unable to find a specific file (
README.md) in the react-app template directory. This could be due to a variety of reasons, such as the file not existing, the file being in a different location, or issues with file permissions.
Here are a few steps you can try to resolve this issue:
1. Verify that the README.md file exists in the specified directory. If it doesn't, you might need to create it or copy it from another location.
2. Check the file permissions of the README.md file. Make sure that the user running the wasp db-migrate dev command has read access to the file.
3. Try running wasp clean before running the wasp db-migrate dev command. This command cleans the .wasp directory which might help if there are any issues related to stale or corrupted files (source (https://discord.com/channels/686873244791210014/1221144773834964992)).
4. If you're running this in a non-interactive environment (like a CI/CD pipeline), you might encounter issues with the prisma migrate dev command, which wasp db-migrate dev relies on. In such cases, you might need to use a workaround to simulate an interactive environment (source (https://github.com/wasp-lang/wasp/issues/229)).
If none of these steps resolve your issue, I would recommend reaching out to the Wasp community or opening an issue on the Wasp GitHub repository for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Mitu, 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?nothing helped
Can you share more details (the commands you're running, your system, your wasp version, etc.)?
This looks like the install of the Wasp CLI didn't go through as expected. What do you see in the terminal when you run:
curl -sSL https://get.wasp-lang.dev/installer.sh | sh