\n \u003CPageContentblock v-for=\"(item, index) in posts.data[0].content\" :key=\"item.id\" :item=\"item\" v-once/>\n \u003C/div>\n\u003C/template>\n\u003Cscript setup lang=\"ts\">\nconst img = useImage()\nconst { data: posts } = await useAsyncData('home', () => $fetch('https://dummyurl.to.directus'), { watch: false, deep: false, strategy: 'static' })\nvar metaData = [{ name: 'description', content: posts.value.data[0].meta_description }, { property: 'og:image', content: img('/directus/assets/' + posts.value.data[0].OG_Image,{ width: 1024, height: 576, format: 'webp'}) }]\nuseHead({\n title: posts.value.data[0].titel,\n meta: metaData\n})\n\u003C/script>\n\n### Reproduction\n\nYou can see the issue live on my production website when you open the console:\nhttps://www.florian-strasser.de\n\n### Describe the bug\n\nWhen I switched over from nuxt 2 to nuxt 3 it introduced my website to the warning:\n`The resource https://www.florian-strasser.de/_payload.json?54c17914-61aa-4ea1-86d9-735ec3e50181 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it wasn't preloaded for nothing.`\n\nAt first I thought that this will be fixed during later patches, but now we are more or less before nuxt 4 and it still appears.\n\nSince the latest patches there is also another json file that has a similar warning:\n`[Warning] The resource https://www.florian-strasser.de/_nuxt/builds/meta/54c17914-61aa-4ea1-86d9-735ec3e50181.json was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it wasn't preloaded for nothing.`\n\nThe Files are not that big as I would expect any problems - also my page speed results are pretty good so I really don't understand what could be the issue for that type of warning. When inspecting the payload json someone could argue that this is actually alot of text, but I don't see other possibilities when creating an entire page.\n\nFor the meta file I'm even more confused since is a very small file.\n\nAnyone has an idea?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3019,3022],{"name":3020,"color":3021},"pending triage","E99695",{"name":3023,"color":3024},"needs reproduction","FBCA04",30833,"nuxt","open","[de:translated] payload.json and meta json file preloaded but not used within a few seconds","2025-03-18T22:28:42Z","https://github.com/nuxt/nuxt/issues/30833",0.7048777,{"description":3033,"labels":3034,"number":3046,"owner":3026,"repository":3047,"state":3027,"title":3048,"updated_at":3049,"url":3050,"score":3051},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nHello everyone, I’d like to discuss the possibility of setting `props` by default from `AppConfig`. Currently, it’s very convenient that we can configure the theme through the config. It would be great to have a similar option for props. Previously, @benjamincanac mentioned [here](https://github.com/nuxt/ui/issues/1289#issuecomment-2480556540) that this is not currently planned.\n\nMy proposal is simple: wrap all `withDefaults` in our own implementation. This way, we can define props without making significant changes to the code.\n\n## What it could look like\n\nLet’s look at the `Accordion.vue` component. At the moment, its props look like this:\n```ts\nconst props = withDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n type: 'single',\n collapsible: true,\n labelKey: 'label'\n})\n```\nLet’s assume our wrapper is called `withUiDefaults`. Then the code would look like this:\n```diff\n-const props = withDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n+const props = withUiDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n type: 'single',\n collapsible: true,\n labelKey: 'label'\n})\n```\nThe implementation of `withUiDefaults` is quite simple:\n```ts\nfunction withUiDefaults(props, defaults) {\n const defaultFromConfig = {}\n\n return withDefaults(props, {\n ...defaults,\n ...defaultFromConfig\n })\n}\n``` \n\n## Issues I See\n\n1) **Typing `AppConfig` might be challenging** \n We would need to somehow generate types based on the components. \n **My opinion:** I think we can retrieve this using `vue-component-meta` during the UI build stage. So, in my opinion, this isn’t a significant problem.\n\n2) **Developers might set `modelValue` or other critical props by default** \n **My opinion:** In such cases, we can log a warning to the console. Additionally, developers should understand which props they are overriding. We won’t be able to cover all edge cases, but I don’t think we need to.\n\n### Additional context\n\n_No response_",[3035,3038,3041,3044],{"name":3036,"color":3037},"enhancement","a2eeef",{"name":3039,"color":3040},"v3","49DCB8",{"name":3042,"color":3043},"closed-by-bot","ededed",{"name":3045,"color":3043},"stale",2662,"ui","Override default props from `AppConfig`","2025-07-03T08:46:07Z","https://github.com/nuxt/ui/issues/2662",0.7071896,{"description":3053,"labels":3054,"number":3058,"owner":3026,"repository":3026,"state":3059,"title":3060,"updated_at":3061,"url":3062,"score":3063},"Nuxt 3 should provide defaults headers for best developer experience.\n\n```js\n{ charset: 'utf-8' }\n{ name: 'viewport', content: 'width=device-width, initial-scale=1' }\n```\n\nWe shall also provide a key for uniqueness (`hid` for vue-meta)",[3055],{"name":3056,"color":3057},"3.x","29bc7f",11635,"closed","app: Head defaults","2023-01-19T15:30:10Z","https://github.com/nuxt/nuxt/issues/11635",0.4558296,{"labels":3065,"number":3067,"owner":3026,"repository":3026,"state":3059,"title":3060,"updated_at":3068,"url":3069,"score":3063},[3066],{"name":3056,"color":3057},11683,"2023-01-19T15:33:19Z","https://github.com/nuxt/nuxt/issues/11683",{"description":3053,"labels":3071,"number":3073,"owner":3026,"repository":3026,"state":3059,"title":3060,"updated_at":3068,"url":3074,"score":3063},[3072],{"name":3056,"color":3057},11718,"https://github.com/nuxt/nuxt/issues/11718",{"description":3053,"labels":3076,"number":3081,"owner":3026,"repository":3026,"state":3059,"title":3060,"updated_at":3082,"url":3083,"score":3084},[3077,3078],{"name":3056,"color":3057},{"name":3079,"color":3080},"app","17512D",11682,"2023-01-19T15:58:24Z","https://github.com/nuxt/nuxt/issues/11682",0.4601645,{"labels":3086,"number":3094,"owner":3026,"repository":3026,"state":3059,"title":3095,"updated_at":3096,"url":3097,"score":3098},[3087,3090,3091],{"name":3088,"color":3089},"types","2875C3",{"name":3020,"color":3021},{"name":3092,"color":3093},"2.x","d4c5f9",10468,"Nuxt 2 Broken Typescript Typings when Specifying head","2023-03-17T12:50:05Z","https://github.com/nuxt/nuxt/issues/10468",0.69048065,{"description":3100,"labels":3101,"number":3104,"owner":3026,"repository":3047,"state":3059,"title":3039,"updated_at":3105,"url":3106,"score":3107},"The development is ongoing on the default branch of this repository: https://github.com/nuxt/ui.\n\n---\n\nA lot has changed since `@nuxt/ui` was made open-source (May 2023), so the plan here is to rewrite every component from scratch alongside their config.\n\nI'll post regular updates on this issue and on https://twitter.com/benjamincanac.\n\n## Documentation\n\nhttps://ui3.nuxt.dev\n\n## Roadmap (Nov 20, 2024)\n\n- [x] Finish the migration to `reka-ui@alpha` on `@nuxt/ui` & `@nuxt/ui-pro` #2448\n- [x] Write the docs for implemented `@nuxt/ui-pro` components\n- [x] Finish `@nuxt/ui-pro` components\n- [x] Make Nuxt UI Pro v3 work with Vue like Nuxt UI https://github.com/nuxt/ui-pro/pull/742\n- [ ] Implement new components in `@nuxt/ui` like\n - [x] `Calendar` #2618\n - [ ] `InputDate` #2524\n - [x] `Tree` #3180\n - [x] `Stepper` #2733\n- [x] Migrate all the Nuxt UI Pro templates\n - [x] Starter\n - [x] Landing\n - [x] Docs\n - [x] SaaS https://github.com/nuxt-ui-pro/saas/pull/86\n - [x] Dashboard https://github.com/nuxt-ui-pro/dashboard/pull/86\n- [ ] Build the Nuxt UI docs marketing pages\n - [x] Landing\n - [x] Figma\n - [x] Pro -> Landing\n - [x] Pro -> Pricing\n - [x] Pro -> Templates\n - [x] Pro -> Activate\n - [ ] Releases\n- [x] Write migration guide https://ui3.nuxt.dev/getting-started/migration\n- [x] Release `@nuxt/ui` & `@nuxt/ui-pro` officially once `tailwindcss` and `reka-ui` are released\n- [x] Migrate all the Nuxt apps (nuxt.com, image.nuxt.com, eslint.nuxt.com, devtools.nuxt.com, fonts.nuxt.com, hub.nuxt.com, nuxt.studio, etc.)\n- [ ] Implement new `@nuxt/ui` & `@nuxt/ui-pro` components\n- [ ] Create new templates like Changelog, Portfolio, etc. \n\n## Breaking Changes\n\nThe biggest change is the switch to `tailwind-variants`, this will cause lots of breaking changes if you've used the `ui` prop or `app.config.ts` to override the config. I apologize in advance for this but I strongly believe this will be beneficial and will bring consistency across all components.\n\n> At the beginning the config was split in many keys for the same div to give more flexibility, but since then we introduced `tailwind-merge` which now allows us to group those keys together, this is a good opportunity to clean the whole thing. \n\nThe config will now have a `slots` amongst other keys that will specifically target dom nodes. The `ui` prop will only allow you to target those slots.\n\nThese changes alongside the refactor of all components will also improve the types, the `app.config.ts` and `ui` props are now perfectly typed, as well as all components `props`, `slots`, `emits` and `expose`.\n\n> Feel free to comment on this if you have any ideas for the next major.\n\n```[tasklist]\n### Components\n- [x] Accordion\n- [x] Alert\n- [x] Avatar\n- [x] AvatarGroup\n- [x] Badge\n- [x] Breadcrumb\n- [x] Button\n- [x] ButtonGroup\n- [x] Card\n- [x] Carousel\n- [x] Checkbox\n- [x] Chip\n- [x] Collapsible\n- [x] CommandPalette\n- [x] Container\n- [x] ContextMenu\n- [x] Drawer\n- [x] DropdownMenu (Dropdown)\n- [x] Form\n- [x] FormField (FormGroup)\n- [x] Icon\n- [x] Input\n- [x] InputMenu\n- [x] Kbd\n- [x] Link\n- [x] Modal\n- [x] NavigationMenu (HorizontalNavigation/VerticalNavigation)\n- [x] Pagination\n- [x] Popover\n- [x] Progress\n- [x] Provider\n- [x] RadioGroup\n- [x] Select\n- [x] SelectMenu\n- [x] Separator (Divider)\n- [x] Skeleton\n- [x] Slideover\n- [x] Slider (Range)\n- [x] Table\n- [x] Tabs\n- [x] Textarea\n- [x] Toast (Notification)\n- [x] Switch (Toggle)\n- [x] Tooltip\n```\n",[3102],{"name":3103,"color":3040},"release",1289,"2025-07-17T12:55:11Z","https://github.com/nuxt/ui/issues/1289",0.6945486,{"description":3109,"labels":3110,"number":3115,"owner":3026,"repository":3026,"state":3059,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Environment\r\n\r\nOperating System: Windows_NT\r\nNode Version: v18.0.0\r\nNuxt Version: 3.3.3\r\nNitro Version: 2.3.2\r\nPackage Manager: npm@9.4.2\r\nBuilder: vite\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/iabirkhan/Nuxt-3-Minimal\r\n\r\n### Describe the bug\r\n\r\nwith default nuxt 3.3.3 setup or upgraded version shows type error in nuxt,config.ts. \r\n\r\n- *** This type error shows on minimal setup:\r\n\r\nArgument of type '{ app: { head: { charset: string; viewport: string; }; }; }' is not assignable to parameter of type 'NuxtConfig'.\r\n Object literal may only specify known properties, and 'app' does not exist in type 'NuxtConfig'.ts(2345)\r\n\r\n- *** Extending config also shows type error on plugins, css, build, vite\r\n\r\n```\r\nexport default defineNuxtConfig({\r\n// app, plugins, css, build, vite not working\r\n app: {\r\n head: {\r\n title: \"Nuxt 3 App\",\r\n charset: \"utf-8\",\r\n viewport: \"width=device-width, initial-scale=2\",\r\n },\r\n }, // if app config removed plugins dosen't work\r\n plugins: [], // shows error one after another\r\n css: [],\r\n build: {},\r\n vite: {},\r\n// modules, typescript working\r\n modules: [],\r\n typescript: {\r\n strict: true,\r\n },\r\n});\r\n```\r\n\r\nHopefully explained the problem clearly, please check. \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3111,3112,3113,3114],{"name":3088,"color":3089},{"name":3056,"color":3057},{"name":3020,"color":3021},{"name":3023,"color":3024},20040,"shows type error on nuxt.config.ts for app meta, plugins, css, build, vite","2023-12-05T07:21:45Z","https://github.com/nuxt/nuxt/issues/20040",0.6954853,{"description":3121,"labels":3122,"number":3126,"owner":3026,"repository":3026,"state":3059,"title":3127,"updated_at":3128,"url":3129,"score":3130},"Hi,\r\nas the release of `Vue 2.2` of `vue-server-renderer` adds the `context.head` and `context.style` functions, maybe drop this in favor for the use of `vue-meta`? Might make `NUXT` more lightweight and independent from external dependency.\r\nCheers!\r\n\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c270\">#c270\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3123,3125],{"name":3036,"color":3124},"8DEF37",{"name":3092,"color":3093},318,"making use of vue-server-renderer contex.head and context.style function","2023-01-18T15:38:47Z","https://github.com/nuxt/nuxt/issues/318",0.70061976,["Reactive",3132],{},["Set"],["ShallowReactive",3135],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fwxaVanKLu_p9Cw08oGf0gruMvq1z1Jk36OaNzMxNa30":-1},"/nuxt/nuxt/11459"]