\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```",[2016,2017],{"name":1985,"color":1986},{"name":2006,"color":2007},2713,"UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.7202512,{"description":2024,"labels":2025,"number":2028,"owner":1991,"repository":2029,"state":2030,"title":2031,"updated_at":2032,"url":2033,"score":2034},"https://content-v2.nuxtjs.org/guide/writing/mdc#props\n\n",[2026],{"name":1985,"color":2027},"ff281a",496,"nuxt.com","closed","[Milkdown] On serialize, component props should keep their current format `inline` or `yaml`","2023-06-06T12:14:53Z","https://github.com/nuxt/nuxt.com/issues/496",0.65784746,{"description":1982,"labels":2036,"number":2028,"owner":1991,"repository":2040,"state":2030,"title":2041,"updated_at":2042,"url":2043,"score":2034},[2037],{"name":2038,"color":2039},"vitest-environment","b60205","test-utils","documentation/examples","2023-12-02T22:52:29Z","https://github.com/nuxt/test-utils/issues/496",{"description":2045,"labels":2046,"number":2049,"owner":1991,"repository":1992,"state":2030,"title":2050,"updated_at":2051,"url":2052,"score":2053},"### Environment\n\n-Macbook Apple M2 Pro, macOS 15.3\nOn your site, when you select a date in the select by double-clicking on the date, the popover breaks and the calendar flies to the top corner of the page.\n\nhttps://github.com/user-attachments/assets/a1fa58d1-1f82-464e-8af9-fe044a6cf65b\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nopen site https://ui3.nuxt.dev/components/calendar#as-a-datepicker and try to select date\n\n### Description\n\nwhen you select date my click on date and second click in this date will brake popover, and calendar move top top left corner\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2047,2048],{"name":1985,"color":1986},{"name":1988,"color":1989},3283,"Calendar as a Datepicker","2025-02-10T14:13:24Z","https://github.com/nuxt/ui/issues/3283",0.7005552,{"description":2055,"labels":2056,"number":2058,"owner":1991,"repository":1992,"state":2030,"title":2059,"updated_at":2060,"url":2061,"score":2062},"### Description\n\nThere should be an option via Nuxt UI's configuration to disable all of the other modules:\r\n- @nuxt/icon\r\n- @nuxtjs/tailwindcss\r\n- @nuxtjs/color-mode\r\n\r\nThat way, if a user wanted access to the components, but entirely unstyled, they could still use Nuxt UI.\r\n\r\nCurrently, I have a use case for using UPopover, but not Tailwind, Nuxt Icon, or color mode. I could use Headless UI instead, but Nuxt UI's implementation of the hover mode is already complete and ready to use.\n\n### Additional context\n\n_No response_",[2057],{"name":2002,"color":2003},2162,"Disable @nuxt/icon, @nuxtjs/tailwindcss and @nuxtjs/color-mode modules via config","2024-09-10T16:29:53Z","https://github.com/nuxt/ui/issues/2162",0.70349216,{"description":2064,"labels":2065,"number":2077,"owner":1991,"repository":1991,"state":2030,"title":2078,"updated_at":2079,"url":2080,"score":2081},"### Environment\r\n\r\nEvery Environment\r\n\r\n### Reproduction\r\n\r\nI really believe a reproduction is not needed but tell me otherwise and I create one.\r\n\r\n### Describe the bug\r\n\r\nRegarding `useLazyAsyncData` example: https://nuxt.com/docs/api/composables/use-lazy-async-data#example\r\n\r\n\u003Cimg width=\"809\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/47485736/12cb870f-c219-4642-a852-00ede0d74dc1\">\r\n\r\nWe are making a `watch` call in an async context in this example, after further investigation I found some docs in Vue 3 oficial site (https://vuejs.org/guide/essentials/watchers.html#stopping-a-watcher) that say the automatic process of stopping watchers does not work in async contexts. \r\n\r\nMy workaround for this was making a new hook called `useSafeWatch` that looks something like this:\r\n\r\n./useSafeWatch.ts\r\n```ts\r\nexport default useSafeWatch() {\r\n const watchersToBeCleaned = []\r\n onBeforeUnmount(() => {\r\n watchersToBeCleaned.forEach(stopWatcher => stopWatcher())\r\n })\r\n return {\r\n watch: (...args) => {\r\n watchersToBeCleaned.push(watch(...args))\r\n }\r\n }\r\n}\r\n```\r\n\r\n./usingTheHook.vue\r\n```js\r\n\u003Cscript setup>\r\nconst { watch } = useSafeWatch()\r\n\u003C/script>\r\n```\r\n\r\nAnother solution is making something like `unctx` and store the current context (vue instance in this case) in globalThis and window but this seems to be an upstream solution...\r\n\r\nIs this something worth implementing a PR? Computeds seem to be another issue here?\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2066,2068,2071,2074],{"name":2002,"color":2067},"8DEF37",{"name":2069,"color":2070},"discussion","538de2",{"name":2072,"color":2073},"3.x","29bc7f",{"name":2075,"color":2076},"performance","E84B77",23043,"Possible memory leak example in the docs could be a feature `useSafeWatch`","2024-04-03T09:49:04Z","https://github.com/nuxt/nuxt/issues/23043",0.7043738,{"description":2083,"labels":2084,"number":2085,"owner":1991,"repository":2029,"state":2030,"title":2086,"updated_at":2087,"url":2088,"score":2089},"### Environment\n\nproduction\n\n### Reproduction\n\nhttps://nuxt.com/docs/getting-started/installation\n\n### Describe the bug\n\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[],1577,"nuxt.com throwing errors","2024-05-07T09:42:16Z","https://github.com/nuxt/nuxt.com/issues/1577",0.7079967,{"description":2091,"labels":2092,"number":2097,"owner":1991,"repository":1992,"state":2030,"title":2098,"updated_at":2099,"url":2100,"score":2101},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nI've noticed that links (\\\u003Ca\\> tags) created with `UButton` contain a lot of unnecessary styling related to the button itself, disabled and enabled state. Given that for anchors there is no `disabled` property in the HTML specification, this means that out of the following styles:\n```\nrounded-[calc(var(--ui-radius)*1.5)] font-medium inline-flex items-center focus:outline-none transition-colors px-2.5 py-1.5 text-sm gap-1.5 ring ring-inset ring-[var(--ui-primary)]/50 text-[var(--ui-primary)] hover:bg-[var(--ui-primary)]/10 focus-visible:ring-2 focus-visible:ring-[var(--ui-primary)]\n```\n\nAt the very least, these can be removed:\n\n```\ndisabled:cursor-not-allowed aria-disabled:cursor-not-allowed disabled:opacity-75 aria-disabled:opacity-75 disabled:bg-transparent aria-disabled:bg-transparent dark:disabled:bg-transparent dark:aria-disabled:bg-transparent\n```\n\nThis is quite a reduction in classes and can make a moderate difference in total page size and even web vitals scores, especially if there are a lot of links on the page created with `UButton` (which is very likely given the customization UButton provides with icons, variants, colors, and more)\n\nIn order to make this work, the classes that rely on disabled state would likely need to be extracted into a separate place in the theme, which tailwind-variants will then need to merge if there is no `to` property present.\n\nYou might be asking why, given that technically people can rely on it to prevent navigation until a certain condition. But the answer to that is that restricting links like that is generally bad practice and can be circumvented pretty easily. It's not meant to be a security feature and it also lacks in terms of functional purpose.\n\nI'll check to see what I can do about it, but I thought sharing it here would be more beneficial in case someone will be faster than me in preparing a PR for this =)",[2093,2096],{"name":2094,"color":2095},"question","d876e3",{"name":1988,"color":1989},2907,"[Performance improvement opportunity]: remove disabled-dependent classes on links created with `UButton`","2025-01-13T22:45:37Z","https://github.com/nuxt/ui/issues/2907",0.71022916,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"RNbM6kKHaXIlG8ns0lPTnJjoEi3zM-WwVWDFZR7yYus":-1},"/nuxt/ui/3125"]