Why is my project not recompiling after file change?
Why is my project not recompiling after file change?
5 Replies
Hi @lazi. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
There are a few potential reasons why your Wasp project might not be recompiling after file changes. Based on the provided knowledge sources, here are the most likely explanations:
1. WSL2 on Windows filesystem: If you're using WSL2 and your project files are stored on the Windows filesystem (e.g., in
/mnt/c/), file change detection may not work properly. This is a known issue with WSL2, not specific to Wasp.
Solution: Move your project files to the Linux filesystem within WSL2. This should enable proper file change detection and hot reloading.
GitHub Issue: File changes not detected by wasp start in WSL2
2. Rapid file changes: If multiple files are changing very quickly (e.g., during automated refactoring), Wasp might not be able to keep up with the changes.
Solution: Wasp developers have considered introducing a delay for recompilation to address this issue, but it's not clear if this has been implemented yet.
GitHub Issue: Introduce a delay for recompilation
3. Incorrect file location: Ensure that you're modifying files in the correct locations. Changes to .wasp files and files in the ext/ directory should trigger recompilation.
If none of these solutions work, you may want to check for any error messages in the terminal where you're running wasp start or in your browser's developer console. These could provide additional clues about why recompilation isn't occurring.
If you're still experiencing issues, it might be helpful to share more details about your specific setup, including your Wasp version, operating system, and any error messages you're seeing.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @lazi, 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?Thanks, I think it is the 1st GitHub Issue presented - I'm on WSL2
Oh idk if that's the problem, i am using wsl2 and change things constantly and it recompiles
sometimes quitting the wasp dev server and restarting your app fixes things. also
wasp clean may help if not. did you get it working @lazi ?I actually didn't but also didn't really investigate any further - I might today! It's deff a problem on my end with the environment I have set-up in Cursor/WSL