\n\u003C/UCard>\n```\n\n### Description\n\nIf using a UTable component on a background that isn't the default neutral color the bg-color of the thead is visible.\n\n\n\n\n\n_A little bit easier to see with white Background_\n\n\n\n\nMaybe this is a wanted behavior. So if so please ignore and close the issue.\nI know sometimes you want a background color in the headlines. But sometimes you don't want them.\nAnyways if this is a wanted behavior, then maybe this issue will help those who don't want a background color and are looking for a solution.\n\n### Additional context\n\nCould be fixed by adding:\n```vue\n:ui=\"{\n thead: 'bg-unset'\n}\"\n```\nto the `\u003CUTable>` tag\n\n\n\n### Logs\n\n```shell-script\n-\n```",[2885,2886,2889],{"name":2868,"color":2869},{"name":2887,"color":2888},"v3","49DCB8",{"name":2874,"color":2875},3607,"Background-Color for UTable","2025-03-18T15:08:25Z","https://github.com/nuxt/ui/issues/3607",0.72766584,{"description":2896,"labels":2897,"number":2898,"owner":2857,"repository":2857,"state":2859,"title":2899,"updated_at":2900,"url":2901,"score":2902},"### 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-05-15T11:09:43Z","https://github.com/nuxt/nuxt/issues/31999",0.7321975,{"description":2904,"labels":2905,"number":2909,"owner":2857,"repository":2857,"state":2859,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Environment\n\nnuxt: 3.17.3\n\n### Reproduction\n\nhttps://github.com/user-attachments/assets/c5839828-9408-49d7-90e4-72ae38d8015f\n\nhttps://stackblitz.com/edit/github-ycxmi8dl-ou7o3zwv?file=pages%2Findex.vue\n\n### Describe the bug\n\nWhen `immediate: false` is set, the watch that should trigger the fetch stops working after a while. I haven't been able to fully isolate the cause, but it seems to happen when I change the watched value before the previous fetch has completed. After that, subsequent changes to the value don't trigger any new request.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2906],{"name":2907,"color":2908},"pending triage","E99695",32109,"`useFetch` with `immediate: false` causes watch to stop triggering in Nuxt 3.17.3","2025-05-14T15:07:27Z","https://github.com/nuxt/nuxt/issues/32109",0.7397317,{"description":2915,"labels":2916,"number":2917,"owner":2857,"repository":2918,"state":2859,"title":2919,"updated_at":2920,"url":2921,"score":2922},"Hi there!\n\nI've been using the Icon component both personally and at work; I found that when working with local icon collections, the intellisense I get back from the Icon component is lacking compared to the experience I have with Iconify collections.\n\nIf possible I'd like to make a modification that enables type generation for local collections (I already have a good working PR, but it might require some feedback).\n\n",[],359,"icon","Type safe local icon support","2025-02-19T19:13:53Z","https://github.com/nuxt/icon/issues/359",0.7400554,{"description":2924,"labels":2925,"number":2926,"owner":2857,"repository":2918,"state":2927,"title":2928,"updated_at":2929,"url":2930,"score":2931},"I don't have a whole lot of info for this issue other than when in `mode: 'css'` it spits out\r\n\r\n```\r\nUncaught (in promise) DOMException: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules\r\n```\r\n\r\nbut `mode: 'svg'` works just fine\r\n\r\nIts worth noting that the icons still render in CSS mode",[],189,"closed","[BUG]: CSS mode causes DOMException","2024-07-15T16:07:16Z","https://github.com/nuxt/icon/issues/189",0.63167894,{"description":2933,"labels":2934,"number":2940,"owner":2857,"repository":2877,"state":2927,"title":2941,"updated_at":2942,"url":2943,"score":2944},"Related to https://github.com/nuxt/ui/pull/2650\n\nMight be fixed when `vaul-vue` will migrate to `reka-ui`.",[2935,2936,2937],{"name":2868,"color":2869},{"name":2887,"color":2888},{"name":2938,"color":2939},"reka-ui","56d799",2920,"[Drawer] Closing when clicking on a Toast","2025-03-04T12:46:17Z","https://github.com/nuxt/ui/issues/2920",0.6399761,{"description":2946,"labels":2947,"number":2949,"owner":2857,"repository":2857,"state":2927,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.10.2\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-ftrxnd?file=pages%2Ffetch.vue\r\n\r\n### Describe the bug\r\n\r\nWhile playing around using `useRouteQuery` composable fromVueUse library, I have noticed different behaviour watching the `ref` retrieved from `useRouteQuery` when using it with `useFetch` vs `useAsyncData`.\r\nWhenever `useAsyncData` is used to call the API and `ref` from `useRouteQuery` is listed inside `watch` array, API is being called only once whenever ref value changes. As expected.\r\nBut it is different with `useFetch`, where whenever `ref` value updates, there are two API calls made where one is cancelled by dedupe.\r\n\r\nI have prepared reproduction with two different pages, each for different implementation where behaviour can be observed.\r\nI would assume it has to do with `ref` being updated twice because URL query sync, but I am not sure why it differs.\r\n\r\nAlso I am aware of https://github.com/nuxt/nuxt/issues/24788 but trying to use vueuse implementation as of now.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2948],{"name":2907,"color":2908},25852,"`useAsyncData` watch vs `useFetch` watch with `useRouteQuery` ref","2025-04-02T12:46:45Z","https://github.com/nuxt/nuxt/issues/25852",0.7065951,{"description":2955,"labels":2956,"number":2957,"owner":2857,"repository":2918,"state":2927,"title":2958,"updated_at":2959,"url":2960,"score":2961},"Hi, \r\n\r\nWe just replaced nuxt-icon with the new @nuxt/icon and our build time went from around 150 seconds to 450 seconds.\r\nThe increased delay appears to be from the prerendering phase, please see differences below.\r\n\r\nBefore:\r\n\r\n```\r\n(...)\r\nServer built in 20910ms\r\n[nitro] ℹ Initializing prerenderer\r\n[nitro] ℹ Prerendering 1 routes\r\n[nitro] ├─ /api/_content/cache.1720712707379.json (2480ms)\r\n[nitro] ℹ Prerendered 1 routes in 37.293 seconds\r\n[nitro] ✔ Generated public .output/public\r\n[nitro] ℹ Building Nuxt Nitro server (preset: node-server)\r\n[nitro] ✔ Nuxt Nitro server built\r\n ├─ .output/server/chunks/_/empty.mjs (161 B) (151 B gzip)\r\n ├─ .output/server/chunks/_/empty.mjs.map (173 B) (145 B gzip)\r\n ├─ .output/server/chunks/_/error-500.mjs (4.83 kB) (2.05 kB gzip)\r\n ├─ .output/server/chunks/_/error-500.mjs.map (190 B) (157 B gzip)\r\n ├─ .output/server/chunks/_/node.mjs (176 B) (156 B gzip)\r\n ├─ .output/server/chunks/_/node.mjs.map (216 B) (170 B gzip)\r\n ├─ .output/server/chunks/_/node2.mjs (169 B) (152 B gzip)\r\n ├─ .output/server/chunks/_/node2.mjs.map (210 B) (167 B gzip)\r\n ├─ .output/server/chunks/_/pure.mjs (2.06 kB) (903 B gzip)\r\n ├─ .output/server/chunks/_/pure.mjs.map (178 B) (150 B gzip)\r\n ├─ .output/server/chunks/_/renderer.mjs (14.8 kB) (4.32 kB gzip)\r\n ├─ .output/server/chunks/_/renderer.mjs.map (1.37 kB) (305 B gzip)\r\n(...)\r\n```\r\n\r\nAfter:\r\n\r\n```\r\n(...)\r\nServer built in 21261ms\r\n[nitro] ℹ Initializing prerenderer\r\n[nitro] ℹ Prerendering 1 routes\r\n[nitro] ├─ /api/_content/cache.1721052129200.json (3168ms)\r\n[nitro] ℹ Prerendered 1 routes in 204.492 seconds\r\n[nitro] ✔ Generated public .output/public\r\n[nitro] ℹ Building Nuxt Nitro server (preset: node-server)\r\n[nitro] ✔ Nuxt Nitro server built\r\n ├─ .output/server/chunks/_/empty.mjs (161 B) (151 B gzip)\r\n ├─ .output/server/chunks/_/empty.mjs.map (173 B) (145 B gzip)\r\n ├─ .output/server/chunks/_/error-500.mjs (4.83 kB) (2.05 kB gzip)\r\n ├─ .output/server/chunks/_/error-500.mjs.map (190 B) (157 B gzip)\r\n ├─ .output/server/chunks/_/icons.mjs (983 kB) (251 kB gzip)\r\n ├─ .output/server/chunks/_/icons.mjs.map (7.35 kB) (118 B gzip)\r\n ├─ .output/server/chunks/_/icons2.mjs (7.25 MB) (2.65 MB gzip)\r\n ├─ .output/server/chunks/_/icons2.mjs.map (8.74 kB) (121 B gzip)\r\n ├─ .output/server/chunks/_/icons3.mjs (893 kB) (218 kB gzip)\r\n ├─ .output/server/chunks/_/icons3.mjs.map (8.83 kB) (121 B gzip)\r\n ├─ .output/server/chunks/_/icons4.mjs (1.76 MB) (275 kB gzip)\r\n ├─ .output/server/chunks/_/icons4.mjs.map (16.9 kB) (129 B gzip)\r\n ├─ .output/server/chunks/_/index_bg.mjs (1.06 MB) (435 kB gzip)\r\n ├─ .output/server/chunks/_/index_bg.mjs.map (110 B) (103 B gzip)\r\n ├─ .output/server/chunks/_/node.mjs (176 B) (156 B gzip)\r\n ├─ .output/server/chunks/_/node.mjs.map (216 B) (170 B gzip)\r\n ├─ .output/server/chunks/_/node2.mjs (169 B) (152 B gzip)\r\n ├─ .output/server/chunks/_/node2.mjs.map (210 B) (167 B gzip)\r\n ├─ .output/server/chunks/_/pure.mjs (2.06 kB) (903 B gzip)\r\n ├─ .output/server/chunks/_/pure.mjs.map (178 B) (150 B gzip)\r\n ├─ .output/server/chunks/_/renderer.mjs (14.8 kB) (4.3 kB gzip)\r\n ├─ .output/server/chunks/_/renderer.mjs.map (1.27 kB) (287 B gzip)\r\n(...)\r\n```\r\n\r\nNote the very large IconsX.mjs files with the new module (I'm assuming it's caching the icons locally maybe?)\r\n\r\nBut what we find very strange is that the delay is apparently when pre-rendering the endpoint from nuxt-content that went from 37 to 204 seconds (!)\r\n\r\nAny ideas why this can be happening or how we can speed this up?\r\n\r\nThank you, cheers.\r\n\r\n",[],203,"@nuxt/icon greatly increases build prerender time vs nuxt-icon","2024-07-18T22:45:11Z","https://github.com/nuxt/icon/issues/203",0.7144669,["Reactive",2963],{},["Set"],["ShallowReactive",2966],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fIXcITXKRudhRdm63835vw9e-tBWal-Lz3nlBFpReqzQ":-1},"/nuxt/fonts/181"]