This issue could be caused by a few different factors. Here are a few potential solutions to try:
Clear the cache: Sometimes, cached files can cause issues with reactivity. Try clearing the cache by running the following command:
npm cache clean --force
Update dependencies: Make sure all your dependencies are up to date. Run the following command to update all dependencies in your project:
npm update
Check for conflicting packages: It's possible that there are conflicting packages in your project that are causing the reactivity issues. Check your package.json file for any duplicate or conflicting packages and remove them.
Restart your development server: Sometimes, simply restarting your development server can resolve reactivity issues. Try stopping the server and running npm run dev again.
If none of these solutions work, it would be helpful to provide more information about your setup, such as the specific versions of React and other relevant packages you are using, as well as any error messages you are seeing.
@vincent15000 Vite doesn't have an npm watch command, just the npm run dev.
But I think I found the problem. It wasn't actually the reactivity breaking as much as the assets were not being refreshed accordingly, and it was caused for some reason by the fact that I was aliasing some paths in vide.config.js.
I remove those aliases ( reverting to the ugly imports using "../../.." ) and everything works without issue.
I am indeed using WSL on Windows. I the thread you're sharing, your're suggesting amongst other things to remove https:true, but I am using https. Would it have any issue whatsoever with it?
The fun part is that hmr is actually working, it just stops working suddenly, and I cannot really tell why .. which makes this all the more difficult to troubleshoot.
