`\n- [x] Head: `\u003Clink target />`\n- [x] Head: `\u003Cstlye scoped>`\n- [x] `useServerHead`\n- [x] `useServerHeadSafe`\n- [x] `useServerSeoMeta`\n- [x] `NuxtPlgin.ssr`\n- [x] `ConfigSchema.app.rootId`\n- [x] `ConfigSchema.app.teleportId`\n- [ ] `experimental.serverAppConfig`\n\nToDos:\n- Codemods?",[3151,3154],{"name":3152,"color":3153},"discussion","538de2",{"name":3155,"color":3156},"5.x","006b75",32960,"nuxt","open","Possible removals of deprecated features with v5","2025-08-22T09:32:56Z","https://github.com/nuxt/nuxt/issues/32960",0.6867075,{"description":3165,"labels":3166,"number":3170,"owner":3158,"repository":3158,"state":3159,"title":3171,"updated_at":3172,"url":3173,"score":3174},"### Describe the feature\n\nSince Nuxt 3.2, useFetch automatically passes request data to api call in an SSR context. The steps described in the docs aren't needed anymore: https://nuxt.com/docs/getting-started/data-fetching#example-pass-client-headers-to-the-api\r\n\r\nI think we shouldn't remove this section right away, but I propose to add a small alert in the docs saying that this change is not necessary anymore. \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).",[3167],{"name":3168,"color":3169},"documentation","5319e7",18927,"Documentation: Describe the new useFetch() behavior","2024-06-30T11:09:27Z","https://github.com/nuxt/nuxt/issues/18927",0.6881828,{"description":3176,"labels":3177,"number":3184,"owner":3158,"repository":3158,"state":3159,"title":3185,"updated_at":3186,"url":3187,"score":3188},"### Environment\n\nNuxt project info: 1:24:04 AM\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: yarn@1.22.21\r\n- Builder: -\r\n- User Config: devtools, runtimeConfig, routeRules, storyblok, modules, vue, vite, components, app, css, postcss\r\n- Runtime Modules: @pinia/nuxt@0.5.1, @storyblok/nuxt@6.0.10\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nAs far as i can tell this is pretty obvious and it seems to be happening in most nuxt3 projects.\n\n### Describe the bug\n\nIf `useLazyAsyncData` is used together with an `await` (to be able to show for example ghosts before the data has finished fetching) and together with a `getCachedData` function, the lazy async data is no longer returning pending and is instead waiting until the data is available (similar to how just a normal `useAsyncData` works).\n\n### Additional context\n\nWe found this issue while trying to use `getCachedData` to improve loading times since our app keeps fetching the same data on navigation.\n\n### Logs\n\n_No response_",[3178,3181],{"name":3179,"color":3180},"pending triage","E99695",{"name":3182,"color":3183},"needs reproduction","FBCA04",27351,"Using `getCachedData` together with `await useLazyAsyncData` causing it to not be pending anymore","2025-03-17T15:01:13Z","https://github.com/nuxt/nuxt/issues/27351",0.70113254,{"description":3190,"labels":3191,"number":3196,"owner":3158,"repository":3158,"state":3197,"title":3198,"updated_at":3199,"url":3200,"score":3201},"### 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_",[3192,3195],{"name":3193,"color":3194},"3.x","29bc7f",{"name":3179,"color":3180},19218,"closed","`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.6833678,{"description":3203,"labels":3204,"number":3206,"owner":3158,"repository":3158,"state":3197,"title":3207,"updated_at":3208,"url":3209,"score":3210},"### Describe the feature\r\n\r\nnode版本22,当创建完项目,安装依赖包提示:\r\nnpm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.\r\nnpm WARN deprecated npmlog@5.0.1: This package is no longer supported.\r\nnpm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported\r\nnpm WARN deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported\r\nnpm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported\r\nnpm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported\r\nnpm WARN deprecated are-we-there-yet@2.0.0: This package is no longer supported.\r\nnpm WARN deprecated gauge@3.0.2: This package is no longer supported.\r\n这依赖包不在提供长期支持,后面会不会影响项目?官方能处理下么\r\n\r\n### Additional information\r\n\r\n- [ ] 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).",[3205],{"name":3179,"color":3180},28155,"nuxt3最新版本安装依赖的时候提示好几个”no longer supported“","2024-10-11T19:05:08Z","https://github.com/nuxt/nuxt/issues/28155",0.68401164,{"description":3212,"labels":3213,"number":3227,"owner":3158,"repository":3158,"state":3197,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### Describe the feature\r\n\r\nCurrently, data fetching composables expose pending information in two ways: `pending` and `status` (`status.value === 'pending'`). It would be great to consider removing `pending` for consistency, which currently has a duplicated source of truth. As this would be a breaking change, it's probably best to address it in the next version of Nuxt.\r\n\r\n([Update in this comment](https://github.com/nuxt/nuxt/issues/25225#issuecomment-2182690498))\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).",[3214,3217,3220,3223,3226],{"name":3215,"color":3216},"good first issue","fbca04",{"name":3218,"color":3219},"🍰 p2-nice-to-have","0E8A16",{"name":3221,"color":3222},"⚠️ breaking change","D746A6",{"name":3224,"color":3225},"4.x","3B01A5",{"name":3155,"color":3156},25225,"Remove `pending` in favor of `status` in data fetching composables","2025-04-18T11:03:08Z","https://github.com/nuxt/nuxt/issues/25225",0.6846035,{"description":3233,"labels":3234,"number":3236,"owner":3158,"repository":3158,"state":3197,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Environment\n\n````\n------------------------------\n- Operating System: Ubuntu 24.04 LTS\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.6.12\n- Builder: -\n- User Config: extends, compatibilityDate\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n````\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/martinszeltins/nuxt-component-already-mounted\n\n### Describe the bug\n\nI have a simple Nuxt app. I have a page with a `\u003CNuxtLink>` to another page. On the other page there is a composable which makes 2 API requests when you enter the page. But I am getting this warning in the console:\n\n````\nuseSingleShipmentFormInitialData.ts:6 [nuxt] [useFetch] Component is already mounted, please use $fetch instead. See https://nuxt.com/docs/getting-started/data-fetching\nuseSingleShipmentFormInitialData\t@\tuseSingleShipmentFormInitialData.ts:6\nawait in useSingleShipmentFormInitialData\t\t\n(anonymous)\t@\tsingle-shipment.vue:10\nsetup\t@\tsingle-shipment.vue:10\nShow 39 more frames\n````\n\nThe component couldn't possibly be already mounted because both API calls are awaited one after another.\n\nI don't have anything fancy going on. I am using layers and I have set `asyncContext: true` in nuxt.config.ts. That's about it. Please see the reproduction.\n\n_Note: It may not work in Stackblitz, so you might need to download the repo and try it locally._\n\n**Screenshot:**\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3235],{"name":3179,"color":3180},31058,"Bug: [nuxt] [useFetch] Component is already mounted, please use $fetch instead","2025-08-20T11:14:15Z","https://github.com/nuxt/nuxt/issues/31058",0.6865288,{"labels":3242,"number":3247,"owner":3158,"repository":3158,"state":3197,"title":3248,"updated_at":3249,"url":3250,"score":3251},[3243,3244],{"name":3179,"color":3180},{"name":3245,"color":3246},"2.x","d4c5f9",10490,"Lot's of deprecation warning after fresh create-nuxt-app","2023-02-17T05:27:56Z","https://github.com/nuxt/nuxt/issues/10490",0.690676,{"labels":3253,"number":3256,"owner":3158,"repository":3158,"state":3197,"title":3257,"updated_at":3258,"url":3259,"score":3260},[3254,3255],{"name":3193,"color":3194},{"name":3179,"color":3180},13460,"useAsyncData changed behaviour","2023-01-19T16:58:59Z","https://github.com/nuxt/nuxt/issues/13460",0.69235754,{"description":3262,"labels":3263,"number":3265,"owner":3158,"repository":3158,"state":3197,"title":3266,"updated_at":3267,"url":3268,"score":3269},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v18.17.0`\n- Nuxt Version: `4.0.0-0`\n- CLI Version: `3.22.4`\n- Nitro Version: `-`\n- Package Manager: `pnpm@10.5.2`\n- Builder: `-`\n- User Config: `modules`, `pages`, `dir`, `typescript`\n- Runtime Modules: `()`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-pmvrs6vw?file=app.vue\n\n### Describe the bug\n\nWrong warn is given during `useFetch` or `useLazyFetch` execution on the server-side.\nIt was mentioned here https://github.com/nuxt/nuxt/issues/31211 but without fix in useLazyFetch.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nWARN [nuxt] useAsyncData must return a value (it should not be undefined) or the request may be duplicated on the client side.\n```",[3264],{"name":3179,"color":3180},31259,"Wrong warn is given during `useFetch` or `useLazyFetch` execution on the server-side.","2025-03-07T15:42:27Z","https://github.com/nuxt/nuxt/issues/31259",0.6937135,["Reactive",3271],{},["Set"],["ShallowReactive",3274],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fo9hdbuIIdg_6NdRRlrsUcFiXGTbeWBDYWlxiZstdDRI":-1},"/nuxt/nuxt/26560"]