-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hot module replacement #3
Comments
Thanks for the issues! Can you provide a minimal reproduction for this? It works fine for me. |
Hmm maybe it's related to my TS monorepo set-up. I have an
I'll try to make a repro. |
I was able to reproduce the bug: I had fixed it in vitejs/vite#16018, but forgot to port the fix back to this plugin. Thanks for catching! Will be fixed shortly. I also found that HMR doesn't currently work in CSS Module dependencies in Vite: vitejs/vite#16074 |
🎉 This issue has been resolved in version 1.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I added this demo to the README to confirm HMR is working now in v1.3.0: |
Awesome, glad you were able to reproduce! I forked your repro because I'm still having issues when coupled with the |
Problem
You're probably aware of it already, but CSS modules are no longer reloaded automatically on change with this plugin. Even refreshing the page doesn't seem to work; I have to restart the server to see changes.
Expected behavior
Any changes to CSS modules should appear right away in the browser in development, without restarting/reloading.
Minimal reproduction URL
NA
Version
5.1.0
Node.js version
20
Package manager
pnpm
Operating system
Windows
Contributions
The text was updated successfully, but these errors were encountered: