\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```",[2865,2868],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"triage","ffffff",2713,"nuxt","ui","open","UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.70702577,{"description":2880,"labels":2881,"number":2884,"owner":2872,"repository":2873,"state":2874,"title":2885,"updated_at":2886,"url":2887,"score":2888},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.2\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules\n- Runtime Modules: @nuxt/ui@2.21.0\n- Build Modules: -\n\n### Version\n\nv2.21.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-kt7kxa75?file=app.vue\n\n### Description\n\nThe position of the arrow of a tooltip which is used inside a popover appears in the wrong position if the `top` placement is used\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2882,2883],{"name":2866,"color":2867},{"name":2869,"color":2870},3164,"Bug on tooltip arrow position if inside a popover","2025-01-23T09:36:39Z","https://github.com/nuxt/ui/issues/3164",0.75121325,{"description":2890,"labels":2891,"number":2898,"owner":2872,"repository":2873,"state":2874,"title":2899,"updated_at":2900,"url":2901,"score":2902},"### Description\n\nHow do you set viewport align to \"start\" like [this](https://reka-ui.com/docs/components/navigation-menu#viewport) ?\n\nFor now I am using this horrible workaround\n\n```\n:ui=\"{\n viewport: 'left-0 -ml-[1em]',\n viewportWrapper: 'absolute top-full left-4 w-auto'\n}\"\n```",[2892,2895],{"name":2893,"color":2894},"question","d876e3",{"name":2896,"color":2897},"v3","49DCB8",3364,"navigationmenu viewport align prop","2025-02-21T18:12:23Z","https://github.com/nuxt/ui/issues/3364",0.756576,{"description":2904,"labels":2905,"number":2909,"owner":2872,"repository":2872,"state":2874,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.12.3\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.18\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: \r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-zckkxt\r\n\r\n### Describe the bug\r\n\r\nIf you use `useFetch` with the same target url in multiple components, the application will fetch this multiple times.\r\n\r\ne.g. `useFetch('/api/random')`\r\n\r\nEven if the docs describe another behavior \r\n\r\n**From docs:**\r\n\r\nAbout Keys\r\n\r\n> [useFetch](https://nuxt.com/docs/api/composables/use-fetch) uses the provided URL as a key. Alternatively, a key value can be provided in the options object passed as a last argument.\r\n\r\nThere is a hint, about using references or functions in options\r\n\r\n> If you provide a function or ref as the url parameter, or if you provide functions as arguments to the options parameter, then the useFetch call will not match other useFetch calls elsewhere in your codebase, even if the options seem to be identical. If you wish to force a match, you may provide your own key in options.\r\n\r\nFrom Data-Fetching docs\r\n\r\n> Since the autogenerated key only takes into account the file and line where useAsyncData is invoked, it is recommended to always create your own key to avoid unwanted behavior, like when you are creating your own custom composable wrapping useAsyncData.\r\n\r\nSince `useFetch` just wraps `useAsyncData` it could be that the same rule counts for `useFetch`, but its not clear from the docs. If you read the docs you would assume that `useFetch` passes a generated key by URL to `useAsyncData` independent from the file and line where it was invoked.\r\n\r\nUsing \r\n```ts\r\nuseFetch('/api/random', { key: 'my-key' })\r\n```\r\nprevents multiple calls.\r\n\r\n\r\n### **What would be expected behaviour?**\r\nWhenever the auto-generated `key` by passed url from `useFetch` is identical across components, the composable should act same as passing the `key` as option.\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2906],{"name":2907,"color":2908},"pending triage","E99695",28169,"useFetch only prevents multiple requests when `key` option is set","2024-07-16T11:21:42Z","https://github.com/nuxt/nuxt/issues/28169",0.7581704,{"description":2915,"labels":2916,"number":2919,"owner":2872,"repository":2920,"state":2921,"title":2922,"updated_at":2923,"url":2924,"score":2925},"\n\nhttps://nuxt.com/design-kit",[2917],{"name":2866,"color":2918},"ff281a",1516,"nuxt.com","closed","[design kit] Color boxes are broken","2024-03-03T09:33:13Z","https://github.com/nuxt/nuxt.com/issues/1516",0.6544005,{"description":2927,"labels":2928,"number":2930,"owner":2872,"repository":2873,"state":2921,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.12.1`\n- Nuxt Version: `3.13.2`\n- CLI Version: `3.14.0`\n- Nitro Version: `2.9.7`\n- Package Manager: `pnpm@9.9.0`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n\n### Version\n\n2.18.4\n\n### Reproduction\n\n```\nexport default defineAppConfig({\n ui: {\n primary: 'black',\n gray: 'neutral',\n...\n```\n\n### Description\n\nWhen setting `ui.primary` to black the primary colour changes to black as expected, but then I am unable to select (I.e highlight) any of the text anywhere on any page.\n\nIf I set the colour to a Tailwind colour like `slate` then the text is selectable. However, `slate-950` doesn't work, it seems it doesn't support shades. \n\nSpecifying a colour with `#` does not seem to be supported in that field either. \n\nSubsequently there is no way to access black. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2929],{"name":2866,"color":2867},2370,"Unable to use black as primary ui colour","2024-10-23T20:24:09Z","https://github.com/nuxt/ui/issues/2370",0.669493,{"description":2936,"labels":2937,"number":2938,"owner":2872,"repository":2920,"state":2921,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Environment\r\n\r\nN/A\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nGoing to https://nuxt.com/modules/tailwindcss resulted in this:\r\n\r\n\u003Cimg width=\"573\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/26592486/c1018a94-852c-46f2-ae1b-2c42f83028e4\">\r\n\r\n**ID as Text**: `cle1::k9s6r-1697123779540-48474018b10e`\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[],1368,"nuxt.com 504: GATEWAY_TIMEOUT","2023-10-18T11:04:15Z","https://github.com/nuxt/nuxt.com/issues/1368",0.7066077,{"description":2944,"labels":2945,"number":2946,"owner":2872,"repository":2920,"state":2921,"title":2947,"updated_at":2948,"url":2949,"score":2950},"If you go to any blog and click `Edit on Github` on aside it will bring you to a 404 on github.\r\n\r\nCode that is incorrect: https://github.com/nuxt/nuxt.com/blob/a9b1e32c93714f23703f12add0f0c17cc518bd2a/pages/blog/%5Bslug%5D.vue#L66\r\n\r\nNeeds to be: \r\n\r\n```\r\nhttps://github.com/nuxt/nuxt.com/edit/main/content/${article.value._file}\r\n```",[],1533,"blog \"Edit on Github\" url is broke.","2024-03-11T22:23:34Z","https://github.com/nuxt/nuxt.com/issues/1533",0.7142434,{"description":2952,"labels":2953,"number":2956,"owner":2872,"repository":2873,"state":2921,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Environment\n\n\n Operating System: Windows_NT\n Node Version: v20.18.0\n Nuxt Version: 3.13.2\n CLI Version: 3.14.0\n Nitro Version: 2.9.7\n Package Manager: pnpm@9.12.1\n Builder: -\n User Config: -\n Runtime Modules: -\n Build Modules: -\n\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nCannot use v3 on stackblitz so no repo.\n\n### Description\n\nIt looks like `onSelect?(e: Event): void` doesn't work, instead it is `select?(e: Event): void`. \nSpent a good amount of time until I figured it out. :')\nDocs problem only or something else?\n\nOnly tried nav and dropdown menus but this probably happens on all components that have onSelect:\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2954,2955],{"name":2866,"color":2867},{"name":2896,"color":2897},2392,"[NavigationMenu/DropdownMenu etc] 'onSelect' doesn't work, instead it is 'select' only","2024-10-16T09:55:28Z","https://github.com/nuxt/ui/issues/2392",0.7155704,{"description":2962,"labels":2963,"number":2967,"owner":2872,"repository":2873,"state":2921,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Description\n\nI would like the ability to add / enable animations like slide / fade when the carousel changes the current page.\n\nI noticed from the repo links refering to https://www.embla-carousel.com/plugins. This present some animations like sliding https://www.embla-carousel.com/plugins/autoplay or fading https://www.embla-carousel.com/plugins/fade.\n\nI tried the prop `fade` whith `\u003CUCarousel />` but didn't see the effect.\n\nThank you.\n\n### Additional context\n\n_No response_",[2964],{"name":2965,"color":2966},"enhancement","a2eeef",3101,"[Feature request] animation on change for carousel","2025-01-25T13:14:24Z","https://github.com/nuxt/ui/issues/3101",0.7229142,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3n915gXgsZvXTCL4TjgV2ztobp9kwz1UVv3D_9uTojs":-1},"/nuxt/nuxt.com/1374"]