Actions.ts doesn't have hot reload?
My actions file isn't reloading. The frontend stuff reloads but my actions file doesn't when I make a change, and I have to manually restart server.
KHi @Don Bugito. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
K----------------------
Hot reloading should work with Wasp, including for the
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Hot reloading should work with Wasp, including for the
actions.ts file. However, there are a few things that could potentially cause issues:- If you're using WSL2 and your project is on the Windows file system, hot reloading won't work due to an issue with WSL2. The recommended solution is to move your project to the Linux file system. source (https://github.com/wasp-lang/wasp/issues/603)
- Make sure you're running
in your project directory. If you're not seeing any output about new changes in the terminal where you ranwasp start
, or if the webpage isn't updating, there might be an issue. source (🙋questionsHot Reloading?)wasp start - If you're still having issues, it might be helpful to check for any errors in your terminal or in your browser's developer console. source (🙋questionsHot Reloading?)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
KSorry @Don Bugito, 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?
Perhaps try again in 15mins?
MDid anything Kapa mentioned help? 
Dno
MYou'll need to give a bit more info so we can help you 
what is your OS? What did you try?
what is your OS? What did you try?
MAre you on WSL on Windows? If so then your files must be on Linux fielsystem, not windows, that is a WSL bug. Other than that, do you see any errors in the terminal?
NI had a similar issue. Close the IDE, and do a wasp clean. That seems to fix it. I think it is some nodemon or node cache issue.
MDo you see any errors in the terminal before do your fix?
NNo, it just was showing an older version of the code persistently.
NOn the terminal output I mean, my vscode was updated to my latest changes (obviously) but the terminal output was showing the older output with the older code.
MOk, next time it happens, please copy the terminal output here and we'll see what is going on 
