\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_",[2865,2868],{"name":2866,"color":2867},"enhancement","8DEF37",{"name":2869,"color":2870},"馃嵃 p2-nice-to-have","0E8A16",13874,"nuxt","open","allow changing priority hints for modules and their CSS","2024-12-26T06:08:32Z","https://github.com/nuxt/nuxt/issues/13874",0.79571795,{"description":2879,"labels":2880,"number":2883,"owner":2872,"repository":2884,"state":2885,"title":2886,"updated_at":2887,"url":2888,"score":2889},"Like on `Design Kit`",[2881],{"name":2866,"color":2882},"1ad6ff",631,"nuxt.com","closed","[Resources] Live events `Ask us for a conference` link should have a gradient border","2023-02-15T12:30:52Z","https://github.com/nuxt/nuxt.com/issues/631",0.69719785,{"description":2891,"labels":2892,"number":2901,"owner":2872,"repository":2872,"state":2885,"title":2902,"updated_at":2903,"url":2904,"score":2905},"Possibly we could move CSS resource hints from preload -> prefetch, and/or change stylesheet to load after site is interactive, maybe following one of [these strategies](https://github.com/GoogleChromeLabs/critters#preloadstrategy).",[2893,2894,2897,2898],{"name":2866,"color":2867},{"name":2895,"color":2896},"3.x","29bc7f",{"name":2869,"color":2870},{"name":2899,"color":2900},"performance","E84B77",14792,"avoid double-downloading of inlined css","2023-01-19T17:40:20Z","https://github.com/nuxt/nuxt/issues/14792",0.7592628,{"labels":2907,"number":2912,"owner":2872,"repository":2872,"state":2885,"title":2913,"updated_at":2914,"url":2915,"score":2916},[2908,2909],{"name":2866,"color":2867},{"name":2910,"color":2911},"2.x","d4c5f9",8113,"Preload resources set crossorigin separately between css and js.","2024-06-14T16:04:13Z","https://github.com/nuxt/nuxt/issues/8113",0.77342194,{"description":2918,"labels":2919,"number":2921,"owner":2872,"repository":2884,"state":2885,"title":2922,"updated_at":2923,"url":2924,"score":2925},"",[2920],{"name":2866,"color":2882},387,"`/resources` page should redirect to `/resources/blog`","2022-04-22T11:12:32Z","https://github.com/nuxt/nuxt.com/issues/387",0.78076166,{"description":2927,"labels":2928,"number":2921,"owner":2872,"repository":2929,"state":2885,"title":2930,"updated_at":2931,"url":2932,"score":2925},"in [module testing docs](https://test-utils.nuxtjs.org/api-reference/module-testing) page It only shows the following options:\r\n- `addPlugin`\r\n- `addLayout` \r\n- `addErrorLayout`\r\n- `addServerMiddleware` \r\n- `requireModule`\r\n\r\nBut the `addModule` option is not documented although it can be used!",[],"test-utils","Module testing page is missing the \"addModule\" option","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/387",{"description":2934,"labels":2935,"number":2937,"owner":2872,"repository":2884,"state":2885,"title":2938,"updated_at":2939,"url":2940,"score":2941},"Blocked by nuxtlabs/nuxt.com#617",[2936],{"name":2866,"color":2882},620,"Replace `primary` buttons by `gradient` variant","2022-06-15T16:59:48Z","https://github.com/nuxt/nuxt.com/issues/620",0.7820427,{"description":2943,"labels":2944,"number":2937,"owner":2872,"repository":2929,"state":2885,"title":2954,"updated_at":2955,"url":2956,"score":2941},"After update `\"nuxt\": \"3.8.0\"` to `3.8.1` my test started to fail:\r\n```ts\r\nimport { describe, expect, it, vi } from 'vitest'\r\nimport { mountSuspended } from 'vitest-environment-nuxt/utils'\r\nimport type { DisplayInstance } from 'vuetify'\r\nimport * as vuetify from 'vuetify'\r\nimport GuestRegisterBtn from '~/components/main/header/GuestRegisterBtn.vue'\r\nimport * as nuxt from 'nuxt/app'\r\n\r\ndescribe('Guest Register button test', () => {\r\n const navigateToSPY = vi.spyOn(nuxt, 'navigateTo').mockReturnValue(Promise.resolve())\r\n\r\n it('check login guest button for mobile in header', async () => {\r\n const component = await mountSuspended(GuestRegisterBtn)\r\n const buttonWide = component.find('button')\r\n\r\n // This is still working\r\n const classes: string[] = buttonWide.classes()\r\n expect(classes).contains('v-btn--variant-plain')\r\n // ... other working asserts\r\n\r\n await buttonWide.trigger('click')\r\n // This does not work after update 馃憞馃徎馃憞馃徎馃憞馃徎馃憞馃徎 鉂孿r\n expect(navigateToSPY).toHaveBeenCalledOnce()\r\n expect(navigateToSPY).toBeCalledWith('/login?t=1') \r\n })\r\n```",[2945,2948,2951],{"name":2946,"color":2947},"vitest-environment","b60205",{"name":2949,"color":2950},"needs reproduction","DE7793",{"name":2952,"color":2953},"closed-by-bot","ededed","trigger('click') stopped working after Nuxt update from `3.8.0` to `3.8.1`","2024-09-05T12:34:30Z","https://github.com/nuxt/test-utils/issues/620",{"description":2958,"labels":2959,"number":2967,"owner":2872,"repository":2872,"state":2885,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v21.6.1`\r\n- Nuxt Version: `0.0.0`\r\n- Nitro Version: `-`\r\n- Package Manager: `npm@9.6.4`\r\n- Builder: `webpack`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-9d4aie?file=pages%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\nWhen building for production and inspecting page source, I get most of the CSS inlined with \u003Cstyle> tags properly, but not all of it.\r\n\r\nI always end up having some components producing a \u003Clink> CSS like this one: `\u003Clink rel=\"stylesheet\" href=\"[/_nuxt/homepage.vy-tb-hO.css](http://localhost:3000/_nuxt/homepage.vy-tb-hO.css)\">` which is a blocking resource and lighthouse complains about it. \r\n\r\nYou can run a lighthouse report and see \"Avoid render-blocking resources\" - this is a huge pain in my main production app costing us almost 2.5 seconds.\r\n\r\nWhy is this happening? I saw the docs stating that all CSS is automatically inlined :)\r\nThank you so much for any help!\r\n\r\n### Additional context\r\n\r\nYou can see the issue here very clearly: view-source:https://www.locaverse.at/essen-bestellen\r\nAll component's CSS is style=\"scoped\"\r\n\r\n### Logs\r\n\r\n_No response_",[2960,2961,2964],{"name":2895,"color":2896},{"name":2962,"color":2963},"pending triage","E99695",{"name":2965,"color":2966},"inline styles","68AF97",26056,"CSS is inlined and added as a blocking resource after production build","2024-03-21T21:20:40Z","https://github.com/nuxt/nuxt/issues/26056",0.78414094,{"description":2973,"labels":2974,"number":2977,"owner":2872,"repository":2872,"state":2885,"title":2978,"updated_at":2979,"url":2980,"score":2981},"### What problem does this feature solve?\n\n\nI would like to use gradient and images as a background of loadingIndicator.\nHowever, the background property of the loadingIndicator template is currently attached with -image suffix and it can not be done.\nhttps://github.com/nuxt/nuxt.js/blob/dev/lib/app/views/loading/circle.html#L3\n\n### What does the proposed changes look like?\n\nI'd like to Implement function and submit a Pull Request.\nThe function content is to delete the -image suffix, or add the option of `{image: true}` to lodindIndicator.\n\nIs this reasonable?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7512\">#c7512\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2975,2976],{"name":2866,"color":2867},{"name":2910,"color":2911},3649,"Add 'Remove \"-image\" to background' option or remove '-image' suffix to background property to loadingIndicator","2023-01-22T15:50:41Z","https://github.com/nuxt/nuxt/issues/3649",0.7849181,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$foGZa0-KitF1kimUpC6dcWNMFPX8BdEwLHA0KmHzMjas":-1},"/nuxt/nuxt.com/632"]