\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003CUInput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[2001,2004],{"name":2002,"color":2003},"bug","d73a4a",{"name":2005,"color":2006},"triage","ffffff",2713,"UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.7429081,{"description":2013,"labels":2014,"number":2018,"owner":1991,"repository":1992,"state":1993,"title":2019,"updated_at":2020,"url":2021,"score":2022},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.9\n- Package Manager: bun@1.2.8\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/fonts@0.11.1, @nuxt/icon@1.12.0, @nuxt/ui@3.0.2, @pinia/nuxt@0.11.0\n- Build Modules: -\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nI tried running this code from `playground-vue`:\n\n```\n\u003CUModal>\n \u003CUButton>Open\u003C/UButton>\n \u003Ctemplate #body>\n \u003CUSelectMenu :items=\"items\" :search-input=\"{ autofocus: false }\" />\n \u003C/template>\n\u003C/UModal>\n```\n\n\n### Description\n\nselect menu's search input always autofocus inside modal, even when the autofocus is set to false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2015,2016,2017],{"name":2002,"color":2003},{"name":1988,"color":1989},{"name":2005,"color":2006},3933,"SelectMenu's autofocus doesn't work inside Modal","2025-04-19T06:22:26Z","https://github.com/nuxt/ui/issues/3933",0.7533182,{"description":2024,"labels":2025,"number":2032,"owner":1991,"repository":1992,"state":1993,"title":2033,"updated_at":2034,"url":2035,"score":2036},"### Environment\n\n- Operating System: Linux\n- Bun Version: v1.1.29\n- Vue Version: v3.5.13\n- Vite Version: v5.4.11\n- Package Manager: bun@1.1.29\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nUnable to run on \u003Chttps://stackblitz.com/edit/vitejs-vite-2s99rp> because of https://github.com/stackblitz/core/issues/1855 (I think) but I'll create a repo as soon as I can.\n\n### Description\n\nAfter following the setup tutorial for the installation of Nuxt UI in a Vue-only environment and running the project, I get an error (see logs). \nThe only different thing in the setup I had to do is that, as I am building a custom element, I did:\n```ts\nconst Widget = defineCustomElement(App, {\n\tconfigureApp(app) {\n\t\tapp.use(ui)\n\t\tapp.use(i18n)\n\t\tapp.provide(I18nInjectionKey, i18n)\n\t},\n})\n```\nInstead of the usual `createApp` method. Did I miss something?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n15:53:45 [vite] Internal server error: [postcss] postcss-import: /home/dany/Documenti/GitHub/chat-widget/node_modules/@nuxt/ui/dist/module.mjs:1:16: Unknown word\n Plugin: vite:css\n File: /home/dany/Documenti/GitHub/chat-widget/node_modules/@nuxt/ui/dist/module.mjs:1:15\n 1 | import defu, { defu as defu$1 } from 'defu';\n | ^\n 2 | import { defineNuxtModule, createResolver, addVitePlugin, addPlugin, addComponentsDir, addImportsDir, extendPages, hasNuxtModule, installModule } from '@nuxt/kit';\n 3 | import { d as defaultOptions, r as resolveColors, a as getDefaultUiConfig, b as addTemplates, c as buildTemplates } from './shared/ui.d52SSCwA.mjs';\n at Input.error (/home/dany/Documenti/GitHub/chat-widget/node_modules/postcss/lib/input.js:106:16)\n at Parser.unknownWord (/home/dany/Documenti/GitHub/chat-widget/node_modules/postcss/lib/parser.js:593:22)\n at Parser.other (/home/dany/Documenti/GitHub/chat-widget/node_modules/postcss/lib/parser.js:435:12)\n at Parser.parse (/home/dany/Documenti/GitHub/chat-widget/node_modules/postcss/lib/parser.js:470:16)\n at parse (/home/dany/Documenti/GitHub/chat-widget/node_modules/postcss/lib/parse.js:11:12)\n at get root [as root] (/home/dany/Documenti/GitHub/chat-widget/node_modules/postcss/lib/no-work-result.js:119:14)\n at Result.get [as root] (/home/dany/Documenti/GitHub/chat-widget/node_modules/postcss/lib/no-work-result.js:27:21)\n at loadImportContent (file:///home/dany/Documenti/GitHub/chat-widget/node_modules/vite/dist/node/chunks/dep-C6EFp3uH.js:867:33)\n at async Promise.all (index 0)\n at async resolveImportId (file:///home/dany/Documenti/GitHub/chat-widget/node_modules/vite/dist/node/chunks/dep-C6EFp3uH.js:800:27)\n15:53:45 [vite] Pre-transform error: [postcss] postcss-import: /home/dany/Documenti/GitHub/chat-widget/node_modules/@nuxt/ui/dist/module.mjs:1:16: Unknown word\n```",[2026,2027,2028,2029],{"name":2002,"color":2003},{"name":1988,"color":1989},{"name":2005,"color":2006},{"name":2030,"color":2031},"vue","42b883",2827,"Internal server error: [postcss] postcss-import: Unknown word","2025-03-15T05:10:43Z","https://github.com/nuxt/ui/issues/2827",0.75399375,{"description":2038,"labels":2039,"number":2042,"owner":1991,"repository":2043,"state":2044,"title":2045,"updated_at":2046,"url":2047,"score":2048},"The Roadmap table (and probably the table component in general) might need some improvements for small screens.\r\n\r\n\r\n\r\n\r\nReported by @AndreyYolkin on [Discord](https://discord.com/channels/473401852243869706/473407466630152201/1164224885170647050)",[2040],{"name":1985,"color":2041},"1ad6ff",1374,"nuxt.com","closed","Improve roadmap table on mobile","2023-12-08T16:15:30Z","https://github.com/nuxt/nuxt.com/issues/1374",0.6751663,{"description":2050,"labels":2051,"number":2060,"owner":1991,"repository":1991,"state":2044,"title":2061,"updated_at":2062,"url":2063,"score":2064},"### Describe the feature\n\nWhen using the `useRoute` composable, the route params aren't beeing typed.\r\nI'm in the folder's path `pasges/me/[id].vue` and when I type the code below, the `id` insn't in the vscode completition.\r\n\r\n```javascript\r\n\u003Cscript setup>\r\nconst route = useRoute();\r\nconsole.log(route.params.id) // id isn't in the vscode completition\r\n\u003C/script>\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).",[2052,2054,2057],{"name":1985,"color":2053},"8DEF37",{"name":2055,"color":2056},"3.x","29bc7f",{"name":2058,"color":2059},"🍰 p2-nice-to-have","0E8A16",20299,"Route params typefication","2023-05-18T09:59:31Z","https://github.com/nuxt/nuxt/issues/20299",0.71042836,{"description":2066,"labels":2067,"number":2070,"owner":1991,"repository":2043,"state":2044,"title":2071,"updated_at":2072,"url":2073,"score":2074},"\n\nhttps://nuxt.com/design-kit",[2068],{"name":2002,"color":2069},"ff281a",1516,"[design kit] Color boxes are broken","2024-03-03T09:33:13Z","https://github.com/nuxt/nuxt.com/issues/1516",0.71048635,{"description":2076,"labels":2077,"number":2080,"owner":1991,"repository":1992,"state":2044,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.13.1\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: yarn@4.5.2\n- Builder: -\n- User Config: modules, ssr, components, app, css, runtimeConfig, compatibilityDate, vite, eslint\n- Runtime Modules: @pinia/nuxt@0.10.1, @pinia-plugin-persistedstate/nuxt@1.2.1, @nuxt/ui@3.0.0-alpha.13, dayjs-nuxt@2.1.11, @nuxt/eslint@1.1.0\n- Build Modules: -\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/bold-fog-4r922z\n\n### Description\n\nWhen a modal is too long, it's not possible to scroll\n\nCurrent solution is to use this\n\n```\n:ui=\"{\n content: 'overflow-y-auto'\n }\"\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2078,2079],{"name":2002,"color":2003},{"name":1988,"color":1989},3398,"Modal: Long modals are not scrollable","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3398",0.7509886,{"description":2086,"labels":2087,"number":2091,"owner":1991,"repository":1991,"state":2044,"title":2092,"updated_at":2093,"url":2094,"score":2095},"Hi,\r\n\r\nI have a js file in which I try to set a path variable like:\r\n\r\n```\r\nconst MANIFEST = {\r\n path: 'assets/something/',\r\n}\r\n\r\n```\r\nHowever, whatever I put as the path it always ends in 404's, even tho the path that is output looks correct to me like:\r\n\r\n`http://localhost:3000/assets/something/....`\r\n\r\nAny idea why?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1831\">#c1831\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2088],{"name":2089,"color":2090},"2.x","d4c5f9",2064,"path variable 404 ","2023-01-18T15:43:03Z","https://github.com/nuxt/nuxt/issues/2064",0.7566197,{"description":2097,"labels":2098,"number":2106,"owner":1991,"repository":1991,"state":2044,"title":2107,"updated_at":2108,"url":2109,"score":2110},"### Version\n\n[v2.8.1](https://github.com/nuxt.js/releases/tag/v2.8.1)\n\n### Reproduction link\n\n[n/a](n/a)\n\n### Steps to reproduce\n\nCreate following file/directory structure:\n```\n/pages/test1/_param1.vue\n/pages/test2/_param2/index.vue\n```\n\n### What is expected ?\n\nRoutes to be generated as:\n```\n/test1/:param1?\n/test2/:param2\n```\n\n### What is actually happening?\n\nRoutes are generated as:\n```\n/test1/:param1?\n/test2/:param2?\n```\n\n### Additional comments?\n\nThe [guide](https://nuxtjs.org/guide/routing/#dynamic-routes) says:\n> As you can see the route named `users-id` has the path `:id?` which makes it optional, if you want to make it required, create an `index.vue` file in the `users/_id` directory instead.\n\nFollowing this advice (test2) results the parameter still being optional.\n\nThe test related to this functionality (https://github.com/nuxt/nuxt.js/blob/2fabea9402864828fe9aafe8b0d13bcc674a1b3b/packages/utils/test/route.test.js#L174-L184) seems to cover only cases where the parameter is defined in a filename, eg being the very last node.\n\nI believe that any parameters specified as directories should be treated as required, so it would be possible to have full control over whether a route parameter is required or optional without resorting to any workarounds.\n\n\u003C!--cmty-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9312\">#c9312\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2099,2102,2105],{"name":2100,"color":2101},"good first issue","fbca04",{"name":2103,"color":2104},"pending triage","E99695",{"name":2089,"color":2090},5874,"Unable to create a dynamic route with required parameter by following the guide","2023-01-22T15:33:07Z","https://github.com/nuxt/nuxt/issues/5874",0.75887096,["Reactive",2112],{},["Set"],["ShallowReactive",2115],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"zVfLEXAPG-2n-PkDW-LR4hSdcr06G8_Q9r5xSe_bdPU":-1},"/nuxt/ui/2370"]