Open antonio-fr opened 1 year ago
Any plan or feedback about this?
Hi, @antonio-fr. I have no quick solution for it... This might be more related to vue and requires deep dive. Would be nice to separate reproduction from Vuestic Admin and make issue in vue repo.
My current understanding of this issue is that this is not related to Vue, but to Vuestic or VuesticAdmin. One solution could be to replace va-dropdown by va-accordion in MenuAccordion.
My current understanding of this issue is that this is not related to Vue, but to Vuestic or VuesticAdmin. One solution could be to replace va-dropdown by va-accordion in MenuAccordion.
Try to update vue to latest ^3.3.4
it fixes the issue for me.
Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.
I'm submitting a ...
Do you want to request a feature or report a bug? Report a bug
What is the current behavior? When editing MenuAccordion component, the HMR is not working. An error is encountered, hence the HMR is stopped.
If the current behavior is a bug, please provide the steps to reproduce, ideally also a screenshot or gif if it's a style issue Start the local service with 'npm run dev' Edit src/components/sidebar/menu/MenuAccordion.vue HMR doesn't work, because of an error.
TypeError: Cannot read properties of null (reading '_vei')
What is the expected behavior? HMR should work.
What is the motivation / use case for changing the behavior? Fix this issue. Because for every change in the MenuAccordion (and eventually component files "around"), the HMR is not working. So the developer needs to manually trigger the refresh of the page, and this makes a cold refresh.
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
This may be a bug in the underlying VuesticUI.
runtime-core.esm-bundler.js:571 TypeError: Cannot read properties of null (reading '_vei')