\n );\n});\n```\n\nhttps://codesandbox.io/p/devbox/dreamy-kepler-dqcx4s\n\n### Description\n\nWhen using the `UIcon` component in a JSX/TSX environment, it triggers a \"Maximum call stack size exceeded\" error. The issue appears to be caused by a circular reference in the `Icon.vue` component where it might be incorrectly referencing itself instead of the Nuxt UI icon.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3170,3173,3174],{"name":3171,"color":3172},"bug","d73a4a",{"name":3143,"color":3144},{"name":3146,"color":3147},3671,"Maximum call stack size exceeded when using UIcon in JSX/TSX environment","2025-03-24T15:05:07Z","https://github.com/nuxt/ui/issues/3671",0.7492685,{"description":3181,"labels":3182,"number":3185,"owner":3149,"repository":3150,"state":3162,"title":3186,"updated_at":3187,"url":3188,"score":3189},"### Environment\n\nOperating System: `Darwin`\nNode Version: `v22.11.0`\nNuxt Version: `3.14.1592`\nCLI Version: `3.16.0`\nNitro Version: `2.10.4`\nPackage Manager: `npm@10.9.0`\nBuilder: -\nUser Config: `default`\nRuntime Modules: `@nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.2, @nuxt/image@1.8.1`\nBuild Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nhttps://github.com/makvv4/nuxtui3-avatar-bug-reproduction\n\n### Description\n\nIn the markup we see the correct link to the image, but in the avatar component only a fallback is displayed.\nIn the Network tab, you can see that there are multiple requests made at the same time: one with the correct link, and another request links to the localhost.\n\nThe provider is located in `/providers/my-img-provider.ts`\nAnd config looks like:\n```javascript\nexport default defineNuxtConfig({\n devtools: { enabled: true },\n modules: ['@nuxt/ui', '@nuxt/eslint', '@nuxt/image'],\n css: ['~/assets/css/main.css'],\n\n future: {\n compatibilityVersion: 4,\n },\n\n compatibilityDate: '2024-11-27',\n\n image: {\n providers: {\n myImgProvider: {\n provider: '~~/providers/my-img-provider.ts',\n },\n },\n provider: 'myImgProvider',\n },\n})\n```\n\n### Additional context\n\n\n\n\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[3183,3184],{"name":3171,"color":3172},{"name":3143,"color":3144},2857,"[v3][UAvatar] `UAvatar` breaks when using `@nuxt/image` with custom provider","2025-01-11T15:14:06Z","https://github.com/nuxt/ui/issues/2857",0.7542905,{"description":3191,"labels":3192,"number":3195,"owner":3149,"repository":3150,"state":3162,"title":3196,"updated_at":3197,"url":3198,"score":3199},"### Environment\n\n- Nuxt UI Version: v3.0.0-alpha.7\n- Browser: Chrome | Opera Gx\n- Operating System: Android 12\n\n### Version\n\nv3.0.0-alpha.7\n\n### Reproduction\n\nAfter Adding `overflow-x: auto` Preview\n\n\n\n\n### Description\n\nIn the [NavigationMenu](https://ui3.nuxt.dev/components/navigation-menu) component of Nuxt UI v3.0.0-alpha.7, the horizontal orientation is not displaying correctly due to lack of horizontal overflow handling. When there are multiple items in the menu, items overflow outside the viewport instead of creating a scrollable area. Adding `overflow-x: auto` styling could resolve this issue and improve usability.\n\n### Additional context\n\nWithout `overflow-x: auto` in [NavigationMenu](https://ui3.nuxt.dev/components/navigation-menu)\n\n\n\n\n\n### Logs\n\n_No response_",[3193,3194],{"name":3171,"color":3172},{"name":3143,"color":3144},2468,"Navigation Menu Overflow Bug in Nuxt UI v3.0.0-alpha.7","2025-03-20T00:49:15Z","https://github.com/nuxt/ui/issues/2468",0.75788885,{"description":3201,"labels":3202,"number":3206,"owner":3149,"repository":3150,"state":3162,"title":3207,"updated_at":3208,"url":3209,"score":3210},"### Description\n\nThere is currently no easy way to know what state the modal is in. Adding a `toggle` method would make life very much easier.\n\nI'm willing to make a PR\n\n### Additional context\n\n_No response_",[3203,3204,3205],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},3720,"feat: add toogle for useOverlay","2025-04-09T15:26:14Z","https://github.com/nuxt/ui/issues/3720",0.763178,{"description":3212,"labels":3213,"number":3216,"owner":3149,"repository":3150,"state":3162,"title":3217,"updated_at":3218,"url":3219,"score":3220},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v20.16.0`\n- Nuxt Version: `3.16.1`\n- CLI Version: `3.23.1`\n- Nitro Version: `2.11.7`\n- Package Manager: `pnpm@10.6.3`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `vite`, `colorMode`, `nitro`, `future`, `compatibilityDate`, `hub`, `app`, `schemaOrg`, `i18n`\n- Runtime Modules: `@nuxthub/core@0.8.18`, `@nuxt/ui@3.0.0`, `@nuxtjs/i18n@9.3.2`, `@nuxtjs/seo@3.0.1`, `nuxt-auth-utils@0.5.17`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/dry-sun-8ddkqr\n\n### Description\n\nThe events of the `USelectMenu` do not work as intended. As you can see in the reproduction, the `change` event of the `UForm` is expected to be emitted every time you select/deselect/create an item, but instead it's emitted only a few seemingly random times.\n\nSwitching to the `input` event on the form has the same random behavior.\n\nI am also surprised programmatically changing the list of values doesn't trigger the `update` event on the `USelectMenu`, but that could be by design and is not really the blocking issue here.\n\nMy reproduction code is a simplification of my real code. It is very similar to the documentation example for creating items, main difference is the multi selection. However the issue also occurs without multi selection.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3214,3215],{"name":3171,"color":3172},{"name":3143,"color":3144},3660,"`USelectMenu` doesn't emit `UForm`.`change` as expected","2025-04-04T16:14:05Z","https://github.com/nuxt/ui/issues/3660",0.7670053,{"description":3222,"labels":3223,"number":3224,"owner":3149,"repository":3225,"state":3162,"title":3226,"updated_at":3227,"url":3228,"score":3229},"Hello,\n\nUmami recently released a [new version](https://github.com/umami-software/umami/releases/tag/v2.18.0) with the possibility to set an [unique id](https://umami.is/docs/tracker-functions#sessions)\n\nUsing the proxy.identify works but for the moment the IDE display a red error due to the fact that the first parameter is a string. \n\nWould it be possible to update the interface of identify to something like `Record\u003Cstring, any> | string`\n\n",[],459,"scripts","Umami 2.18 support of Distinct ID","2025-06-02T03:43:11Z","https://github.com/nuxt/scripts/issues/459",0.7697527,{"description":3231,"labels":3232,"number":3233,"owner":3149,"repository":3234,"state":3162,"title":3235,"updated_at":3236,"url":3237,"score":3238},"Blog page:\n\n[Blog](https://nuxt.com/blog) > Release - January 30, 2023\n\nModule page:\n\n[Modules](https://nuxt.com/modules) > Security (module category)",[],1508,"nuxt.com","Blog / Module: Improve back button to leverage breadcrumb instead","2024-02-22T15:18:14Z","https://github.com/nuxt/nuxt.com/issues/1508",0.77658325,{"description":3240,"labels":3241,"number":3245,"owner":3149,"repository":3150,"state":3162,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Description\n\n\n## 🔧 Current Behavior\n\nThe `deferInputValidation` parameter in `useFormField` is currently hardcoded in the `Input` component:\n\n```ts\nconst { emitFormBlur, emitFormInput, /* ... */ } = useFormField\u003CInputProps>(props, { \n deferInputValidation: false // Hardcoded\n})\n```\n\nThis limits flexibility, as consumers of the `Input` component cannot control validation timing behavior (e.g., validate on blur vs. validate on input).\n\n## ✅ Proposed Solution\n\nMake `deferInputValidation` configurable via a component prop:\n\n1. **Pass dynamic value to `useFormField`:**\n\n```ts\nuseFormField\u003CInputProps>(props, {\n deferInputValidation: props.deferInputValidation\n})\n```\n\n2. **Update the component props interface:**\n\n```ts\ndeferInputValidation?: boolean\n```\n\n---\n\n## 💡 Use Cases\n\n- **Delayed validation** for complex, interdependent form fields \n- **Immediate validation** for sensitive or critical fields \n- Flexibility for UX patterns like **\"validate-on-blur\"** or **\"validate-as-you-type\"**\n\n---\n\n## 🔁 Alternatives Considered\n\n- **Wrapper Component**: Adds unnecessary complexity \n- **Global Form-Level Config**: Less flexible than per-field control\n\n---\n\n## 🧪 Testing Impact\n\n- Covered by existing validation tests with both `true` and `false` cases\n\n---\n\n## 📚 Documentation\n\nRequires updates to:\n\n- Component prop API \n- Form validation best practices\n\n---\n\n## ⚙️ Why This Matters\n\nThis change supports **Inversion of Control** — empowering component consumers to control validation timing based on specific UX needs.\n```\n\n### Additional context\n\n_No response_",[3242,3243,3244],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},3810,"[UForm] Feature Request: Make deferInputValidation Configurable in useFormField","2025-04-20T15:25:42Z","https://github.com/nuxt/ui/issues/3810",0.78890026,["Reactive",3251],{},["Set"],["ShallowReactive",3254],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$faCEwhQ28uGx07V9Ee0VfqtiJKJsX_alz3LnxhWZ6kAs":-1},"/nuxt/ui/3126"]