\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```",[1984,1987,1990],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"v3","49DCB8",{"name":1991,"color":1992},"triage","ffffff",3607,"nuxt","ui","open","Background-Color for UTable","2025-03-18T15:08:25Z","https://github.com/nuxt/ui/issues/3607",0.6368044,{"description":2002,"labels":2003,"number":2007,"owner":1994,"repository":2008,"state":1996,"title":2009,"updated_at":2010,"url":2011,"score":2012},"When attempting to render a component for a whitebox test, the entire Nuxt environment is being loaded instead of just the component. This behavior is likely caused by the presence of an authentication guard in the project, which leads to redirection to the sign-in page during test execution.\r\n\r\n### Steps to Reproduce\r\nAccess the following StackBlitz link: [Reproduction Test](https://stackblitz.com/edit/nuxt-vitest-ewepwb?file=test%2Ftest.nuxt.spec.ts)\r\n\r\n### Expected Behavior\r\nThe test should only render the targeted component without triggering global route middleware or redirections.\r\n\r\n### Actual Behavior\r\nUpon running the test, the entire Nuxt environment is loaded, including global route middleware, leading to redirection to the sign-in page due to the presence of the authentication guard.\r\n\r\n### Additional Information\r\nNuxt project info: \r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.5.3\r\n- Nitro Version: 2.4.1\r\n- Package Manager: yarn@3.6.0\r\n- Builder: vite\r\n- User Config: alias, app, build, sourcemap, ssr, runtimeConfig, vite, css, modules, components, ignore, dayjs, typescript, experimental, devtools\r\n- Runtime Modules: dayjs-nuxt@1.1.2, nuxt-vitest@0.10.2, @pinia/nuxt@^0.4.11\r\n- Build Modules: -\r\n------------------------------",[2004],{"name":2005,"color":2006},"vitest-environment","b60205",526,"test-utils","Components tests it is triggering global route middleware","2024-12-22T21:23:11Z","https://github.com/nuxt/test-utils/issues/526",0.666041,{"description":2014,"labels":2015,"number":2019,"owner":1994,"repository":1994,"state":1996,"title":2020,"updated_at":2021,"url":2022,"score":2023},"### Environment\n\n```\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-rt2zig?file=pages%2Findex.vue\r\n\n\n### Describe the bug\n\nOn Page Load `Response` is null. But when changing something in code to trigger client refresh (i provided the console.log to trigger update), Response is given. \r\nIt works on page reload when using the doSuccess with another composable method.\r\n\r\nWhile debugging, it seems like that causes it:\r\n\r\nIn the described behaviour asyncData use `_nuxtOnBeforeMountCbs` to process the initialFetch\r\n\r\nhttps://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/composables/asyncData.ts#L372\r\n\r\nBut, what seems to be a bug, the line ([395](https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/composables/asyncData.ts#L395)) resolves in the given case the Promise where it isn´t processed ([359](https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/composables/asyncData.ts#L359)) yet.\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2016],{"name":2017,"color":2018},"pending triage","E99695",28485,"useFetch returns null used in component when on parent data is loaded via composable useFetch on route watch","2024-08-13T09:19:21Z","https://github.com/nuxt/nuxt/issues/28485",0.70423245,{"description":2025,"labels":2026,"number":2027,"owner":1994,"repository":2028,"state":1996,"title":2029,"updated_at":2030,"url":2031,"score":2032},"Hi there. Is there any way we could add a feature that minifies the CSS generated by this plugin and/or then extracts the code to a single separate CSS file, rather than having it all output in the ```\u003Chead>``` element?\n\nEven with...\n```javascript\nvite: {\n\tbuild: {\n\t\t\tassetsInlineLimit: 0, // default is 4096 (4 KiB); threshold to inline assets as base64 URLs\n\t\t\tcssCodeSplit: false, // if false, all CSS in the entire project will be extracted into a single CSS file\n\t}\n}\n``` \n...in my ```nuxt.config.ts``` file, the icon-related CSS code from this plugin still gets output onto my pages un-minified *and* un-extracted.\n\nThanks. :-)\n",[],327,"icon","Don't force CSS to be inline","2024-12-22T00:14:16Z","https://github.com/nuxt/icon/issues/327",0.7072996,{"description":2034,"labels":2035,"number":2043,"owner":1994,"repository":2008,"state":2044,"title":2045,"updated_at":2046,"url":2047,"score":2048},"Because `happy-dom` is not fully compatible with `jsdom`, we can't use, for example, `@testing-library/jest-dom` within the Nuxt environment. \r\nI suggest to add possibility to replace `happy-dom` with `jsdom`, `@happy-dom/jest-environment` etc.",[2036,2039,2042],{"name":2037,"color":2038},"enhancement","a2eeef",{"name":2040,"color":2041},"good first issue","7057ff",{"name":2005,"color":2006},553,"closed","Add option to replace `happy-dom` with `jsdom`","2023-12-02T00:37:13Z","https://github.com/nuxt/test-utils/issues/553",0.66072196,{"description":2050,"labels":2051,"number":2007,"owner":1994,"repository":2052,"state":2044,"title":2053,"updated_at":2054,"url":2055,"score":2012},"https://www.figma.com/file/OLlmzoVQ7FSBh4FJJORNpl/%F0%9F%96%A5---nuxt.com?node-id=4854%3A41400\n\nhttps://www.figma.com/file/OLlmzoVQ7FSBh4FJJORNpl/%F0%9F%96%A5---nuxt.com?node-id=4854%3A42110\n\nhttps://github.com/nuxt/nuxtjs.org/tree/main/content/_collections/partners",[],"nuxt.com","[Community] Partners integration `/community/partners`","2023-02-15T12:32:29Z","https://github.com/nuxt/nuxt.com/issues/526",{"description":2057,"labels":2058,"number":2061,"owner":1994,"repository":2052,"state":2044,"title":2062,"updated_at":2063,"url":2064,"score":2065},"",[2059],{"name":2037,"color":2060},"1ad6ff",611,"[Resources] Refactor showcases into a composable","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/611",0.68243635,{"description":2067,"labels":2068,"number":2061,"owner":1994,"repository":2008,"state":2044,"title":2070,"updated_at":2071,"url":2072,"score":2065},"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```",[2069],{"name":2005,"color":2006},"typecheck issues with defineVitestConfig?","2023-12-02T23:35:07Z","https://github.com/nuxt/test-utils/issues/611",{"description":2074,"labels":2075,"number":2080,"owner":1994,"repository":1994,"state":2044,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### Environment\n\nrc-13\r\nnode-18\n\n### Reproduction\n\n//composable\r\n```javascript\r\nconst myfetch = async (url,options,emits) => {\r\n const { data, pending, error, refresh } = await useFetch(url, {\r\n \r\n ...options,\r\n baseURL: useRuntimeConfig().API_URL, \r\n initialCache: false,\r\n headers: new Headers({ 'authorization': (process.client)?localStorage.getItem(\"token\"):''}),\r\n onResponse ({ response }) {\r\n return response._data\r\n },\r\n onResponseError ({ response }) {\r\n return response._data\r\n }\r\n })\r\n const resData = data.value\r\n \r\n return resData\r\n }\r\n```\r\n//component 1\r\n\r\n```javascript\r\n\u003Cscript setup>\r\ngetAllItems();\r\nasync function getAllItems() {\r\n let response = await myfetch('/article/artPosts?' +\r\n 'page=' + page.value + '&' +\r\n 'artPostGroup=' + artPostGroup.value + '&' +\r\n 'limit=' + limit.value, {\r\n method: 'GET'\r\n });\r\n if (response.data)\r\n list.value = response.data.docs;\r\n pages.value = response.data.pages;\r\n}\r\n\u003C/script>\r\n```\r\n\r\n//component 2\r\n\r\n```javascript\r\n\u003Cscript setup>\r\ngetAllItems();\r\nasync function getAllItems() {\r\n let response = await myfetch('/store/storeCourses?' +\r\n 'page=' + page.value + '&' +\r\n 'storeCourseGroup=' + storeCourseGroup.value + '&' +\r\n 'limit=' + limit.value, {\r\n method: 'GET'\r\n });\r\n if (response.data)\r\n list.value = response.data.docs;\r\n pages.value = response.data.pages;\r\n}\r\n\u003C/script>\r\n```\r\n//home.vue\r\n```javascript\r\n\u003Cdiv>\r\n\u003Ccomponent1>\u003C/component1>\r\n\u003Ccomponent2>\u003C/component2>\r\n\u003C/div>\r\n```\n\n### Describe the bug\n\nthe bug is here...\r\nin the page load:\r\nresponse of component1 is the same as response of component2...\r\n\r\n\r\nwhen i use $fetch instead of useFetch, it works good but it makes another problem for me...\r\n\r\non refreshing page,it send a request twice to server\r\n\n\n### Additional context\n\nhow can i write function in composables?\n\n### Logs\n\n_No response_",[2076,2079],{"name":2077,"color":2078},"3.x","29bc7f",{"name":2017,"color":2018},15451,"UseFetch() calling multiple request, only the last data is fetched and $fetch send requests twice","2023-01-19T17:50:37Z","https://github.com/nuxt/nuxt/issues/15451",0.6843025,{"description":2086,"labels":2087,"number":2089,"owner":1994,"repository":2090,"state":2044,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### 🐛 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.",[2088],{"name":1985,"color":1986},442,"scripts","Clarity proxy not working","2025-04-16T08:12:32Z","https://github.com/nuxt/scripts/issues/442",0.6852626,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"PRNi4LkC9GVdVUOYjbgJqQJhC98GvjXeXt7vKW-o4ko":-1},"/nuxt/ui/3130"]