-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
[Vite 3] HMR doesn't work on first dev #8719
Comments
Also isn't the following surprising?
Maybe I'm missing something here, but I've doubts this is the first impression Vite wants to give to users. |
Actually, I'm seeing that this message isn't shown in other examples. Not sure why it's shown? |
@brillout people switch to vite@3.0.0-beta.1, the client error you show here looks resolved there. The HMR issue still persists though. Trying to understand what is going on |
HMR one happens with 3.0.0-alpha.10 but does not happen with 3.0.0-alpha.9. (tried with plugin-react@2.0.0-alpha.3) |
Thanks @sapphi-red, looks like the first PR where it fails is: There is a refactoring and a fix on it, but at least we are getting closer. |
@brillout this should be fixed by: vite-plugin-ssr is currently adding all pages to |
👍 Neat.
Makes sense. Thanks a lot for the hint; I've changed vite-plugin-ssr to only set (Btw. I'm wondering whether these messages |
We are only showing the message now when there is a reload (IIRC). Why would you want to set |
This. It's one reason I've opened #8721 (but feel free to ignore it :-)). But the primary motivation is the subpar end-user DX: the user is wondering why the browser reloads and may think "something's wrong with my app, why is my app reloading at the beginning?". |
Describe the bug
HMR doesn't work the first time the dev server is started.
Reproduction
https://github.com/brillout/vite-3-bug_hmr-first-dev
System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: