`\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?",[3186,3187],{"name":3149,"color":3150},{"name":3188,"color":3189},"5.x","006b75",32960,"Possible removals of deprecated features with v5","2025-08-22T09:32:56Z","https://github.com/nuxt/nuxt/issues/32960",0.7705675,{"description":3196,"labels":3197,"number":3203,"owner":3152,"repository":3178,"state":3204,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Description\n\nAfter using the [Discord help area](https://discord.com/channels/473401852243869706/1375131221126021161) it seems that there's no callback function for dynamically created toasts (when using `useToast` composable).\n\nIIRC this used to be possible with the previous major version of Nuxt UI (using Notification, _I think_).\n\nUpdate: [here's](https://ui2.nuxt.com/components/notification#callback) how it worked previously.\n\n### Additional context\n\nIt would be helpful to have the ability to have a callback option that could be used whenever a specific toast is cleared (when using `useToast` and the `toast` clears through it's own timeout or the use dismissing it using the close button).\n\nThe Discord AI helper suggested watching all the toasts array, and then reacting when one is removed. Doing this each time would become rather time consuming and repetitive.",[3198,3199,3200],{"name":3146,"color":3173},{"name":3175,"color":3176},{"name":3201,"color":3202},"triage","ffffff",4206,"closed","[useToast] include callback when dynamically creating toasts","2025-05-29T10:18:14Z","https://github.com/nuxt/ui/issues/4206",0.7175193,{"description":3210,"labels":3211,"number":3222,"owner":3152,"repository":3152,"state":3204,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Describe the feature\n\nSeveral composable functions ( `useState`, `useFetch`, `useAsyncData`, `useLazyAsyncData`, `useLazyFetch`) provide auto-key generation that is unique to the file name and line number of the instance of function call. However, this makes it impossible to create your own wrappers around these functions, because then the auto-generated key will always be the same for any wrapper-function call.\r\n\r\n```ts\r\n// composables/useAsyncSpecifiedData.ts\r\nexport function useAsyncSpecifiedData(params) {\r\n\t// ... do some work\r\n\tconst handler = createHandler( params )\r\n\tconst options = createOptions( params )\r\n\treturn useAsyncData(handler, options) // \u003C- the unique key always generated exactly for this file+line\r\n}\r\n```\r\nI would like to have oportynity to somehow expand keyed functions with myown\r\nhttps://github.com/nuxt/framework/blob/51bc6e44fef6e4a249946ba910a497089b089a64/packages/vite/src/plugins/composable-keys.ts#L15-L17\r\n\r\nSo that nuxt will generates a unique key directly for the wrapper function call, which will be passed down in `useAsyncData`. Since it is work for `useLazyAsyncData`\r\nhttps://github.com/nuxt/framework/blob/51bc6e44fef6e4a249946ba910a497089b089a64/packages/nuxt/src/app/composables/asyncData.ts#L263-L274\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://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3212,3213,3216,3219],{"name":3146,"color":3147},{"name":3214,"color":3215},"good first issue","fbca04",{"name":3217,"color":3218},"3.x","29bc7f",{"name":3220,"color":3221},"🍰 p2-nice-to-have","0E8A16",12369,"Ability to add your own keyed functions ","2023-03-07T21:06:18Z","https://github.com/nuxt/nuxt/issues/12369",0.73999137,{"labels":3228,"number":3236,"owner":3152,"repository":3152,"state":3204,"title":3237,"updated_at":3238,"url":3239,"score":3240},[3229,3230,3233],{"name":3217,"color":3218},{"name":3231,"color":3232},"upstream","E8A36D",{"name":3234,"color":3235},"upstream-bug","B60205",13793,"Primevue: Toast duplicates elements after it","2023-01-19T17:06:05Z","https://github.com/nuxt/nuxt/issues/13793",0.75007343,{"labels":3242,"number":3248,"owner":3152,"repository":3152,"state":3204,"title":3249,"updated_at":3250,"url":3251,"score":3252},[3243,3244,3245],{"name":3146,"color":3147},{"name":3217,"color":3218},{"name":3246,"color":3247},"dx","C39D69",13963,"automatically generate unique keys for keyed composables","2023-01-19T17:11:03Z","https://github.com/nuxt/nuxt/issues/13963",0.7534618,{"description":3254,"labels":3255,"number":3260,"owner":3152,"repository":3178,"state":3204,"title":3261,"updated_at":3262,"url":3263,"score":3264},"### Environment\n\nHi, I just wanted to share that the styling on the docs website appears broken when viewed in Firefox. I checked on Chrome, and it displays correctly there.\n\nHere’s a screenshot:\n\n\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nN/A\n\n### Reproduction\n\nN/A\n\n### Description\n\nN/A\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3256,3259],{"name":3257,"color":3258},"bug","d73a4a",{"name":3175,"color":3176},3397,"Nuxt UI v3 docs styling broken","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3397",0.75622153,{"labels":3266,"number":3271,"owner":3152,"repository":3152,"state":3204,"title":3272,"updated_at":3273,"url":3274,"score":3275},[3267,3268],{"name":3146,"color":3147},{"name":3269,"color":3270},"2.x","d4c5f9",7753,"Components into root element","2023-02-15T00:59:50Z","https://github.com/nuxt/nuxt/issues/7753",0.75757766,["Reactive",3277],{},["Set"],["ShallowReactive",3280],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fxiajOCRMzxEPB8uU3VrmjKZ7676U4hoBkNLtaWmpFvs":-1},"/nuxt/ui/1706"]