\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[1984,1987],{"name":1985,"color":1986},"enhancement","a2eeef",{"name":1988,"color":1989},"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.74145526,{"description":1999,"labels":2000,"number":2001,"owner":1991,"repository":2002,"state":2003,"title":2004,"updated_at":2005,"url":2006,"score":2007},"Use the same component for aside filters on modules and showcase + Add icons on modules\n\n- [x] Merge components\n- [ ] Refactor types\n- [ ] Add icons",[],1149,"nuxt.com","closed","[Aside] Use same component","2023-06-06T12:14:41Z","https://github.com/nuxt/nuxt.com/issues/1149",0.7113719,{"description":2009,"labels":2010,"number":2014,"owner":1991,"repository":2002,"state":2003,"title":2015,"updated_at":2016,"url":2017,"score":2018},"\n",[2011],{"name":2012,"color":2013},"bug","ff281a",522,"Checkboxes broken on dark mode","2022-05-23T15:16:45Z","https://github.com/nuxt/nuxt.com/issues/522",0.71488893,{"description":2020,"labels":2021,"number":2014,"owner":1991,"repository":2028,"state":2003,"title":2029,"updated_at":2030,"url":2031,"score":2018},"Hey I was using `mockNuxtImport` to mock 2 different users from a nuxt composable in the same test file. It seems to use the last `mockNuxtImport` that is called in the file, not the one scoped to the test.\r\n\r\n```ts\r\nit('renders the users email', () => {\r\n\tmockNuxtImport('useSupabaseUser', () => {\r\n\t\treturn () => mockUser\r\n\t})\r\n\r\n\trender(User)\r\n\r\n\texpect(screen.getByText('jdoe@gmail.com')).toBeInTheDocument()\r\n})\r\n\r\nit('renders the Error when there is no user', () => {\r\n\tmockNuxtImport('useSupabaseUser', () => {\r\n\t\treturn () => {}\r\n\t})\r\n\r\n\trender(User)\r\n\r\n\texpect(screen.getByText('Error')).toBeInTheDocument()\r\n})\r\n```\r\n\r\nThe first test fails here as it thinks `useSupabaseUser` returns {}\r\n\r\nI did manage to get this working with a global variable:\r\n\r\n```ts\r\nlet mockUser = { id: 1, name: 'John Doe', email: 'jdoe@gmail.com' }\r\n\r\nmockNuxtImport('useSupabaseUser', () => {\r\n\treturn () => mockUser\r\n})\r\n\r\nit('renders the users email', () => {\r\n\trender(User)\r\n\r\n\texpect(screen.getByText('jdoe@gmail.com')).toBeInTheDocument()\r\n})\r\n\r\nit('renders the Error when there is no user', () => {\r\n\tmockUser = {}\r\n\r\n\trender(User)\r\n\r\n\texpect(screen.getByText('Error')).toBeInTheDocument()\r\n})\r\n```\r\n\r\nNot really sure if this is expected, it seems a little strange to me, so figured I post my findings.",[2022,2025],{"name":2023,"color":2024},"documentation","0075ca",{"name":2026,"color":2027},"vitest-environment","b60205","test-utils","Mocking multiple iterations of nuxt imports in the same test file","2024-01-24T12:25:29Z","https://github.com/nuxt/test-utils/issues/522",{"description":2033,"labels":2034,"number":2044,"owner":1991,"repository":1991,"state":2003,"title":2045,"updated_at":2046,"url":2047,"score":2048},"### Describe the feature\n\nWhen usefetch makes network requests, the parameters of the second request depend on the response result of the first interface. If usefetch is nested, an error will be returned, indicating that usefetch can only be used by setup. If $fetch is used, both client and server will be triggered once. What's the solution\r\n\r\n\n\n### Additional information\n\n- [X] 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).",[2035,2038,2041],{"name":2036,"color":2037},"3.x","29bc7f",{"name":2039,"color":2040},"pending triage","E99695",{"name":2042,"color":2043},"needs reproduction","FBCA04",26529,"When usefetch makes network requests, the parameters of the second request depend on the response result of the first interface. If usefetch is nested, an error will be returned, indicating that usefetch can only be used by setup. If $fetch is used, both client and server will be triggered once. What's the solution","2024-03-30T01:44:56Z","https://github.com/nuxt/nuxt/issues/26529",0.7182069,{"description":2050,"labels":2051,"number":2057,"owner":1991,"repository":1991,"state":2003,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### Describe the feature\n\nWe are using Laravel Precognition feature to validate forms server-side before we actually submit them.\r\n\r\nBy default we use useFetch, and simply add the header required by this feature to perform the validation instead of the actual request.\r\nSince useFetch deduplicates identical requests by default, our validation request is actually the request that gets cached. This means that when we actually want to make the request, we just get our cached response back instantly, which does not actually do anything.\r\n\r\nWe traced this down to this line https://github.com/nuxt/nuxt/blob/876fa7f3136129097ae3d04acff1dac87f2d2a90/packages/nuxt/src/app/composables/fetch.ts#L88\r\n\r\nSince we don't actually change the body, url, or params, the cache is hit.\r\n\r\nI think it would be sensible to also include the headers in the caching key.\n\n### Additional information\n\n- [X] 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).",[2052,2053,2055],{"name":2036,"color":2037},{"name":2012,"color":2054},"d73a4a",{"name":2056,"color":2043},"🔨 p3-minor",23455,"Consider headers in useFetch key","2023-10-26T20:10:49Z","https://github.com/nuxt/nuxt/issues/23455",0.7199647,{"description":2063,"labels":2064,"number":2067,"owner":1991,"repository":1991,"state":2003,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v19.5.0`\r\n- Nuxt Version: `3.2.3`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@9.3.1`\r\n- Builder: `vite`\r\n- User Config: `modules`, `runtimeConfig`, `content`, `image`, `googleFonts`\r\n- Runtime Modules: `@nuxt/content@2.5.2`, `@nuxtjs/google-fonts@3.0.0`, `@nuxt/image-edge@1.0.0-27968280.9739e4d`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nThe following code fetches search results. It's automatically refreshed when the searchquery ref is changed.\r\n\r\n```javascript\r\nconst navSearchAPICall = useLazyAsyncData(\r\n 'searchWorking',\r\n () => $fetch('/api/search', {\r\n params: {\r\n query: searchquery.value\r\n }\r\n }),\r\n { \r\n server: false,\r\n watch: [searchquery]\r\n }\r\n)\r\n```\r\n\r\nThis works as expected. But the following code, wich should behave the same according to the documentation, does not work. The request is refreshed when the searchquery ref changes, but the query parameters stay the same.\r\n\r\n```javascript\r\nconst searchAPICall = useLazyFetch('/api/search', {\r\n key: 'searchNotWorking',\r\n params: {\r\n query: searchquery.value\r\n },\r\n server: false,\r\n watch: [searchquery]\r\n }\r\n)\r\n```\r\n\r\n\r\n\n\n### Describe the bug\n\nAs described in the reproduction, when using `useLazyAsyncData`, the request is refreshed with updated query parameters according to the searchquery ref. \r\n\r\nBut when using `useLazyFetch`, the request is refreshed but sent with unchanged query parameters.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2065,2066],{"name":2036,"color":2037},{"name":2039,"color":2040},19665,"useLazyFetch does not behave like useLazyAsyncData","2023-03-14T11:09:45Z","https://github.com/nuxt/nuxt/issues/19665",0.72181845,{"description":2073,"labels":2074,"number":2076,"owner":1991,"repository":2077,"state":2003,"title":2078,"updated_at":2079,"url":2080,"score":2081},"### 🐛 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.",[2075],{"name":2012,"color":2054},442,"scripts","Clarity proxy not working","2025-04-16T08:12:32Z","https://github.com/nuxt/scripts/issues/442",0.7225321,{"description":2083,"labels":2084,"number":2087,"owner":1991,"repository":1991,"state":2003,"title":2088,"updated_at":2089,"url":2090,"score":2091},"### Describe the feature\n\n我重新封装了一下useFetch,在使用的时候,通过onRequest添加Authorization。\r\n等我在组件内使用的时候,为了不触发依赖改变的自动请求,我就在onRequest函数内注入body参数,这样表单数据修改的时候,不会触发自动请求。\r\n\r\n由于onRequest是一个函数,所以我需要自己进行嵌套函数。\r\n如果是一个数组,就可以在数组随便push了。\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).",[2085,2086],{"name":2036,"color":2037},{"name":2039,"color":2040},19046,"useFetch的几个钩子现在是函数,希望变成数组形势","2023-02-16T08:44:15Z","https://github.com/nuxt/nuxt/issues/19046",0.72779393,{"description":2093,"labels":2094,"number":2097,"owner":1991,"repository":1991,"state":2003,"title":2098,"updated_at":2099,"url":2100,"score":2101},"### Environment\r\n\r\nwindows\r\nNodejs 18.14.0\r\nNuxt3.6.3\r\n\r\n### Reproduction\r\n\r\n```\r\nconst {data, error} = await useFetch(\"https://api.com/get\", {\r\n params: {\r\n path: \"path1%7Cpath2\"\r\n }\r\n});\r\nconsole.log(data, error);\r\n```\r\n\r\n### Describe the bug\r\n\r\nuseFetch will auto encoded params's special characters, like % will be encoded to %25 :\r\n\r\nwhich means server actually request url is: https://api.com/get?path=path1%257Cpath2\r\n\r\nWhile the character \"|\" will not be encoded to \"%7C\", this is confusing.\r\nIs this a bug or feature?\r\n\r\nBy the way, my workaround is concating params in url instead of using params option, like this: \r\n```\r\nconst {data, error} = await useFetch(\"https://api.com/get?path=path1%7Cpath2\");\r\nconsole.log(data, error);\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_\r\n```[tasklist]\r\n### Tasks\r\n```\r\n",[2095,2096],{"name":2036,"color":2037},{"name":2039,"color":2040},22186,"useFetch corrupting params containing \"%\"","2023-07-18T09:08:44Z","https://github.com/nuxt/nuxt/issues/22186",0.7292704,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"L6vR_lHgLAZcPybp79VEBov8lUh_V2HJ0k8fKzT5l5o":-1},"/nuxt/test-utils/586"]