Hot Reloading?
Hi everyone, does Wasp come with hot reloading? I generated a templated SaaS app and hot reloading doesn't seem to be working like a create-react-app does. I'm hoping that I don't need to kill the app and rerun 'wasp start' every time I make changes to preview them. Can this be achieved somehow? I can't find anything in the docs about it. Thanks!
14 Replies
Is this working for everyone else and I've broken something, or is it not a feature of WASP?
it should reload after every change
are you seeing any errors in your terminal where you ran
wasp start? what about in your brower's developer console? if so, please share them 🙂@Vinny (@Wasp) As someone experiencing a similar issue, this is the only error that I see on DevTools:
Warning: Each child in a list should have a unique "key" prop.
Check the render method of LandingPage. See https://reactjs.org/link/warning-keys for more information.
at figure
at LandingPage (http://localhost:3000/@fs/mnt/c/Users/User/Downloads/pick-a-layout/app/src/client/landing-page/LandingPage.tsx:34:47)
at Route2 (http://localhost:3000/node_modules/.vite/deps/react-router-dom.js?v=e3eec317:2503:29)
at Switch2 (http://localhost:3000/node_modules/.vite/deps/react-router-dom.js?v=e3eec317:2647:29)
at div
at div
at App (http://localhost:3000/@fs/mnt/c/Users/User/Downloads/pick-a-layout/app/src/client/App.tsx:24:31)
at Router2 (http://localhost:3000/node_modules/.vite/deps/react-router-dom.js?v=e3eec317:2216:30)
at BrowserRouter2 (http://localhost:3000/node_modules/.vite/deps/react-router-dom.js?v=e3eec317:2764:35)
at QueryClientProvider (http://localhost:3000/node_modules/.vite/deps/@tanstack_react-query.js?v=e3eec317:2847:3)Do you have any errors in the terminal where you are running
wasp start?Oooooh you know what -> hot reloading won't work on WSL if your project is on the Windows file system, instead of the Linux file system. SO it should be on the Linux file system. This is an issue in WSL2, has nothing to do with Wasp actually.
https://github.com/microsoft/WSL/issues/4739
@MOTLAKZ I know you came from Mage, and @Halabrad arrived from Open Saas.
And both of them didn't see the warnig about this, because our warning about this is in the https://wasp-lang.dev/docs/quick-start, at the bottom, which they had no reason to look at.
We need some better way to inform people about this hm. Could we possibly detect, in Wasp, that it is being run on Windows file system, not Linux? We probably could. And we could warn people.
Ah! I see. Explains why the terminal shows no issues and only the DevTools
So what you will want to do is make sure your code is on the Linux file system
We actually have this article that deatils how to do Wasp development on WSL, check it out: https://wasp-lang.dev/blog/2023/11/21/guide-windows-development-wasp-wsl .
Thanks. I'll follow on it now
Ok, I created an issue for this, to better inform people about it: https://github.com/wasp-lang/wasp/issues/1857 .
GitHub
Inform users about Wasp not doing hot reloading when run on WSL on ...
Hot reloading won't work on WSL if your project is on the Windows file system, instead of the Linux file system. SO it should be on the Linux file system. This is an issue in WSL2, has nothing ...
Thanks, yes I'm on WSL2 🙏
Sadly, the ease with which this is accomplished is not working for me. Apparently there is some permission issue and after hours of research, I can't seem to find a fix. My VirtualBox stopped being supported ages ago so I cant use it either. Think I will need a divine solution.
Ah I am sorry about that @MOTLAKZ , unfortunately I am not sure how to help more. What seems to be your permissions issue? DO you have some kind of unusual setup?
I just use VSCode on Windows and have Ubuntu and Linux installed so I can use WSL. I made sure any additional instances were removed and there is no context as to where the permission issue is. It just wont let me move anything into Ubuntu folder and when I try other folders, it works, but I can't access them from VSCode when I try they are invisible.
I also tried changing ownership of the app directory from the CLI but to no avail