\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[2927,2930],{"name":2928,"color":2929},"enhancement","a2eeef",{"name":2914,"color":2915},3868,"Allow assigning IDs to Nuxt UI Tab panels for scroll targeting","2025-04-12T08:35:52Z","https://github.com/nuxt/ui/issues/3868",0.6638386,{"description":2937,"labels":2938,"number":2941,"owner":2917,"repository":2942,"state":2943,"title":2944,"updated_at":2945,"url":2946,"score":2947},"",[2939],{"name":2928,"color":2940},"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.6339708,{"description":2949,"labels":2950,"number":2941,"owner":2917,"repository":2954,"state":2943,"title":2955,"updated_at":2956,"url":2957,"score":2947},"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```",[2951],{"name":2952,"color":2953},"vitest-environment","b60205","test-utils","typecheck issues with defineVitestConfig?","2023-12-02T23:35:07Z","https://github.com/nuxt/test-utils/issues/611",{"description":2959,"labels":2960,"number":2965,"owner":2917,"repository":2918,"state":2943,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Description\n\nIt's shorter and can save traffic.\n\n### Additional context\n\n_No response_",[2961,2962],{"name":2928,"color":2929},{"name":2963,"color":2964},"v3","49DCB8",3250,"Use `foo-(--bar)` instead of `foo-[var(--bar)]` for tailwindcss classes","2025-02-07T10:24:17Z","https://github.com/nuxt/ui/issues/3250",0.63461685,{"description":2971,"labels":2972,"number":2973,"owner":2917,"repository":2942,"state":2943,"title":2974,"updated_at":2975,"url":2976,"score":2977},"On the 'Enterprise Jobs' page, location badges were closely together on mobile screens. I removed the `mr-3` class from the badge element and placed the badges inside a parent `\u003Cdiv>` with the classes` flex`, `flex-wrap`, and `gap-3` Now it won't stick together and will look good on mobile devices.\r\n\r\n| **BEFORE** | **AFTER** | \r\n|-------- | ------ | \r\n|  |  |\r\n\r\n\r\n\r\n\n```[tasklist]\n### Tasks\n```\n",[],1403,"Spacing issue with Location badges on 'Enterprise Jobs' page for mobile screens","2024-09-19T19:38:43Z","https://github.com/nuxt/nuxt.com/issues/1403",0.6395113,{"description":2979,"labels":2980,"number":2986,"owner":2917,"repository":2918,"state":2943,"title":2987,"updated_at":2988,"url":2989,"score":2990},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v18.20.5\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: default\n- Runtime Modules: nuxt-vuefire@1.0.4, @nuxt/ui@3.0.0-alpha.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\n\n\n\n\n```\n \u003CUTooltip :delay-duration=\"0\" :text=\"`R$ ${transactionCost.brl}`\">\n \u003CUIcon class=\"text-yellow-500 text-xs\" name=\"i-lucide-coins\" />\n \u003Cp class=\"text-neutral-200 text-xs\">\n {{ transactionCost.credits }}\n \u003C/p>\n\u003C/UTooltip>\n```\n\n``` \n\u003CNuxtLayout>\n \u003CUApp :toaster=\"{ position: 'top-right' }\">\n \u003CNuxtPage />\n \u003C/UApp>\n\u003C/NuxtLayout>\n```\n\n\n### Description\n\nThe `app.vue` is already using the `UApp`. When I try to add a `UTooltip` inside the modal, it throw an error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```\nUncaught (in promise) Error: Injection `Symbol(TooltipProviderContext)` not found. Component must be used within `TooltipProvider`\n```",[2981,2982,2985],{"name":2908,"color":2909},{"name":2983,"color":2984},"needs reproduction","CB47CF",{"name":2963,"color":2964},2801,"[v3][UTooltip] `UTooltip` inside `UModal` causing error","2025-02-06T15:28:30Z","https://github.com/nuxt/ui/issues/2801",0.6421014,{"description":2992,"labels":2993,"number":2999,"owner":2917,"repository":2917,"state":2943,"title":3000,"updated_at":3001,"url":3002,"score":3003},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.3.0\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: compatibilityDate, devtools, future, vite, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.1.3, nuxt-svgo@4.2.2, @nuxt/image@1.10.0\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\n```ts\n\u003Cscript setup lang=\"ts\">\nconst page = useState('movie-page', () => 1)\nconst data = useState\u003CMovie[]>('movie-data', () => [])\n\nconst { pending, execute } = await useFetch\u003CListResponse\u003CMovie>>('/api/tmdb/discover/movie', {\n query: {\n page,\n },\n async onResponse({ response }) {\n data.value.push(...response._data.results)\n },\n immediate: false,\n})\n\nif (data.value.length === 0)\n execute()\n\nconst pageContainer = useTemplateRef('pageContainer')\n\nonMounted(() => {\n const scrollContainer = document.getElementById('scrollContainer')\n scrollContainer?.addEventListener('scroll', () => {\n if (!pending.value && pageContainer.value && window.innerHeight + 1000 > pageContainer.value?.getBoundingClientRect().bottom) {\n page.value++\n }\n })\n})\n\u003C/script>\n```\n\n### Describe the bug\n\nI want to create an infinite scrollable page. To do so, I need to store the received data of `useFetch` in an array.\nSince I want to be able to navigate to another page and go back, without refetching all data, I use `useState`.\n\nHowever, when navigating back, `useFetch` would trigger again (with previous page value) if I use `immediate: true.` Therefore `immediate: false` is set and we manually call execute to fetch data on first page load.\n\nin the scroll listener, `page++` is called. The strange thing is:\n* On first page load, this is enough to retrigger fetching data. Not needing to call `execute()` manually.\n* Once navigated away and returning to the page, the `page` value is increased by the event listener (so still working), but `useFetch` does not trigger anymore.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2994,2997],{"name":2995,"color":2996},"pending triage","E99695",{"name":2983,"color":2998},"FBCA04",32467,"inconsistent behaviour useFetch","2025-06-24T21:21:12Z","https://github.com/nuxt/nuxt/issues/32467",0.6432044,{"description":3005,"labels":3006,"number":3011,"owner":2917,"repository":2917,"state":2943,"title":3012,"updated_at":3013,"url":3014,"score":3015},"### Environment\r\n\r\nNuxt project info: 12:42:28\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.2.3`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@8.11.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/beyer-johannes/use-fetch-pending-initial-true\r\n\r\n### Describe the bug\r\n\r\nUsing useFetch with {immediate:false} option is initial true.\r\n\r\n```\r\nconst { pending, execute } = useFetch(\r\n \"https://api.chucknorris.io/jokes/random\",\r\n {\r\n immediate: false,\r\n }\r\n);\r\n\r\n// pending.value === true without execute call.\r\n```\r\n\r\nIt should be `false` initial to make it useable. If its true, and I use it in a `\u003Cinput type=\"text\" :disabled=\"pending\"/>`, the input field is disabled on first visible moment, which's a wrong ux.\r\n\r\n### Additional context\r\n\r\nI tested vueUse's isFetching property in a empty vue environment and it is false per default.\r\n\r\n```\r\nimport { useFetch } from \"@vueuse/core\";\r\n\r\nconst { isFetching, execute } = useFetch(\r\n \"https://api.chucknorris.io/jokes/random\",\r\n {\r\n immediate: false,\r\n }\r\n);\r\n\r\n// isFetching.value === false\r\n```\r\n\r\n### Logs\r\n\r\n_No response_",[3007,3010],{"name":3008,"color":3009},"3.x","29bc7f",{"name":2995,"color":2996},19333,"UseFetch pending is initial true with {immediate: false} option","2023-11-15T20:53:47Z","https://github.com/nuxt/nuxt/issues/19333",0.64641494,{"description":3017,"labels":3018,"number":3021,"owner":2917,"repository":2917,"state":2943,"title":3022,"updated_at":3023,"url":3024,"score":3025},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.17.1`\r\n- Nuxt Version: `3.2.2`\r\n- Nitro Version: `2.2.2`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `modules`, `css`, `app`, `experimental`, `imports`, `nitro`, `typescript`\r\n- Runtime Modules: `@pinia/nuxt@0.4.7`, `@nuxtjs/tailwindcss@6.4.1`\r\n- Build Modules: \n\n### Reproduction\n\n\r\n```\r\n// before refresh call asyncData a pending must be false\r\nconst { pending: isLoadingOne, refresh: fetchOne } = useFetch('https://jsonplaceholder.typicode.com/todos/1', { immediate: false });\r\n\r\n// before refresh call asyncData a pending must be false | perhaps a controversial case\r\nconst { pending: isLoadingTwo, refresh: fetchTwo } = await useFetch('https://jsonplaceholder.typicode.com/todos/2', { immediate: false });\r\n```\r\n\r\nSee full code: https://stackblitz.com/edit/nuxt-starter-9uxzmd?file=app.vue\n\n### Describe the bug\n\nUntil the request is forcibly invoked, it is assumed that the waiting status should be false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3019,3020],{"name":3008,"color":3009},{"name":2995,"color":2996},19218,"`useFetch/useAsyncData`: BUG: when `immediate: false`, then `pending` is `true` before call `execute/refresh` (must to be false)","2023-12-20T16:49:10Z","https://github.com/nuxt/nuxt/issues/19218",0.64952004,["Reactive",3027],{},["Set"],["ShallowReactive",3030],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$feqngyFA0ObB2qMxzOqqr_E5eSbQl6QZSySpkBYXwhQs":-1},"/nuxt/ui/3602"]