Alois Sečkár

> Well, the hope would be that this gets fixed in npm in the not too distant future ... 10 months... Is it the distant future yet? :D

> Any news on that ? I can't even run boilerplate code meaning basic nuxt3 quickstart code with 1 simple pinia store. just add `"overrides": { "vue": 3 }` into...

> just add `"overrides": { "vue": 3 }` into `package.json` and re-run `npm install`, works like charm in all my current Nuxt 3 projects So, this _"works like charm"_ solution...

There is definitely something wrong with Rollup in Nuxt 3.2.0 I was forced to remove manual chunking for DevExtreme UI, because I started getting ``` Entry module "devextreme-vue/button" cannot be...

Thank you, @danielroe, this works great. I just realized one think I don't quite understand the build process. File in `node_modules` for `devextreme-vue/data-grid` has 90 KB. What happens during production...

Thank you for pointing me to the right direction, @fastfedora :+1:

I can't explain, but docs say it is expected behaviour https://nuxt.com/docs/guide/directory-structure/components#dynamic-components also [here](https://github.com/nuxt/nuxt/issues/14036#issuecomment-1397340475)

This exact behaviour is pointed out in [Vue.js docs](https://vuejs.org/guide/built-ins/keep-alive.html#lifecycle-of-cached-instance) But we would need someone more skilled in the framework to tell us both why.

I'll repeat myself about the docs: "When a component instance is removed from the DOM but is part of a component tree cached by ``, **it goes into a deactivated...

Now I am delving deeper into your example. I start believing it actually works as that, but the messages from different components are mixing up in the console. I tried...