\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```",[2010,2011],{"name":1996,"color":1997},{"name":1999,"color":2000},2713,"UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.7404445,{"description":2018,"labels":2019,"number":2027,"owner":1985,"repository":2002,"state":1987,"title":2028,"updated_at":2029,"url":2030,"score":2031},"### Description\n\n### Feature Request: Add `variant` and `status-position` props to `UProgress` component\n\n#### Description\nI’m a junior developer, and I’ve been working on enhancing the flexibility of the `Progress` component by adding two new props: `variant` and `status-position`. These props allow for better customization, especially when using the `Progress` component in different design contexts.\n\n- **`variant`**: This prop allows you to choose between two styles for the progress bar: `linear` and `circular`. The `circular` variant provides a circular progress bar instead of the default linear style.\n \n- **`status-position`**: This prop controls the position of the progress status (the percentage or label) relative to the progress bar. The possible values are:\n - `inside`: The status is displayed inside the circle (for the `circular` variant).\n - `outside`: The status is displayed outside the circle.\n\n#### Motivation\nThis update would help in using the `Progress` component more flexibly across different layouts, providing options for both linear and circular progress indicators with customizable label placements.\n\n#### What I've Done\nI’m still a junior developer, so the implementation is not perfect, but a good portion of the work is done. I’ve added the `variant` and `status-position` props to the `Progress` component. I’d love to know if this is something you’d like to integrate into the main repository and whether I can open a pull request for it.\n\n#### Additional Notes\n- The `variant` prop accepts values `linear` or `circular`.\n- The `status-position` prop accepts values `inside` or `outside`.\n \nWould love to hear your thoughts on this approach!\n\n\n### Additional context\n\n[Reka UI : Progress Circular](https://reka-ui.com/examples/progress-circular)",[2020,2023,2026],{"name":2021,"color":2022},"enhancement","a2eeef",{"name":2024,"color":2025},"v3","49DCB8",{"name":1999,"color":2000},3728,"[UProgress]: Add `variant` and `status-position` props","2025-03-29T14:31:22Z","https://github.com/nuxt/ui/issues/3728",0.7442499,{"description":2033,"labels":2034,"number":2038,"owner":1985,"repository":2039,"state":1987,"title":2040,"updated_at":2041,"url":2042,"score":2043},"### Environment\n\nThis is one of the environments i came across the problem:\r\n[11:15:23 AM] Working directory: /Users/lorenzorottigni/Documents/gitlab_private/portfolio.rottigni.tech\r\n[11:15:23 AM] Nuxt project info: (copied to clipboard)\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.13.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: vite\r\n- User Config: ssr, debug, srcDir, serverDir, test, app, modules, css, postcss, unocss, tailwindcss, googleFonts, i18n, nitro, pwa, image, delayHydration, extensions, typescript, builder, vite, vue, runtimeConfig, devServer, sourcemap, experimental\r\n- Runtime Modules: @vueuse/nuxt@10.7.2, @nuxtjs/tailwindcss@6.10.4, @pinia/nuxt@0.5.1, @unocss/nuxt@0.58.3, @nuxtjs/i18n@8.0.0, @nuxt/image@1.3.0, nuxt-jsonld@2.0.8, @kevinmarrec/nuxt-pwa@0.17.0, @nuxtjs/google-fonts@3.1.3, nuxt-calendly@0.1.18, nuxt-delay-hydration@1.3.3, @nuxt/test-utils/module@3.10.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n[11:15:23 AM] 👉 Report an issue: https://github.com/nuxt/nuxt/issues/new\r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://nuxt.com\n\n### Reproduction\n\nThe crucial file is MyComponent.spec.ts:\r\nhttps://stackblitz.com/~/github.com/LorenzoRottigni/nuxt-test-utils-vitest-spy\n\n### Describe the bug\n\nI'm currently facing challenges in testing a component method within a Nuxt environment. Specifically, I'm attempting to spy on a component method to test its interactions within template events. Despite researching similar cases online, I've yet to find a clear solution to this issue.\r\n\r\nOne suggestion I encountered was to define the spy before the component mounts. However, I'm unable to access `wrapper.vm` before mount time, complicating this approach. Additionally, I experimented with spying on the global injected `$fetch` method from the 'ofetch' library. Unfortunately, this led to another error regarding the inability to redefine the variable `$fetch` when attempting variations like:\r\n\r\n```javascript\r\nimport OFetch from 'ofetch'\r\nconst spy = vi.spyOn(OFetch, '$fetch')\r\n// or\r\nconst spy = vi.spyOn(global, '$fetch')\r\n// or\r\nconst spy = vi.spyOn({ $fetch }, '$fetch')\r\n```\r\n\r\nIt appears that this issue may not be directly tied to the nuxt-test-utils package. Nevertheless, I wanted to bring it to your attention in the hopes that someone might offer guidance or assistance. I'm eager to find a resolution and would appreciate any insights or suggestions you might have.\r\n\r\nI'm also considering reporting a similar issue to the vue-test-utils package, as I suspect that this problem might be reproducible outside of the Nuxt environment.\r\n\r\nThank you for your time and assistance.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2035],{"name":2036,"color":2037},"pending triage","5D08F5",763,"test-utils","Unable to use vitest spy within nuxt 3 component methods.","2024-05-28T15:28:23Z","https://github.com/nuxt/test-utils/issues/763",0.74492055,{"description":2045,"labels":2046,"number":2050,"owner":1985,"repository":1986,"state":2051,"title":2052,"updated_at":2053,"url":2054,"score":2055},"### Environment\n\nNot needed\n\n### Reproduction\n\nNot necessary, any SSR/Prerender Nuxt will fail\n\n### Describe the bug\n\nI'm just creating this issue to warn anyone that is using Cloudflare with Nuxt SSR\r\n\r\nDISABLE ASSET MINIFICATION, it breaks Vue hydration\r\n\r\n\r\nI've spent weeks trying to fix it, and it was as simple as unchecking these boxes, hope it helps anyone\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2047],{"name":2048,"color":2049},"documentation","9DE2BA",1457,"closed","SSR Issues with Coudflare Pages (SOLVED)","2023-12-27T17:11:13Z","https://github.com/nuxt/nuxt.com/issues/1457",0.6977998,{"description":2057,"labels":2058,"number":2064,"owner":1985,"repository":2002,"state":2051,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### Version\n\nv3 latest commit\n\n### Description\n\nI noticed the following behavior:\n\n- When the data prop of a `\u003CUTable>` changes, the rows dont get properly unmounted\n- This results in components within a row to never have `unMounted` being called (only if the amount of rows is less for the ones that get removed)\n- Further this can result in a bugs and unexpected behavior because for components only the props change but the setup function is not called again\n\n### Reproduction\n\nConsider the following simplified example. The badge never changes color. Also if one would use `onMounted`/`onUnmounted` within the badge component they would not get triggered when the data changes (only if the amount of rows change).\n\n**my-badge.vue**\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst props = defineProps\u003C{\n status: 'yes' | 'no';\n}>();\n\nswitch (props.status) {\n case 'yes':\n color = 'success';\n break;\n case 'no':\n color = 'error';\n break;\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUBadge :color variant=\"subtle\">{{ props.status }}\u003C/UBadge>\n\u003C/template>\n```\n\n**my-table.vue**\n```vue\n\u003Cscript setup lang=\"ts\">\n const page = ref(1);\n const { data } = useFetch('url', { query: { page }}); // This gets refetched when `page.value` changes\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUTable :data :columns>\n \u003Ctemplate #status-cell=\"{ row }\">\n \u003CMyBadge :status=\"row.original.status\" />\n \u003C/template>\n \u003C/UTable>\n\u003C/template>\n```\n\n### Additional context\n\nI think this was already the case within v2: There I have a table that contains `\u003CNuxtImg />` tags. When the data changes (e.g. by pagination) the new rows are displayed with the images of the old row until the new images are loaded. That is probably because the `\u003CNuxtImg />` components dont get removed and replaced by all new ones.\n\nLet me know if I should create a reproduction repo\n",[2059,2060,2063],{"name":1996,"color":1997},{"name":2061,"color":2062},"needs reproduction","CB47CF",{"name":2024,"color":2025},3043,"Table rows dont get deleted / unmounted when data changes","2025-03-28T17:35:58Z","https://github.com/nuxt/ui/issues/3043",0.70227826,{"description":2070,"labels":2071,"number":2073,"owner":1985,"repository":2002,"state":2051,"title":2074,"updated_at":2075,"url":2076,"score":2077},"# tldr\r\nWhen using nuxt UI v2.18.5 or higher -> `\u003CUInput value=\"'12714274'\" readonly />` change it to `\u003CUInput :model-value=\"'12714274'\" readonly />`\r\n\r\n\r\n\r\n--------- \r\n\r\n\r\n### Version\r\n\r\nedit: v2.18.5\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-uds7la?file=app.vue\r\n\r\n### Description\r\n\r\nSo i have a few grouped form inputs and noticed all values being empty since last update, reverted back to 2.18.4 and worked again. \r\n\r\n_(👀 or you can tell me im using it wrong)_\r\n\r\n### Why i am using :value= ? \r\n\r\n```\r\n\u003CUInput\r\n :value=\"firstname\"\r\n @input=\"$emit('update:firstname', $event.target.value)\"\r\n />\r\n \u003CUInput\r\n :value=\"lastname\"\r\n @input=\"$emit('update:lastname', $event.target.value)\"\r\n />\r\n```\r\n\r\nand using \r\n```\r\n\u003CAccountFormDetails\r\n v-model:firstname=\"formState.firstname\"\r\n v-model:lastname=\"formState.lastname\"\r\n/>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nno logs,no errors\r\n```\r\n\r\nedit: added repro\r\nedit: pinpointed on 2.18.5, this happened between 18.4 and 18.5",[2072],{"name":1996,"color":1997},2238,"UInput :value not working in v2.18.5","2024-09-25T08:36:59Z","https://github.com/nuxt/ui/issues/2238",0.70834047,{"description":2079,"labels":2080,"number":2088,"owner":1985,"repository":2002,"state":2051,"title":2089,"updated_at":2090,"url":2091,"score":2092},"### 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.)",[2081,2082,2085],{"name":1996,"color":1997},{"name":2083,"color":2084},"pro","5BD3CB",{"name":2086,"color":2087},"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.71686226,{"description":2094,"labels":2095,"number":2098,"owner":1985,"repository":2002,"state":2051,"title":2099,"updated_at":2100,"url":2101,"score":2102},"### Description\n\nI need to create custom components including @nuxt/ui components and forward props, emits on this components.\n\nWhen importing (in vue file)\n```ts\nimport type { FormFieldProps, FormFieldSlots } from '@nuxt/ui';\n\nconst props = defineProps\u003CFormFieldProps & { operations?: T[] }>();\nconst slots = defineEmits\u003CFormFieldSlots>();\n\nconst formFieldProps = reactiveOmit(props, ['operations']);\n```\nI receive this error on execution :\n```log\nIdentifier 'appConfig' has already been declared.\n\nInternal server error: Identifier 'appConfig' has already been declared. (105:6) 09:22:04\n Plugin: vite:vue\n File: .../app/pages/ResDossier/components/MyCustomComponent.vue:105:6\n at toParseError (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parse-error.ts:95:45)\n at raise (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/tokenizer/index.ts:1497:19)\n at checkRedeclarationInScope (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/util/scope.ts:155:19)\n at declareName (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/util/scope.ts:109:12)\n at declareName (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/plugins/typescript/scope.ts:89:11)\n at declareNameFromIdentifier (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parser/lval.ts:739:16)\n at checkIdentifier (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parser/lval.ts:734:12)\n at checkLVal (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parser/lval.ts:636:12)\n at parseVarId (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/parser/statement.ts:1605:10)\n at parseVarId (.../node_modules/.pnpm/@babel+parser@7.26.5/node_modules/@babel/parser/src/plugins/typescript/index.ts:3463:13)\n```\n\nIs there another way to import theses types ?",[2096,2097],{"name":1996,"color":1997},{"name":2024,"color":2025},3124,"how to import type xxxProps / xxxEmits / xxxSlots","2025-01-27T12:26:22Z","https://github.com/nuxt/ui/issues/3124",0.7244694,["Reactive",2104],{},["Set"],["ShallowReactive",2107],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"MUVaUPK46GYRpSIxTiWXMaq3S0GjQTbCmhQZ_Rzkjfo":-1},"/nuxt/ui/2320"]