on any route client route change, but it renders properly on server side rendering (hard refresh)....\r\n\r\n\n\n### Additional context\n\n\r\n\r\nlayouts/default.vue\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"w-screen h-full min-h-[100vh]\">\r\n \u003CSiteHeader />\r\n \u003Cslot />\r\n \u003CSiteFooter />\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n import SiteHeader from './site-components/SiteHeader.vue'\r\n import SiteFooter from './site-components/SiteFooter.vue'\r\n\u003C/script>\r\n```\n\n### Logs\n\n_No response_",[3115,3116],{"name":3069,"color":3070},{"name":3072,"color":3073},24944,"[3.9.0] Client rendering and page transitions broke after updating to the newest Nuxt version","2024-01-03T19:46:15Z","https://github.com/nuxt/nuxt/issues/24944",0.6806314,{"labels":3123,"number":3128,"owner":3029,"repository":3029,"state":3031,"title":3129,"updated_at":3130,"url":3131,"score":3132},[3124,3125],{"name":3072,"color":3073},{"name":3126,"color":3127},"2.x","d4c5f9",4204,"Inconsistent css in dev vs prod","2024-08-03T20:53:43Z","https://github.com/nuxt/nuxt/issues/4204",0.68249726,{"description":3134,"labels":3135,"number":3138,"owner":3029,"repository":3029,"state":3031,"title":3139,"updated_at":3140,"url":3141,"score":3142},"### Environment\r\n\r\n```\r\nNuxt project info: \r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: css, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\n[Nuxt 3 repo](https://stackblitz.com/edit/github-qbfhyv) vs [Nuxt 2 repo](https://stackblitz.com/edit/github-4yydwm)\r\n\r\nBoth projects implement an identical structure (layout with header and index page)\r\n\r\nIn each of the reproductions, run the necessary commands to run the project in production mode\r\n- nuxt 3 - `npm run build && npm run preview`\r\n- nuxt 2 - `npm run build && npm run start`\r\n\r\nInspect the HTML code returned by accessing the index page. Notice the `\u003Cstyle>` tag in the `\u003Chead>`\r\n\r\n### Describe the bug\r\n\r\nThe way Nuxt 3 builds and extracts the CSS from the app is inconsistent with Nuxt 2. This can cause complications when migrating an existing Nuxt 2 app.\r\n\r\nIn Nuxt 3, the global styles specified from the nuxt config are injected at the end of the style tag. With Nuxt 2, these were injected at the beginning.\r\n\r\nIn both reproduction repositories, the `@/assets/styles/global.css` file is provided globally. If you inspect the result of the HTML pages (build for production), the contents of that CSS file are placed differently.\r\n\r\n**Follow-up observation** - this might be unrelated, but you will also notice that in the case of Nuxt 3, it is including the styles for both `components/dynamic/One.vue` and `components/dynamic/Two.vue` even though only at render time only `\u003Cdynamic-one />` is rendered. Nuxt 2 correctly only includes the styles from `One.vue`.\r\n\r\nIf unrelated (and is considered to be an issue) i am happy to open a separate report.\r\n\r\n### Additional context\r\n\r\nWe are in the process of migrating our Nuxt 2 app to Nuxt 3 and are running into multiple complications - this is one of them.\r\n\r\nIn the case of developing an app from scratch this would not be an issue because it would inform the development style.\r\n\r\nHowever, in our case some of the global styles get overridden by rules at the component level. The new order in Nuxt 3 causes this to break.\r\n\r\n### Logs\r\n\r\n_No response_",[3136,3137],{"name":3069,"color":3070},{"name":3072,"color":3073},25393,"Discrepancies in production build styles order (compared to nuxt 2)","2024-01-26T20:16:35Z","https://github.com/nuxt/nuxt/issues/25393",0.68262297,["Reactive",3144],{},["Set"],["ShallowReactive",3147],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0o4t9Ko1lJEaWors33_ehoBb7Fb5zKUIbklUwxbROF4":-1},"/nuxt/ui/4609"]