\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CIntroSlider />\r\n \u003CWidgetFeatured />\r\n \u003CLazyWidgetBenefits />\r\n \u003CLazyWidgetProducts />\r\n \u003CLazyWidgetBannersSlider />\r\n \u003CLazyWidgetBanners />\r\n \u003CLazyWidgetTestimonials />\r\n \u003CLazyFooter />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n\r\nAnd here you can see the Network queue. Footer's mjs and css are loaded as 7th most important assets. This is not what I'm expecting because content like images inside intro slider are more important than footer.\r\n\r\n```\r\ncss2?family=Inter:wght@400;500;600&display=swap\r\nentry-9827921d.mjs\r\nentry.c17fe9a0.css\r\ndefault-84799b20.mjs\r\ndefault.84b15a94.css\r\nAlert-84c7b89b.mjs\r\nFooter-ff7172cf.mjs\r\nFooter.b99df422.css\r\nVNuxtLink-a1e036df.mjs\r\nVButton-89f5f43e.mjs\r\nContainerFluid-62a50c2c.mjs\r\n```\r\n\n\n### Describe the bug\n\nNo way to disable default preload behaviour. Or is there a way to disable preload behaviour and mark component as with high priority which will preload its mjs and css?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3054,3057],{"name":3055,"color":3056},"enhancement","8DEF37",{"name":3026,"color":3027},13874,"allow changing priority hints for modules and their CSS","2024-12-26T06:08:32Z","https://github.com/nuxt/nuxt/issues/13874",0.71257377,{"description":3064,"labels":3065,"number":3069,"owner":3029,"repository":3029,"state":3070,"title":3071,"updated_at":3072,"url":3073,"score":3074},"Hi guys, I'm trying to use uikit inside nuxt, based in this [example](https://github.com/nuxt/nuxt.js/tree/dev/examples/uikit)\r\n\r\nnow, I want to use sass because I require change some uikit variables for custom personalization, in the example he's using plain css...\r\n\r\nfollowing the uikit instructions\r\n```\r\n// 1. Your custom variables and variable overwrites.\r\n$global-link-color: #DA7D02;\r\n\r\n// 2. Import default variables and available mixins.\r\n@import \"uikit/src/scss/variables-theme.scss\";\r\n@import \"uikit/src/scss/mixins-theme.scss\";\r\n\r\n// 3. Your custom mixin overwrites.\r\n@mixin hook-card() { color: #000; }\r\n\r\n// 4. Import UIkit.\r\n@import \"uikit/src/scss/uikit-theme.scss\";\r\n```\r\n\r\ninside my nuxt config I add the files path\r\n```js\r\n css: [\r\n '~/assets/main-variables.scss',\r\n 'uikit/src/scss/variables-theme.scss',\r\n 'uikit/src/scss/mixins-theme.scss',\r\n '~/assets/main-theme.scss',\r\n 'uikit/src/scss/uikit-theme.scss',\r\n\r\n ]\r\n```\r\n\r\nand I create the file _main-variables_ and _main-theme_ inside the assets folder, my idea is that if the css array is loaded in order must works ok (or not???)\r\n\r\nrunning the code I get this\r\n```shell\r\nERROR Failed to compile with 1 errors 11:01:10 a. m.\r\n\r\n error in ./node_modules/uikit/src/scss/uikit-theme.scss\r\n\r\nModule build failed: \r\n$base-code-background: $global-muted-background !default;\r\n ^\r\n Undefined variable: \"$global-muted-background\".\r\n in /home/me/Descargas/proj/js/nuxt/uikitest2/node_modules/uikit/src/scss/theme/base.scss (line 16, column 50)\r\n\r\n @ ./node_modules/uikit/src/scss/uikit-theme.scss 4:14-176 13:3-17:5 14:22-184\r\n @ ./.nuxt/App.js\r\n @ ./.nuxt/index.js\r\n @ ./.nuxt/client.js\r\n @ multi webpack-hot-middleware/client?name=client&reload=true&timeout=30000&path=/__webpack_hmr ./.nuxt/client.js\r\n\r\n nuxt: Call close hooks (2) +0ms\r\n nuxt: server closed +2ms\r\n\r\n```\r\n\r\nnow, it said that $global-muted-background is not defined when it load uikit-theme.scss...but doing a search, I found that this variable is defined in \r\n\r\n```\r\nnode_modules/uikit/src/scss/variables-theme.scss:$global-muted-background: #f8f8f8 !default;\r\n```\r\n\r\nnow, seems that the loader isn't loading variable-themes.scss and them main-theme.scss but it doing the loader in random order, is it ok???\r\n\r\nI suppose that I can create a file in assets and load the uikit themes and variables without problem but I've the doubt if I'm doing something wrong or it's the expected behaviour...\r\n\r\nthank you so much, I really love nuxtjs...\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7741\">#c7741\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3066],{"name":3067,"color":3068},"2.x","d4c5f9",3889,"closed","are css files inside nuxt config loaded in order???","2023-01-18T16:26:42Z","https://github.com/nuxt/nuxt/issues/3889",0.6856763,{"description":3076,"labels":3077,"number":3069,"owner":3029,"repository":3046,"state":3070,"title":3082,"updated_at":3083,"url":3084,"score":3074},"### Description\n\nI have a UNavigationMenu in vertical orientation in a sidebar. I would like to always have the current path open from the current route\n\ndoing something like: defaultOpen: route.path.includes('/xxx')\n\nresults in a very laggy experience... is there any other way to achieve this?",[3078,3081],{"name":3079,"color":3080},"question","d876e3",{"name":3040,"color":3041},"UNavigationMenu in Sidebar: Default open current route","2025-04-14T14:34:07Z","https://github.com/nuxt/ui/issues/3889",{"description":3086,"labels":3087,"number":3092,"owner":3029,"repository":3029,"state":3070,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Version\n\n[v1.4.2](https://github.com/nuxt.js/releases/tag/v1.4.2)\n\n### Reproduction link\n\n[https://github.com/pearofducks/nuxt-bug-reproduction](https://github.com/pearofducks/nuxt-bug-reproduction)\n\n### Steps to reproduce\n\n- `yarn` then `yarn dev` to bootstrap\n- observe that for `div.page-content`: `foo.css` is loaded *after* `default.vue` and `index.vue` — this is 100% counter to what should be done for base CSS imports, components should be able to override these\n\nbonus round:\n- change `nuxt.config.js` CSS property to import `test.css` instead of `foo.css` (commented in file)\n- observe that the CSS loading order has completely changed and `test.css` now comes *before* the components\n\n### What is expected ?\n\n config.css files should always be loaded before component-based styles\n\n### What is actually happening?\n\nconfig.css is sometimes being loaded after component-based styles, and sometimes after — dependent on the file (size?)\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7688\">#c7688\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3088,3091],{"name":3089,"color":3090},"pending triage","E99695",{"name":3067,"color":3068},3851,"CSS loaded in wrong (also varying) order","2023-01-22T15:30:05Z","https://github.com/nuxt/nuxt/issues/3851",0.69001013,{"description":3098,"labels":3099,"number":3102,"owner":3029,"repository":3029,"state":3070,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Version\n\n[2.2.0](https://github.com/nuxt.js/releases/tag/2.2.0)\n\n### Reproduction link\n\n[https://github.com/AndrewBogdanovTSS/nuxt-css-order](https://github.com/AndrewBogdanovTSS/nuxt-css-order)\n\n### Steps to reproduce\n\n- Clone the repo\n- $ nuxt build\n- $ nuxt start\n\n### What is expected ?\n\nSwiper active control has orange color and positioned at the bottom http://take.ms/UsNSR\n\n### What is actually happening?\n\nSwiper active control has blue color and has a shift of 10px\nhttp://take.ms/ZDjz0\n\n### Additional comments?\n\nThis issue is happening due to a fact that order of extracted css files is wrong when extractCSS is in use. \n`vendors.css` is placed after `app.css` this is causing vendor styles to override stylesheets defined by the user\nhttp://take.ms/ynVEVK \nhttp://take.ms/D8FH9\n\n\u003C!--cmty-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8052\">#c8052\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3100,3101],{"name":3089,"color":3090},{"name":3067,"color":3068},4219,"CSS Order is different when extractCSS is used","2023-01-22T15:30:07Z","https://github.com/nuxt/nuxt/issues/4219",0.70029503,{"description":3108,"labels":3109,"number":3114,"owner":3029,"repository":3029,"state":3070,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.9.0\r\n- Nuxt Version: -\r\n- CLI Version: 3.10.0\r\n- Nitro Version: -\r\n- Package Manager: pnpm@8.12.1\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n#### I don't understand what determines the sorting order of loading chunks.\r\n#### One fine day, the chunks got confused and began to be sorted in a different order.\r\n\r\n### On the first screen as it was before:\r\n\r\n\u003Cimg width=\"944\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/52721424/ce1c5086-3e76-4216-b12f-11c28688ddf8\">\r\n\r\n## It can be seen that default.[hash].css is at the beginning of the list and has a rel=\"stylesheet\" parameter\r\n```\r\n\u003Clink rel=\"stylesheet\" href=\"/_nuxt/default.414593af.css\">\r\n```\r\n\r\n### But at some point the generation gave me this:\r\n\u003Cimg width=\"943\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/52721424/bc7311ce-7caa-40c5-982b-a303b1ca5bd3\">\r\n\r\n\r\n## Our link with default.[hash].css flew down somewhere and changed the rel to prefetch and added a attr as=\"style\"\r\n```\r\n\u003Clink rel=\"prefetch\" as=\"style\" href=\"/_nuxt/default.414593af.css\">\r\n```\r\n\n\n### Describe the bug\n\n### Please help me figure out who controls the order and types of links, where I can find this information\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3110,3113],{"name":3111,"color":3112},"3.x","29bc7f",{"name":3089,"color":3090},24878,"Chunk ordering in Nuxt 3 (When generating)","2024-01-02T11:48:14Z","https://github.com/nuxt/nuxt/issues/24878",0.705486,{"description":3120,"labels":3121,"number":3124,"owner":3029,"repository":3029,"state":3070,"title":3125,"updated_at":3126,"url":3127,"score":3128},"### 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_",[3122,3123],{"name":3111,"color":3112},{"name":3089,"color":3090},25393,"Discrepancies in production build styles order (compared to nuxt 2)","2024-01-26T20:16:35Z","https://github.com/nuxt/nuxt/issues/25393",0.7055852,{"description":3130,"labels":3131,"number":3138,"owner":3029,"repository":3029,"state":3070,"title":3139,"updated_at":3140,"url":3141,"score":3142},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.15.1`\r\n- Nuxt Version: `3.6.5`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `app`, `runtimeConfig`, `css`, `vite`, `experimental`, `modules`, `build`, `sanity`\r\n- Runtime Modules: `@nuxtjs/sanity@1.8.0`, `@pinia/nuxt@0.4.11`, `nuxt-graphql-client@0.2.29`, `@vueuse/nuxt@10.2.1`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nSee screenshots attached... feel as though they'll clear enough.\n\n### Describe the bug\n\nStyles order set within a template .vue file aren't reflected during a production build (SSG, for example)\r\n\r\n\r\n\r\n\r\nThese above screenshots show the code in the editor as well as what is outputted during local development but in the following screenshots, in production, `font-feature-settings: 'case' on;` is moved to the top.\r\n\r\n\r\n\r\n\r\nAny known reason why this would happen? And if I can resolve?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3132,3133,3134,3135],{"name":3111,"color":3112},{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3136,"color":3137},"🔨 p3-minor","FBCA04",22932,"Styles not always in correct order when in production (SSG)","2023-09-04T11:31:34Z","https://github.com/nuxt/nuxt/issues/22932",0.7073067,["Reactive",3144],{},["Set"],["ShallowReactive",3147],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fj1yZUmeangeX23rlaVA5ZB4-C4ssYvnr-HItWfGzPd4":-1},"/nuxt/ui/4054"]