`\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?",[3192,3195],{"name":3193,"color":3194},"discussion","538de2",{"name":3196,"color":3197},"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.73409486,{"description":3206,"labels":3207,"number":3212,"owner":3199,"repository":3199,"state":3200,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### Describe the feature\r\n\r\nI'm reaching out with a suggestion that might enhance the documentation, particularly for those looking to disable code splitting. We recently came across a method to inline dynamic imports through the Rollup configuration, effectively disabling code splitting. This was discovered in a ViteJS discussion ([Reference here](https://github.com/vitejs/vite/discussions/13925#discussioncomment-7709077)):\r\n\r\n```typescript\r\nbuild: {\r\n rollupOptions: {\r\n output: {\r\n inlineDynamicImports: true\r\n }\r\n }\r\n}\r\n```\r\n\r\nComing forth to this solution took us a considerable amount of time. A search in the Nuxt documentation for \"code splitting\" yielded few results. Including this information in the Nuxt documentation could significantly improve the developer experience, making this knowledge more readily accessible.\r\n\r\nThere are practical scenarios, such as ensuring seamless access for mobile users with unstable internet connections, where disabling code splitting can be beneficial. Although code splitting with dynamic imports provides some fantastic optimizations, ensuring that the entire page content is downloaded and ready on the first load can be crucial in these situations. I do understand, that there are [ways to handle these errors](https://nuxt.com/docs/getting-started/error-handling#errors-with-js-chunks), but unfortunately, as the application grows, it just creates too much room for error.\r\n\r\nI must admit my understanding of the implications of setting `inlineDynamicImports` to `true` is not comprehensive. One of our applications, deployed as a static single-page app, benefits from this setting, but I'm uncertain about its effects in other build configurations. I would greatly appreciate if someone could provide further insight on this.\r\n\r\nAdditionally, I would like your opinion on the best section within the Nuxt documentation to include this information, ensuring it's easily found by those who need it.\r\n\r\nLooking forward to your thoughts and guidance on this matter.\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).",[3208,3211],{"name":3209,"color":3210},"documentation","5319e7",{"name":3193,"color":3194},24539,"Docs: Suggestion for documenting disabling code splitting","2024-06-30T11:06:44Z","https://github.com/nuxt/nuxt/issues/24539",0.7440548,{"description":3218,"labels":3219,"number":3226,"owner":3199,"repository":3227,"state":3200,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\n\nI would really like an implementation of the phone number component. I searched online and found an implementation that uses shadcn vue [https://shadcn-vue-phone-input.vercel.app/](url) . This would be an awesome addition and a very useful feature for my use case. Thanks in advance\n\n### Additional context\n\n_No response_",[3220,3223],{"name":3221,"color":3222},"enhancement","a2eeef",{"name":3224,"color":3225},"v3","49DCB8",2815,"ui","Phone number input component","2025-01-30T14:59:35Z","https://github.com/nuxt/ui/issues/2815",0.74985564,{"description":3233,"labels":3234,"number":3239,"owner":3199,"repository":3227,"state":3240,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Environment\n\n- Operating System: Darwin\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.14.2\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n\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\nhttps://github.com/nuxt/ui/compare/v3...outluch:ui:bugfix-valuekey-customsearch\n\nTry to remove my patch (`filter ? () => rootItems : undefined`) in `SelectMenu.vue` and check how list of found items doesn't render in page select-menu.vue of playground\n\n### Description\n\nI have found weird behavior with custom server-side search, while using custom value-label fields from my db results.\nIf you fetch items from server and they contain for example `id` and `name` instead of `value` and `label`, I pass props to SelectMenu: `:value-key: \"id\"`, `:label-key=\"name\"` and then when I try to search with input, it doesnot render results. I have found that it is because of Radix Vue: when we make own search we should not pass filter function to it, as I got it from sources of Radix. So my patch is in this one commit in my fork.\n\nBtw I have noticed, that migration to Reka UI is on the way and in Reka there are `ignoreFilter` prop now. I guess, we will need to pass it `false` also.. Maybe not. I did not dig this 100% for now.\n\nHope, this will help.\n\nhttps://github.com/nuxt/ui/compare/v3...outluch:ui:bugfix-valuekey-customsearch\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3235,3238],{"name":3236,"color":3237},"bug","d73a4a",{"name":3224,"color":3225},2807,"closed","[v3][SelectMenu] with `filter=false` and `value-key` props","2025-01-25T13:10:49Z","https://github.com/nuxt/ui/issues/2807",0.6979918,{"description":3246,"labels":3247,"number":3252,"owner":3199,"repository":3199,"state":3240,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### Describe the feature\n\nI had a trouble migrating large nuxt 2 project to the nuxt 3 version, because of the missing `router.routeNameSplitter` config parameter, so I was going to submit a PR, but in the last moment I found [this discussion](https://github.com/nuxt/nuxt/issues/18457), and the suggested fix worked for me.\r\n\r\nI still want to help other devs in the migration process, if anyone face similar issue. It took time to found the solution, so should I still suggest a PR with this parameter added for backwards compatibility, [commit for the reference](https://github.com/bargel/nuxt/commit/1d55a28faeafb335e7d5030b0fe3352755428508)? or if those points from the discussion still relevant, maybe just add this solution somewhere to the migration guides?\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).",[3248,3249],{"name":3209,"color":3210},{"name":3250,"color":3251},"3.x","29bc7f",25823,"Missing `routeNameSplitter` router param in config","2024-03-18T15:18:43Z","https://github.com/nuxt/nuxt/issues/25823",0.7109831,{"labels":3258,"number":3261,"owner":3199,"repository":3199,"state":3240,"title":3262,"updated_at":3263,"url":3264,"score":3265},[3259,3260],{"name":3209,"color":3210},{"name":3250,"color":3251},13537,"docs: update migration guide to nuxt 3","2023-01-19T17:03:42Z","https://github.com/nuxt/nuxt/issues/13537",0.7169209,{"description":3267,"labels":3268,"number":3271,"owner":3199,"repository":3272,"state":3240,"title":3273,"updated_at":3274,"url":3275,"score":3276},"http://localhost:3000/integrations?version=2.x\n\n",[3269],{"name":3236,"color":3270},"ff281a",549,"nuxt.com","[Integrations] Version selector is not valid on refresh with query param","2023-02-15T12:32:31Z","https://github.com/nuxt/nuxt.com/issues/549",0.7247888,{"description":3278,"labels":3279,"number":3271,"owner":3199,"repository":3286,"state":3240,"title":3287,"updated_at":3288,"url":3289,"score":3276},"My dev dependencies: \r\n```\r\n{\r\n \"@nuxt/devtools\": \"^0.5.5\",\r\n \"@nuxtjs/tailwindcss\": \"^6.4.1\",\r\n \"@vitest/coverage-c8\": \"^0.31.3\",\r\n \"nuxt\": \"^3.5.2\",\r\n \"nuxt-vitest\": \"0.8.2\",\r\n \"tailwindcss\": \"^3.3.2\",\r\n \"vitest\": \"^0.31.3\"\r\n }\r\n```\r\n\r\nThe app is building fine, but trying to start Vitest is causing the following error:\r\n`ERROR Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'`\r\n\r\nIt seems to be breaking down on `const { startVitest } = await import(await resolvePath(\"vitest/node\"));` in `module.mjs`\r\n\r\nIs anyone else experiencing this issue with the latest version of Nuxt or is it just me?",[3280,3283],{"name":3281,"color":3282},"vitest-environment","b60205",{"name":3284,"color":3285},"windows","6FA283","test-utils","Dynamic module import seems to be causing error","2023-12-02T00:17:10Z","https://github.com/nuxt/test-utils/issues/549",{"description":3291,"labels":3292,"number":3296,"owner":3199,"repository":3227,"state":3240,"title":3297,"updated_at":3298,"url":3299,"score":3300},"### Description\n\nHi,\r\n\r\nI try to create a redirect link for each item in my select, but the redirect doesn't work all the time. If no item is selected, then for the first one it will select it rather than redirect the user :\r\n\r\n```vue\r\n\u003CUSelectMenu\r\n v-model=\"selected\" \r\n :options=\"contacts\" \r\n>\r\n \u003Ctemplate #option=\"{ option }\" >\r\n \u003Cspan>{{ option.name }}\u003C/span>\r\n \u003CNuxtLink :to=\"localePath({name: 'contacts-id', params: { id: option.id }})\" @click.stop>Show\u003C/NuxtLink>\r\n \u003C/template>\r\n\u003C/USelectMenu>\r\n```\r\n\r\nMuch appreciated help!\r\nThanks",[3293],{"name":3294,"color":3295},"question","d876e3",2115,"[SelectMenu] @click.stop not working on first item clicked","2024-09-11T14:48:05Z","https://github.com/nuxt/ui/issues/2115",0.7302398,{"description":3302,"labels":3303,"number":3306,"owner":3199,"repository":3199,"state":3240,"title":3307,"updated_at":3308,"url":3309,"score":3310},"Currently, the migration guides summary and the edge channel page are grouped in two separate pages under the \"Upgrade guide\" section:\n\n- https://v3.nuxtjs.org/getting-started/upgrade-guide/migration\n- https://v3.nuxtjs.org/getting-started/upgrade-guide/edge-channel\n\nThese pages could be merged onto a single \"Upgrade guide\" page with the following structure:\n\n- (Intro)\n- Comparison table\n- From Nuxt 2 to Nuxt 3\n- From Nuxt 2 to Bridge\n- Edge Release Channel\n\nThis would lead to a more flat structure and group all upgrade informations in the same place to make them more discoverable.\n\n",[3304,3305],{"name":3209,"color":3210},{"name":3250,"color":3251},14992,"[Docs] Group migration and edge channel docs","2023-01-19T17:43:25Z","https://github.com/nuxt/nuxt/issues/14992",0.73997825,["Reactive",3312],{},["Set"],["ShallowReactive",3315],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ff92zFHqIUERzvcGjPiaZ4Udp4zNMLS_Uuwvs71UhmOQ":-1},"/nuxt/ui/2112"]