\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[3018,3021],{"name":3019,"color":3020},"enhancement","a2eeef",{"name":3022,"color":3023},"triage","ffffff",3868,"nuxt","ui","open","Allow assigning IDs to Nuxt UI Tab panels for scroll targeting","2025-04-12T08:35:52Z","https://github.com/nuxt/ui/issues/3868",0.67682767,{"description":3033,"labels":3034,"number":3037,"owner":3025,"repository":3038,"state":3039,"title":3040,"updated_at":3041,"url":3042,"score":3043},"",[3035],{"name":3019,"color":3036},"1ad6ff",611,"nuxt.com","closed","[Resources] Refactor showcases into a composable","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/611",0.6544397,{"description":3045,"labels":3046,"number":3037,"owner":3025,"repository":3050,"state":3039,"title":3051,"updated_at":3052,"url":3053,"score":3043},"I'm on v0.11.2 and it seems what `defineVitestConfig` wants and the type definition doesn't line up?\r\n\r\nIt wants an `InlineConfig` passed in directly in the typedef, but I'm having to do this:\r\n\r\n```js\r\nimport { defineVitestConfig } from \"nuxt-vitest/config\";\r\nimport type { InlineConfig } from \"vitest\";\r\n\r\nconst test: InlineConfig = {\r\n coverage: {\r\n all: true,\r\n branches: 87.5, // 7 / 8\r\n exclude: [\r\n \"node_modules\",\r\n \".nuxt\",\r\n \"app\",\r\n \"dist\",\r\n \"scripts\",\r\n \"*.config.ts\",\r\n \"**/types.ts\",\r\n \"**/*.tests.ts\",\r\n \"**/*.js\",\r\n \"**/*.mjs\",\r\n \"pages\",\r\n \"plugins\",\r\n \"app.vue\",\r\n ],\r\n },\r\n environment: \"happy-dom\",\r\n include: [\"**/*.tests.ts\"],\r\n};\r\n\r\n// eslint-disable-next-line @typescript-eslint/ban-ts-comment\r\n// @ts-ignore\r\nexport default defineVitestConfig({ test });\r\n```",[3047],{"name":3048,"color":3049},"vitest-environment","b60205","test-utils","typecheck issues with defineVitestConfig?","2023-12-02T23:35:07Z","https://github.com/nuxt/test-utils/issues/611",{"description":3055,"labels":3056,"number":3060,"owner":3025,"repository":3061,"state":3039,"title":3062,"updated_at":3063,"url":3064,"score":3065},"### 🐛 The bug\n\nUsing proxy from `useScriptClarity` to accept/decline consent doesn't work. The consent updates only after reloading the page (when using cookies/local storage instead of simple refs in useConsent file). When I tried using `window.clarity`, Clarity cookies update as expected.\n\n### 🛠️ To reproduce\n\nhttps://stackblitz.com/edit/nuxt-starter-cohqlgef?file=nuxt.config.ts\n\n### 🌈 Expected behavior\n\nCookies should update as expected.\n\n### ℹ️ Additional context\n\nInstead of viewing the preview window in StackBlitz use this link - https://nuxtstartercohqlgef-ptbs--3000--33edf5bb.local-credentialless.webcontainer.io. It seems cookies don't work in StackBlitz at all.\n\nMaybe I'm using the `useScriptClarity` composable wrong, but I'm not sure.",[3057],{"name":3058,"color":3059},"bug","d73a4a",442,"scripts","Clarity proxy not working","2025-04-16T08:12:32Z","https://github.com/nuxt/scripts/issues/442",0.6567632,{"description":3067,"labels":3068,"number":3069,"owner":3025,"repository":3025,"state":3039,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### Describe the feature\n\nWhen `useFetch` re-fetches (e.g. after a watched state changes), `data` is reset to `null` during the fetch. That causes visible flickering or full UI resets, even when only minor changes happen like pagination or filters.\n\nIn many apps, it's more useful to keep the previous data visible while the new request is in progress.\n\n## Suggested API\n\n```javascript\nconst { data } = await useFetch(\"/api/items\", {\n query: {\n 'page': page\n },\n watch: [page],\n preservePreviousData: true\n});\n```\nWhen preservePreviousData is true, data should hold the last successful value during the next fetch until the new result arrives.\n\n## Current workaround\n\nRight now, we have to manually store the previous data in a separate `ref` using `watch`, and use a `computed` to fall back to it when the current `data` is `null`. This adds boilerplate for a fairly common use case.\n\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[],31999,"[useFetch] Option to preserve previous data during refresh","2025-07-15T06:34:21Z","https://github.com/nuxt/nuxt/issues/31999",0.6600479,{"labels":3075,"number":3085,"owner":3025,"repository":3025,"state":3039,"title":3086,"updated_at":3087,"url":3088,"score":3089},[3076,3079,3082],{"name":3077,"color":3078},"discussion","538de2",{"name":3080,"color":3081},"3.x","29bc7f",{"name":3083,"color":3084},"app","17512D",11742,"Improve `asyncData` API","2023-01-19T15:42:33Z","https://github.com/nuxt/nuxt/issues/11742",0.6650033,{"description":3091,"labels":3092,"number":3096,"owner":3025,"repository":3038,"state":3039,"title":3097,"updated_at":3098,"url":3099,"score":3100},"- [ ] Branch deployment on domain\n- [ ] Upgrade to `nuxt3`\n- [ ] Documentation with latest docus\n- [ ] Link to go back to nuxt.com\n",[3093],{"name":3094,"color":3095},"roadmap","ff7a1a",537,"`image.nuxt.com`","2023-10-10T14:45:43Z","https://github.com/nuxt/nuxt.com/issues/537",0.6676243,{"description":3102,"labels":3103,"number":3096,"owner":3025,"repository":3050,"state":3039,"title":3105,"updated_at":3106,"url":3107,"score":3100},"I have a monorepo with a nuxt 3 app and multiple nuxt modules. The nuxt 3 app already has nuxt-vitest tests and it works great with the new RootDir option. But when I try to add nuxt-vitest to a module in the monorepo, it fails with this error:\r\n```\r\n> vitest --ui --coverage\r\n\r\nfailed to load config from /home/jordy/repositories/my_repo/packages/my_package/vitest.config.ts\r\nError: Context conflict\r\n ❯ checkConflict node_modules/unctx/dist/index.mjs:6:13\r\n ❯ Object.set node_modules/unctx/dist/index.mjs:40:9\r\n ❯ initNuxt node_modules/nuxt/dist/index.mjs:2689:11\r\n ❯ Object.ready node_modules/nuxt/dist/index.mjs:2680:18\r\n ❯ loadNuxt node_modules/nuxt/dist/index.mjs:2989:16\r\n ❯ loadNuxt node_modules/@nuxt/kit/dist/index.mjs:534:19\r\n ❯ startNuxtAndGetViteConfig node_modules/nuxt-vitest/dist/config.mjs:8:16\r\n ❯ getVitestConfigFromNuxt node_modules/nuxt-vitest/dist/config.mjs:48:15\r\n```\r\n\r\nOn their own it works, it's only when running the global vitest workspace, which has all the coverage and UI in one place.\r\n\r\nNot sure how to fix this.",[3104],{"name":3048,"color":3049},"Context conflict when running multiple projects with nuxt-vitest","2025-02-11T15:38:56Z","https://github.com/nuxt/test-utils/issues/537",{"labels":3109,"number":3114,"owner":3025,"repository":3025,"state":3039,"title":3115,"updated_at":3116,"url":3117,"score":3118},[3110,3111],{"name":3080,"color":3081},{"name":3112,"color":3113},"pending triage","E99695",14415,"useFetch fetches value on first call","2023-01-19T17:35:11Z","https://github.com/nuxt/nuxt/issues/14415",0.6714441,{"description":3120,"labels":3121,"number":3125,"owner":3025,"repository":3038,"state":3039,"title":3126,"updated_at":3127,"url":3128,"score":3129},"We should discuss what to show in that video, maybe a teasing video for the moment ?",[3122],{"name":3123,"color":3124},"design","00bd6f",630,"[Projects] Video","2022-10-03T11:03:26Z","https://github.com/nuxt/nuxt.com/issues/630",0.6721871,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fheT0k0n6FwpXMS-rsDwqb-gwgXHvjQimrvEJtmD6yAA":-1},"/nuxt/nuxt/32624"]