\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```",[2016,2019,2020],{"name":2017,"color":2018},"bug","d73a4a",{"name":2002,"color":2003},{"name":2005,"color":2006},3607,"Background-Color for UTable","2025-03-18T15:08:25Z","https://github.com/nuxt/ui/issues/3607",0.7244317,{"description":2027,"labels":2028,"number":1987,"owner":1988,"repository":2029,"state":2030,"title":2031,"updated_at":2032,"url":2033,"score":1994},"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","closed","[Community] Partners integration `/community/partners`","2023-02-15T12:32:29Z","https://github.com/nuxt/nuxt.com/issues/526",{"description":2035,"labels":2036,"number":2049,"owner":1988,"repository":1988,"state":2030,"title":2050,"updated_at":2051,"url":2052,"score":2053},"### Environment\r\n\r\nnuxt: 3.8.2\r\n\r\n### Reproduction\r\n\r\n```ts\r\nconst newOptions: UseFetchOptions\u003CT> = {\r\n baseURL: BASE_URL,\r\n method,\r\n // headers: { ...normalParams },\r\n onRequest ({ options }) {\r\n options.headers = {\r\n ...optionsHeader,\r\n 'Content-Type': 'application/json'\r\n }\r\n },\r\n async onResponse ({ response }) {\r\n const responseData = typeof response._data === 'string' ? JSON.parse(response._data) : response._data\r\n const { code } = responseData\r\n if (code === RESPOND.SUCCESS) {\r\n return response._data\r\n } else if (NOT_FOUND_CODES.includes(code)) {\r\n navigateTo('/404/')\r\n return Promise.reject(response._data)\r\n } else {\r\n if (LOGOUT_CODES.includes(code)) {\r\n user.clearUserInfo()\r\n }\r\n return response._data\r\n }\r\n },\r\n onResponseError ({ response }) {\r\n return response?._data ?? null\r\n },\r\n ...options\r\n }\r\n\r\nuseFetch(url, newOptions)\r\n .then((res) => {\r\n if (typeof res.data.value === 'string') {\r\n resolve(JSON.parse(res.data.value))\r\n } else {\r\n resolve(res.data.value)\r\n }\r\n })\r\n .catch((error) => {\r\n reject(error)\r\n })\r\n```\r\n\r\n### Describe the bug\r\n\r\n\r\n\r\n\r\nthe same request in production environment,status is error and data is null, but in development environment i got data and status is success.\r\nonResponse and onResponseError is not executed.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2037,2040,2043,2046],{"name":2038,"color":2039},"3.x","29bc7f",{"name":2041,"color":2042},"pending triage","E99695",{"name":2044,"color":2045},"needs reproduction","FBCA04",{"name":2047,"color":2048},"closed-by-bot","ededed",25032,"useFetch request status is error, data is null","2024-01-11T01:49:31Z","https://github.com/nuxt/nuxt/issues/25032",0.6723859,{"description":2055,"labels":2056,"number":2059,"owner":1988,"repository":2008,"state":2030,"title":2060,"updated_at":2061,"url":2062,"score":2063},"### Environment\n\nnuxt: 3.15.2\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha11\n\n### Reproduction\n\nself explanatory\n\n### Description\n\n\"Buttons do not have an accessible name\"\n\nComponent: USelect - Missing name/label for aria-label\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2057,2058],{"name":2017,"color":2018},{"name":2002,"color":2003},3130,"Missing Aria-Label on USelect Component","2025-02-21T11:26:36Z","https://github.com/nuxt/ui/issues/3130",0.6724178,{"description":2065,"labels":2066,"number":2069,"owner":1988,"repository":2029,"state":2030,"title":2070,"updated_at":2071,"url":2072,"score":2073},"",[2067],{"name":1999,"color":2068},"1ad6ff",611,"[Resources] Refactor showcases into a composable","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/611",0.69956726,{"description":2075,"labels":2076,"number":2069,"owner":1988,"repository":1989,"state":2030,"title":2078,"updated_at":2079,"url":2080,"score":2073},"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```",[2077],{"name":1985,"color":1986},"typecheck issues with defineVitestConfig?","2023-12-02T23:35:07Z","https://github.com/nuxt/test-utils/issues/611",{"description":2082,"labels":2083,"number":2085,"owner":1988,"repository":2086,"state":2030,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### 🐛 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.",[2084],{"name":2017,"color":2018},442,"scripts","Clarity proxy not working","2025-04-16T08:12:32Z","https://github.com/nuxt/scripts/issues/442",0.7087266,{"description":2092,"labels":2093,"number":2100,"owner":1988,"repository":1988,"state":2030,"title":2101,"updated_at":2102,"url":2103,"score":2104},"### Describe the feature\r\n\r\nWhen developing a rest API, it's considered good to use semantic status codes for different response types. So I do in my API routes:\r\n\r\n```ts\r\nimport { setResponseStatus } from 'h3'\r\n\r\nconst enum OperationResultKind {\r\n Created = 'Created',\r\n AlreadyExists = 'AlreadyExists',\r\n InvalidData = 'InvalidData',\r\n}\r\n\r\ntype OperationResult =\r\n| { kind: OperationResultKind.Created; user: User }\r\n| { kind: OperationResultKind.AlreadyExists }\r\n| { kind: OperationResultKind.InvalidData; problems: ValidationProblem[] }\r\n\r\nexport default defineEventHandler(event => {\r\n const unvalidatedData = readBody(event)\r\n const validationResult = // some validation stuff\r\n\r\n if (!validationResult.success) {\r\n setResponseStatus(event, 400)\r\n return { kind: OperationResultKind.InvalidData, problems: validationResult.problems }\r\n }\r\n\r\n const { data } = validationResult\r\n \r\n try {\r\n const insertedUser = await insertIntoDb(data)\r\n setResponseStatus(event, 203)\r\n return { kind: OperationResultKind.Created; user: insertedUser }\r\n } catch (e) {\r\n if (/* some error checking */) {\r\n setResponseStatus(event, 409)\r\n return { kind: OperationResultKind.AlreadyExists }\r\n }\r\n \r\n throw e\r\n }\r\n})\r\n```\r\n\r\nHowever, when fetching this route with `useFetch`, I end up with `InvalidData` and `AlreadyExists` errors being in the `error` ref. The thing is that these variants are some type of domain errors and I get no typings for them. The other thing is that the `data` ref is of type `OperationResult`, but it only may contain the `Created` variant so I end up using `as` to convert types which is not good. \r\n\r\nI could return only 2xx status codes to resolve this issue, but I might want to reuse this API in many different projects in the future so status codes must be semantic.\r\n\r\nI think that one option for resolving that may be adding some interceptor concept such as in Axios:\r\n```ts\r\naxios.get('/user/12345', {\r\n validateStatus: function (status) {\r\n return status \u003C 500; // Resolve only if the status code is less than 500\r\n }\r\n})\r\n```\r\n\r\nAlso one would want to use this validation interceptor globally, so it's worth adding this to `nuxt.config.ts`.\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2094,2096,2097],{"name":1999,"color":2095},"8DEF37",{"name":2038,"color":2039},{"name":2098,"color":2099},"upstream","E8A36D",18713,"Add an option to `useFetch` to not consider non-5xx status codes as errors","2023-10-22T09:04:12Z","https://github.com/nuxt/nuxt/issues/18713",0.7090395,["Reactive",2106],{},["Set"],["ShallowReactive",2109],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"iIJ0tyaENNECMQQ-XCKLLqZsydr54GDCELcb8Shc-mY":-1},"/nuxt/test-utils/553"]