You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a nuxt bridge project consisting of three pages that are linked to each other, each utilizing the no-prefetch prop in all links. However, upon generating and starting the project, all chunks related to my pages and components are loaded in a single location, rather than loading only the chunks relevant to the currently opened page.
Consequently, this leads to unused component styles from other pages being loaded on the main page, resulting in unnecessary bloat and potential styling conflicts.
Additional context
This issue is not present in Nuxt 3, suggesting a discrepancy in behavior between the versions.
If you set isAsync: true inside the components configs, this issue be solved only in dev mode.
Logs
No response
The text was updated successfully, but these errors were encountered:
We have added an option to not use @vitejs/plugin-legacy.
It will be released with Nuxt Bridge 3.2.0!
(If you want to use it quickly, it is available after bridge-edge@3.1.0-28522654.a6eae9b.)
Environment
Reproduction
https://github.com/hamedniroumand/nuxt-bridge-sample
Describe the bug
I have a nuxt bridge project consisting of three pages that are linked to each other, each utilizing the no-prefetch prop in all links. However, upon generating and starting the project, all chunks related to my pages and components are loaded in a single location, rather than loading only the chunks relevant to the currently opened page.
Consequently, this leads to unused component styles from other pages being loaded on the main page, resulting in unnecessary bloat and potential styling conflicts.
Additional context
This issue is not present in Nuxt 3, suggesting a discrepancy in behavior between the versions.
If you set
isAsync: true
inside thecomponents
configs, this issue be solved only in dev mode.Logs
No response
The text was updated successfully, but these errors were encountered: