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
HMR doesn't work for components that aren't rendered yet (vue-router) #131
Comments
@onx2 did you find a fix for this? This issue is still happening on:
|
@SpeakInCode No it doesn't seem to work. I have noticed that if you haven't navigated to a route yet, but make an update it will work. Once you've navigated to the route, HMR doesn't work for it unless it is rendered on the screen or you save again after navigating. I'll re-open this since I'm not the only one having trouble. My deps: "dependencies": {
"vue": "^3.0.0",
"vue-router": "^4.0.0-beta.13"
},
"devDependencies": {
"@vue/compiler-sfc": "^3.0.0",
"vite": "^1.0.0-rc.4",
} |
@onx2 We are playing with the next deps:
We do not expirience the issue you described above. But seems like we do have a similar one. I've noticed the HMR stops refreshing once any router-view has been visited/rendered. Not sure about the issue comes from vue-router nor HMR. |
Closing stale bugs for 1.x. If the issue persists in 2.0, please open a new issue with proper reproduction. |
In addition to my comment above - the issue has been resolved by fixing url to |
Describe the bug
HMR doesn't update a component that isn't rendered on the screen, but will work once the file is saved and the component is rendered already.
Reproduction
Vite log shows that HMR was triggered though:
[vite:hmr] src/views/Home.vue updated. (reload)
System Info
vite
version: 0.14.2vue
version (fromyarn.lock
orpackage-lock.json
): 3.0.0-beta.12@vue/compiler-sfc
version: 3.0.0-beta.12Logs (Optional if provided reproduction)
Screenshot of the error
The text was updated successfully, but these errors were encountered: