\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```",[2878,2879],{"name":2862,"color":2863},{"name":2880,"color":2881},"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.7024873,{"description":2888,"labels":2889,"number":2894,"owner":2868,"repository":2869,"state":2870,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### 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```",[2890,2893],{"name":2891,"color":2892},"question","d876e3",{"name":2865,"color":2866},3364,"navigationmenu viewport align prop","2025-02-21T18:12:23Z","https://github.com/nuxt/ui/issues/3364",0.71718264,{"description":2900,"labels":2901,"number":2904,"owner":2868,"repository":2905,"state":2906,"title":2907,"updated_at":2908,"url":2909,"score":2910},"https://content-v2.nuxtjs.org/guide/writing/mdc#props\n\n",[2902],{"name":2862,"color":2903},"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.660941,{"description":2859,"labels":2912,"number":2904,"owner":2868,"repository":2916,"state":2906,"title":2917,"updated_at":2918,"url":2919,"score":2910},[2913],{"name":2914,"color":2915},"vitest-environment","b60205","test-utils","documentation/examples","2023-12-02T22:52:29Z","https://github.com/nuxt/test-utils/issues/496",{"description":2921,"labels":2922,"number":2923,"owner":2868,"repository":2905,"state":2906,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### 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.69717306,{"description":2929,"labels":2930,"number":2933,"owner":2868,"repository":2869,"state":2906,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### 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```",[2931,2932],{"name":2862,"color":2863},{"name":2865,"color":2866},3283,"Calendar as a Datepicker","2025-02-10T14:13:24Z","https://github.com/nuxt/ui/issues/3283",0.6972196,{"description":2939,"labels":2940,"number":2945,"owner":2868,"repository":2869,"state":2906,"title":2946,"updated_at":2947,"url":2948,"score":2949},"https://www.radix-vue.com/components/select.html#scrollupbutton",[2941,2944],{"name":2942,"color":2943},"enhancement","a2eeef",{"name":2865,"color":2866},2145,"[Select] Handle scroll buttons","2025-04-21T20:05:00Z","https://github.com/nuxt/ui/issues/2145",0.69852835,{"description":2951,"labels":2952,"number":2964,"owner":2868,"repository":2868,"state":2906,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### 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_",[2953,2955,2958,2961],{"name":2942,"color":2954},"8DEF37",{"name":2956,"color":2957},"discussion","538de2",{"name":2959,"color":2960},"3.x","29bc7f",{"name":2962,"color":2963},"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.70096,{"description":2970,"labels":2971,"number":2979,"owner":2868,"repository":2869,"state":2906,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Environment\n\nBuild error on vercel.app and on local windows 10, both on build and dev.\n\n### Version\n\nv1.4.4 @nuxt/ui-pro - Saas Template\n\n### Reproduction\n\nInstall a clean saas template.\nEnable typescript check in nuxt.config\n\nTry to deploy it on vercel.\n\nAnd try to copy/paste the url in a facebook post.\n\nHere is a 100% clean saas template, without typeCheck enabled:\nhttps://stackblitz.com/~/github.com/LutherApp/codespace-project\n\n(This is a copy of my [github repo](https://github.com/LutherApp/codespace-project))\n\n### Description\n\nOn build there will be \n## errors on the \"title\"-variable\nError-msg:\nObject literal may only specify known properties, and 'title' does not exist in type 'OgImageOptions\u003C\"NuxtSeo\"> | OgImagePrebuilt'. (etc.)\n\n## \"authors\"- and \"title\"-variable in blog/index\n3 x Type 'bla bla bla' is not assignable to type 'bla bla bla'.\n1 x Property 'avatar' is optional in type 'bla bla bla' but required in type 'bla bla bla'.\n\n## Fix\nI was adding this workaround for typecheck in three or four files:\n```\n// @ts-expect-error Object literal may only specify known properties, and 'title' does not exist in type 'OgImageOptions\u003C\"NuxtSeo\"> | OgImagePrebuilt'.\n```\n\nIn blog/index.vue a was adding this lines in the template in front of `UPageBody` (in blog/index.vue):\n``` \n\u003C!--\n @vue-expect-error The variable authors throws four errors;\n 3 x Type 'bla bla bla' is not assignable to type 'bla bla bla'.\n 1 x Property 'avatar' is optional in type 'bla bla bla' but required in type 'bla bla bla'.\n -->\n```\n\n## seo info from the page missing on facebook\nThere is still noe data about the page on facebook. \n(Other nuxt-content I have made earlier have this info when I copy/paste the url to facebook.)\n\n## Any questions to this issue?\nPlease add some questions to get more info about this issues. (This was written faster than normal.)",[2972,2973,2976],{"name":2862,"color":2863},{"name":2974,"color":2975},"pro","5BD3CB",{"name":2977,"color":2978},"upstream","78bddb",2415,"og:fields in my 100% clean saas template doesn't shows on facebook, and your own public saas template don't show the og:image","2024-10-22T09:40:37Z","https://github.com/nuxt/ui/issues/2415",0.705116,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRNbM6kKHaXIlG8ns0lPTnJjoEi3zM-WwVWDFZR7yYus":-1},"/nuxt/ui/3125"]