Vladislav

@dcodeIO any updates about release?

The main lib is 5.0.0 version while types so far 3.0.4 😭

@harlan-zw Tried with node@16 Same thing

It looks like the problem is with optional chaining, but node@18 already have native support for optional chaining

This happens because the components are created and mounted on first render. In case the component is wrapped in KeepAlive, component will be created, mounted and stored in cache and...

:roguesherlock No. `Mounted` fires only on first component render. It works as expected. If you render same component again, lifecycle would be `Deactivated`, `Activated`. As i get you care about...

@danielroe You're right, i forgot about i18n and other tools that changes routing schema. Well, then, it should be written in docs that `definePageMeta` does not work with custom routing...

Have a question just to clarify. Is project in docker container? Also provide please logs of devtools console

I've found a cause and workaround. `definePageMeta` writes meta information in every route like ```js definePageMeta({ middleware: ['private-route'] }) ``` In final router config it looks like: ```js { path:...

You can load that package by dynamic import i.e `await import('foo')` https://vitejs.dev/guide/features.html#async-chunk-loading-optimization I could give you more related answer if you provide your case