\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```",[2887,2890],{"name":2888,"color":2889},"bug","d73a4a",{"name":2891,"color":2892},"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.74354964,{"description":2899,"labels":2900,"number":2904,"owner":2863,"repository":2863,"state":2865,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Describe the feature\n\n```ts\nconst id = ref()\nuseFetch('/api/test', {\n query: {\n id\n },\n ready: () => !!id.value\n})\n```\n\n```ts\ninterface Options {\n /** default `() => true` */\n ready: () => boolean\n // or\n // ready: MaybeRefOrGetter\u003Cboolean>\n}\n```\n\n Whenever the handler is executed, if ready is false, prevent the execution of handler.\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).",[2901],{"name":2902,"color":2903},"pending triage","E99695",29788,"`ready` option for `useFetch` to control requests","2024-11-05T06:26:41Z","https://github.com/nuxt/nuxt/issues/29788",0.7468719,{"description":2910,"labels":2911,"number":2915,"owner":2863,"repository":2864,"state":2865,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Environment\n\nNuxt UI pro v 3.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu#control-search-term\n\n### Description\n\nHello, \n\nI am reopening an issue based on https://github.com/nuxt/ui/issues/3782\n\nI still have an issue on the InputMenu that filters with the default value.\n\nAs a reproduction : we can see the same behavior I am facing in the documentation : https://ui.nuxt.com/components/input-menu#control-search-term . \n\n1) => The first click on InputMenu shows only the seacherd term (here Backlog)\n2) => If I close the popover and reopen it a second time, it shows the entire list.\n\nI tried the :reset-search-term-on-select=\"false\" , it allows to display the entire list at 1st click but it leads to not showing the default selected value (the placeholder is displayed).\n\nActually, I am looking to display the entire list at first click, even if a value is already selected.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2912,2913,2914],{"name":2888,"color":2889},{"name":2860,"color":2861},{"name":2891,"color":2892},3993,"InputMenu Clear Search on Select at first click","2025-04-27T12:37:04Z","https://github.com/nuxt/ui/issues/3993",0.7474314,{"description":2921,"labels":2922,"number":2932,"owner":2863,"repository":2933,"state":2934,"title":2935,"updated_at":2936,"url":2937,"score":2938},"I'm setting up the nuxt-vitest module in my project. Though I'm running into some issues getting a simple test, I use mountSuspended(Logo) to test the mounting of a Logo component. This component uses i18n. Whereas when I'm using mount from Vitest the test passes.\r\n\r\nThe error I'm getting is as follows:\r\n```\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nSyntaxError: Need to install with `app.use` function\r\n ❯ Module.createCompileError ../node_modules/.pnpm/@intlify+message-compiler@9.3.0-beta.17/node_modules/@intlify/message-compiler/dist/message-compiler.mjs:54:19\r\n ❯ createI18nError ../node_modules/.pnpm/vue-i18n@9.3.0-beta.17_vue@3.3.4/node_modules/vue-i18n/dist/vue-i18n.runtime.mjs:97:34\r\n 96| [I18nErrorCodes.INVALID_ARGUMENT]: 'Invalid argument',\r\n 97| [I18nErrorCodes.MUST_BE_CALL_SETUP_TOP]: 'Must be called at the top of a `setup` function',\r\n 98| [I18nErrorCodes.NOT_INSLALLED]: 'Need to install with `app.use` function',\r\n | ^\r\n 99| [I18nErrorCodes.UNEXPECTED_ERROR]: 'Unexpected error',\r\n 100| [I18nErrorCodes.NOT_AVAILABLE_IN_LEGACY_MODE]: 'Not available in legacy mode',\r\n ❯ Module.useI18n ../node_modules/.pnpm/vue-i18n@9.3.0-beta.17_vue@3.3.4/node_modules/vue-i18n/dist/vue-i18n.runtime.mjs:2253:15\r\n ❯ setup app.vue:33:40\r\n```\r\n\r\nAnd while we are at it. Is there a way to test with the translated i18n messages iso the keys?\r\n\r\n######\r\n\r\nHere are some snippets from my configuration.\r\nvitest.config.js\r\n```\r\n...\r\nexport default defineVitestConfig({\r\n resolve: {\r\n alias\r\n },\r\n test: {\r\n dir: tests,\r\n setupFiles: ['tests/unit.setup.ts'],\r\n environment: 'jsdom',\r\n globals: true,\r\n root: rootDir,\r\n environmentOptions: {\r\n nuxt: {\r\n rootDir\r\n }\r\n }\r\n }\r\n})\r\n```\r\n\r\n./test/nuxt/components/Logo.nuxt.spec.ts (with mountSuspended)\r\n```\r\nimport { describe, it, expect } from 'vitest'\r\n\r\nimport { mountSuspended } from 'vitest-environment-nuxt/utils'\r\nimport Logo from '@/components/header/Logo.vue'\r\n\r\ndescribe('HeaderLogo', () => {\r\n it('can mount some component', async () => {\r\n const component = await mountSuspended(Logo)\r\n expect(component.vm).toBeTruthy()\r\n expect(component.text()).toMatchInlineSnapshot(\r\n '\"global.logo-brand-name.global.logo-brand-localehomepage.logo-tagline\"'\r\n )\r\n })\r\n})\r\n```\r\n./tests/unit.setup.ts\r\n```\r\nimport { config } from '@vue/test-utils'\r\nimport { createI18n } from 'vue-i18n'\r\n\r\nimport nlNL from '~/locales/nl_NL.json'\r\n\r\nconst i18n = createI18n({\r\n legacy: false,\r\n locale: 'nl_NL',\r\n missing: (_, key) => key,\r\n messages: {\r\n nlNL\r\n }\r\n})\r\n\r\nconfig.global.mocks = {\r\n t: msg => msg\r\n}\r\nconfig.global.plugins.push(i18n)\r\n```\r\n\r\n\r\n./tests/nuxt/components/Logo.nuxt.spec.ts (without mountSuspended)\r\n```\r\nimport { mount } from '@vue/test-utils'\r\nimport { describe, it, expect } from 'vitest'\r\n\r\nimport Logo from '@/components/header/Logo.vue'\r\n\r\ndescribe('HeaderLogo', () => {\r\n it('can mount some component', () => {\r\n const component = mount(Logo)\r\n expect(component.vm).toBeTruthy()\r\n expect(component.text()).toMatchInlineSnapshot(\r\n '\"global.logo-brand-name.global.logo-brand-localehomepage.logo-tagline\"'\r\n )\r\n })\r\n})\r\n```\r\n\r\n",[2923,2926,2929],{"name":2924,"color":2925},"vitest-environment","b60205",{"name":2927,"color":2928},"needs reproduction","DE7793",{"name":2930,"color":2931},"closed-by-bot","ededed",585,"test-utils","closed","mountSuspended with i18n","2025-01-22T12:49:12Z","https://github.com/nuxt/test-utils/issues/585",0.6981567,{"description":2940,"labels":2941,"number":2952,"owner":2863,"repository":2863,"state":2934,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### 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).",[2942,2943,2946,2949],{"name":2874,"color":2875},{"name":2944,"color":2945},"good first issue","fbca04",{"name":2947,"color":2948},"3.x","29bc7f",{"name":2950,"color":2951},"🍰 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.7165015,{"description":2958,"labels":2959,"number":2962,"owner":2863,"repository":2864,"state":2934,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.10, @vueuse/nuxt@10.11.1, @nuxtjs/mdc@0.6.1, @formkit/auto-animate/nuxt@0.8.2, @vite-pwa/nuxt@0.10.5\n- Build Modules: -\n------------------------------\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\n\n\n\n### Description\n\nI am getting this error when using USelect or USelectMenu when accessing in development mode from a url other than localhost when using the npm run dev -- --host command may be because I am not using http\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2960,2961],{"name":2888,"color":2889},{"name":2860,"color":2861},2877,"v3 USelectMenu webCrypto.randomUUID is not a function","2025-02-05T12:27:33Z","https://github.com/nuxt/ui/issues/2877",0.72307426,{"description":2968,"labels":2969,"number":2972,"owner":2863,"repository":2864,"state":2934,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### Description\n\nI want to configure my Nuxt UI v3 project only to use black and white colors with the neutral palette from Tailwind, similar to the one found in shadcn. I understand Nuxt UI supports Tailwind CSS theming, but I’m unsure of the best/recommended way to override all component colors globally",[2970,2971],{"name":2857,"color":2858},{"name":2860,"color":2861},3200,"How to create a black & white only theme in Nuxt UI v3","2025-02-09T12:59:38Z","https://github.com/nuxt/ui/issues/3200",0.72851413,{"description":2978,"labels":2979,"number":2987,"owner":2863,"repository":2864,"state":2934,"title":2988,"updated_at":2989,"url":2990,"score":2991},"### Environment\n\n```\nNuxt project info: 4:13:17 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.16.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.7.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Version\n\n2.18.7\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button\n\n### Description\n\n\nMy issue is pretty close to https://github.com/nuxt/ui/issues/468.\n\nIt's when you switch between different types of props on a component document that this issue occurs, the first time you enter it no such issue occurs.\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2980,2981,2984],{"name":2888,"color":2889},{"name":2982,"color":2983},"documentation","0075ca",{"name":2985,"color":2986},"duplicate","cfd3d7",2429,"DOCS: You should use slots with \u003CContentRenderer>","2024-10-21T10:20:28Z","https://github.com/nuxt/ui/issues/2429",0.72863066,["Reactive",2993],{},["Set"],["ShallowReactive",2996],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fj0NOWpDUzB2WzE28M96rjW0lNJeWieDzfYOe6d-UMyI":-1},"/nuxt/ui/2840"]