-
Notifications
You must be signed in to change notification settings - Fork 434
HMR does not work with class-components loaded in the router #521
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
Comments
Now I rewrite the
|
HMR not working for components that are loaded via the router is a deal breaking issue for my new projects right now. Can this problem please be acknowledged and either a timeline be given when a fix will be released or at least said that no fix is coming? |
Another issue for Quasar was created (quasarframework/quasar#10527) because of this issue. I did some initial work for tracking it down over there (see here: quasarframework/quasar#10527 (comment) ). However, I am concerned that the project is currently sitting inactive on all branches while issues sit open. |
The problem apparently is into vue-loader itself, see vuejs/vue-loader#1897 |
Hello there, there seems to be a HMR issue when using vue-class-components in Vue3. It seems to have to do with components that are loaded in the routes. I created a codesandbox to reproduce this issue:
https://codesandbox.io/s/fervent-haibt-htft9?file=/src/App.vue
In the 'App.vue' I created a class component in which HMR does work, try changing the text and you see it updated on the screen.
In
Index.vue
which is put into a router-view in theroutes.js
file, HMR works when you use the old options syntax, but when you use the class syntax the HMR does not work anymore.This is of course not a very nice developer experience, can this be fixed?
The text was updated successfully, but these errors were encountered: