\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n```shell-script\r\nTS2322: Type 'string | null | undefined' is not assignable to type 'string | number | undefined'.\r\n```\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nconst value = ref\u003Cboolean|undefined>();\r\nconst options = [\r\n {\r\n label: 'Yes',\r\n value: true\r\n },\r\n {\r\n label: 'No',\r\n value: false\r\n },\r\n {\r\n label: 'None selected',\r\n value: undefined\r\n }\r\n];\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CUSelectMenu\r\n :options=\"options\"\r\n v-model=\"value\"\r\n value-attribute=\"value\" option-attribute=\"label\"\r\n />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n```shell-script\r\nTS2322: Type 'boolean | undefined' is not assignable to type 'string | number | Record\u003Cstring, any> | unknown[] | undefined'.\r\n```\r\n\r\n### Additional context\r\n\r\n\r\n### Logs\r\n\r\n```shell-script\r\napp.vue:14:15 - error TS2322: Type 'string | null | undefined' is not assignable to type 'string | number | undefined'.\r\n\r\n14 \u003CUInput v-model.trim=\"inputValue\" />\r\n ~~~~~~~~~~\r\n\r\n node_modules/@nuxt/ui/dist/runtime/components/forms/Input.vue.d.ts:244:5\r\n 244 modelValue: string | number;\r\n ~~~~~~~~~~\r\n The expected type comes from property 'modelValue' which is declared here on type 'Partial\u003C{ size: InputSize; ui: any; id: string; icon: string; color: any; type: string; class: any; name: string; modelValue: string | number; leading: boolean; variant: InputVariant; ... 12 more ...; modelModifiers: { ...; }; }> & Omit\u003C...> & Record\u003C...>'\r\n\r\n\r\nFound 1 error in app.vue:14\r\n```\r\n",[2941,2942,2945],{"name":2922,"color":2923},{"name":2943,"color":2944},"closed-by-bot","ededed",{"name":2946,"color":2944},"stale","closed","Unable to use boolean values with USelectMenu or null with UInput","2025-06-19T02:12:37Z","https://github.com/nuxt/ui/issues/1710",0.69465166,{"description":2953,"labels":2954,"number":2961,"owner":2931,"repository":2931,"state":2947,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.11`\r\n- Nitro Version: `0.5.4`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-xemd3s?file=app.tsx\n\n### Describe the bug\n\ngetting this typescript error when using an onClick handler in a tsx file:\r\n\r\n> Type '() => void' is not assignable to type 'MouseEvent'.(2322)\r\n> runtime-dom.d.ts(1407, 15): The expected type comes from property 'onClick' which is declared here on type 'ElementAttrs\u003CButtonHTMLAttributes>'\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2955,2958],{"name":2956,"color":2957},"3.x","29bc7f",{"name":2959,"color":2960},"upstream-bug","B60205",15156,"typescript error with event handlers in tsx","2023-01-19T17:45:33Z","https://github.com/nuxt/nuxt/issues/15156",0.7030641,{"description":2967,"labels":2968,"number":2979,"owner":2931,"repository":2931,"state":2947,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Environment\r\n\r\napp\r\n```\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.6.5`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `npm@9.5.1`\r\n- Builder: `vite`\r\n- User Config: `extends`, `typescript`, `devtools`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n```\r\n\r\nlayer\r\n```\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.6.5`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `npm@9.5.1`\r\n- Builder: `vite`\r\n- User Config: `typescript`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n```\r\n\r\n### Reproduction\r\n\r\n1. clone repo https://github.com/DawidKopys/nuxt-h3-event-ts-error-repro\r\n2. run `npm i` in nuxt-layer directory\r\n3. run `npm i` in app directory\r\n4. run `npx nuxi typecheck` / `npm run dev` / `npx vue-tsc --noEmit` inside app directory. You should get below error:\r\n\r\n```\r\nNuxi 3.6.5 3:57:55 PM\r\n../nuxt-layer/server/api/foo.ts:7:13 - error TS2345: Argument of type 'H3Event' is not assignable to parameter of type 'H3Event\u003CEventHandlerRequest>'.\r\n\r\n7 setCookie(event, 'someCookieName', 'someCookieValue')\r\n ~~~~~\r\n\r\n../nuxt-layer/server/utils/someUtil.ts:6:13 - error TS2345: Argument of type 'H3Event' is not assignable to parameter of type 'H3Event\u003CEventHandlerRequest>'.\r\n Type 'H3Event' is missing the following properties from type 'H3Event\u003CEventHandlerRequest>': method, headers, toJSON, fetch, $fetch\r\n\r\n6 setCookie(event, 'someCookieName', 'someCookieValue')\r\n ~~~~~\r\n\r\n\r\nFound 2 errors in 2 files.\r\n\r\nErrors Files\r\n 1 ../nuxt-layer/server/api/foo.ts:7\r\n 1 ../nuxt-layer/server/utils/someUtil.ts:6\r\n```\r\n\r\n### Describe the bug\r\n\r\n- `app` has dependency `h3` installed with version `1.8.0`\r\n- `nuxt-layer` has dependency `h3` installed with version `1.7.1` (forced with `overrides` field in layer's `package.json` - for simplicity - the effect would be exactly the same if layer had `1.7.1` version locked with its `package-lock.json`)\r\n\r\nAs a result, I am getting typescript errors if **some** utils are imported manually from `h3` and others are auto-imported. Layer file `server/api/foo.ts` shows simple example of this scenario. In this file, `defineEventHandler` is imported manually, while function `setCookie` is auto imported - we get ts error because of that.\r\n\r\nThere is a simple solution for this exact situation - don't import `defineEventHandler` manually. If done so, there are no ts errors for this file.\r\n\r\nHowever, sometimes we might need to import something manually from our dependency. File `server/utils/someUtil.ts` serves as an example of such case.\r\nHere, we have some utility function, which accepts `event` as its argument. In order to type the parameter we need to import `H3Event` from `h3`. This function also uses `setCookie` function which is auto imported.\r\nAgain, we get ts error as a result.\r\n\r\n**Workaround** \r\nImporting everything manually from our `h3` dependency fixes the problem - we no longer get ts errors.\r\nWe no longer get the benefit of auto imports though.\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_",[2969,2972,2973,2976],{"name":2970,"color":2971},"types","2875C3",{"name":2956,"color":2957},{"name":2974,"color":2975},"dx","C39D69",{"name":2977,"color":2978},"layers","006B75",22726,"TypeScript errors when layer and app have different dependency versions","2024-05-24T09:56:28Z","https://github.com/nuxt/nuxt/issues/22726",0.70709395,{"description":2985,"labels":2986,"number":2997,"owner":2931,"repository":2931,"state":2947,"title":2998,"updated_at":2999,"url":3000,"score":3001},"### Environment\r\n\r\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.11.1\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.9.3\r\n- Package Manager: pnpm@8.15.4\r\n- Builder: -\r\n- User Config: runtimeConfig, modules, $test, devtools, experimental, vue, tailwindcss, app, nitro, typescript, pinia\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.11.5-1709108338.2ae28e5, @vueuse/nuxt@10.9.0, nuxt-headlessui@1.1.5, @pinia/nuxt@0.5.1, @nuxtjs/fontaine@0.4.1, @formkit/auto-animate/nuxt@0.8.1\r\n- Build Modules: -\r\n------------------------------\r\n\r\n👉 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\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nOn a project using NuxtIslands (via server components), and storybook, running the `build-storybook` command fails with the following error:\r\n\r\n```\r\n=> Failed to build the preview 10:43:12 AM\r\nTypeError: Cannot create property 'ActionMessage' on string './node_modules/.pnpm/@storybook+builder-vite@7.6.17_typescript@5.4.2_vite@5.1.6/node_modules/@storybook/builder-vite/input/iframe.html' 10:43:12 AM\r\n at config (file://./node_modules/.pnpm/nuxt@3.10.3_@types+node@18.19.23_eslint@8.57.0_typescript@5.4.2_vite@5.1.6_vue-tsc@1.8.27/node_modules/nuxt/dist/index.mjs:1866:62)\r\n```\r\n\r\n### Describe the bug\r\n\r\nIn `packages/nuxt/src/components/islandsTransform.ts`, the `componentsChunkPlugin` function makes the following type assertion ` (config.build.rollupOptions.input as Record\u003Cstring, string>)`.\r\n\r\n\r\n```typescript\r\nexport const componentsChunkPlugin = createUnplugin((options: ComponentChunkOptions) => {\r\n const { buildDir } = options\r\n return {\r\n name: 'componentsChunkPlugin',\r\n vite: {\r\n async config (config) {\r\n const components = options.getComponents()\r\n config.build = config.build || {}\r\n config.build.rollupOptions = config.build.rollupOptions || {}\r\n config.build.rollupOptions.output = config.build.rollupOptions.output || {}\r\n config.build.rollupOptions.input = config.build.rollupOptions.input || {}\r\n // don't use 'strict', this would create another \"facade\" chunk for the entry file, causing the ssr styles to not detect everything\r\n config.build.rollupOptions.preserveEntrySignatures = 'allow-extension'\r\n for (const component of components) {\r\n if (component.mode === 'client' || component.mode === 'all') {\r\n (config.build.rollupOptions.input as Record\u003Cstring, string>)[component.pascalName] = await resolvePath(component.filePath)\r\n }\r\n }\r\n },\r\n```\r\n\r\n`config.build.rollupOptions.input` is declared as `type InputOption = string | string[] | { [entryAlias: string]: string }`. When using storybook and `@storybook/builder-vite`, `config.build.rollupOptions.input` is a `string`, with a value similar to `/node_modules/.../@storybook/builder-vite/input/iframe.html`.\r\n\r\nWould a PR that checks first for the type of `config.build.rollupOptions.input` make sense? Something along the lines of:\r\n\r\n```typescript\r\n if (component.mode === 'client' || component.mode === 'all') {\r\n if ('object' === typeof config.build.rollupOptions.input && !Array.isArray(config.build.rollupOptions.input)) \r\n (config.build.rollupOptions.input as Record\u003Cstring, string>)[component.pascalName] = await resolvePath(component.filePath)\r\n```\r\n\r\n### Additional context\r\n\r\nDisabling server components is a workaround that fixes the issue when running or building storybook. I have them enabled when building the app, but disabled when building statically with storybook.\r\n\r\n### Logs\r\n\r\n_No response_",[2987,2990,2991,2994],{"name":2988,"color":2989},"good first issue","fbca04",{"name":2956,"color":2957},{"name":2992,"color":2993},"🔨 p3-minor","FBCA04",{"name":2995,"color":2996},"server components","839413",26220,"TypeError in `islandsTransform.ts` affecting storybook","2024-04-03T10:36:16Z","https://github.com/nuxt/nuxt/issues/26220",0.7075091,{"description":3003,"labels":3004,"number":3012,"owner":2931,"repository":2931,"state":2947,"title":3013,"updated_at":3014,"url":3015,"score":3016},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, modules, typescript\r\n- Runtime Modules: @nuxtseo/module@2.0.0-beta.15\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\n- minimal changes to nuxt config adding `typeCheck: true` and `compilerOptions.noUncheckedIndexedAccess: true`\r\n\r\nhttps://stackblitz.com/edit/github-vdxk2t?file=nuxt.config.ts\r\n\r\n### Describe the bug\r\n\r\nThis highlights an issue when trying to use tsconfig features e.g. `noUncheckedIndexedAccess` or `noUnusedLocals` etc. in a nuxt project to provide stricter code conformance. Any nuxt module you have installed will also be checked for these same rules.\r\n\r\nThis effectively means you cannot use any of the tsconfig rules for the risk of a module developer not adhering to those same standards.\r\n\r\nNuxt should not be type checking any installed modules as part of build with the same tsconfig rules defined at the project level. Providing access to all tsconfig properties is misleading as they effectively don't work with the nuxt ecosystem unless you have a raw project.\r\n\r\nThe repro and logs below show how this fails for the `@nuxtseo/module` module but this error is present in a number of modules I have tried to use e.g. `content`\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nERROR 21:54:09\r\n ERROR(vue-tsc) Type '{ icon: string; label: false; ariaLabel: string | undefined; current?: boolean | undefined; disabled?: boolean | undefined; to?: string | undefined; separator?: string | undefined; hideSeparator?: boolean | undefined; ui?: { ...; } | undefined; }' is not assignable to type 'BreadcrumbItemProps'.\r\n Types of property 'to' are incompatible.\r\n Type 'string | undefined' is not assignable to type 'string'.\r\n Type 'undefined' is not assignable to type 'string'.\r\n FILE /home/projects/github-vdxk2t/node_modules/nuxt-seo-ui/dist/runtime/components/Breadcrumb.vue:46:5\r\n\r\n 44 | }\r\n 45 | if (props.homeIcon) {\r\n > 46 | items[0] = {\r\n | ^^^^^^^^\r\n 47 | ...items[0],\r\n 48 | icon: 'material-symbols:home-outline-rounded',\r\n 49 | label: false,\r\n\r\n[vue-tsc] Found 1 error. Watching for file changes. (x3)\r\n```\r\n```\r\n",[3005,3008,3009,3010,3011],{"name":3006,"color":3007},"discussion","538de2",{"name":2970,"color":2971},{"name":2956,"color":2957},{"name":2922,"color":2923},{"name":2992,"color":2993},23609,"`typeCheck` reports errors from modules when using `tsconfig` rules","2023-11-30T07:26:56Z","https://github.com/nuxt/nuxt/issues/23609",0.709279,{"description":3018,"labels":3019,"number":3028,"owner":2931,"repository":2931,"state":2947,"title":3029,"updated_at":3030,"url":3031,"score":3032},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v18.16.0\n- Nuxt Version: 3.4.3\n- Nitro Version: 2.4.0\n- Package Manager: pnpm@8.5.0\n- Builder: vite\n- User Config: experimental, modules, colorMode\n- Runtime Modules: @unocss/nuxt@0.51.12, @vueuse/nuxt@10.1.2, nuxt-icon@0.4.0, nuxt-swiper@1.1.0, @nuxt/devtools@0.4.6, @nuxt/image-edge@1.0.0-28020728.5df24eb, @nuxtjs/color-mode@3.2.0\n- Build Modules: -\n\n### Reproduction\n\n\n\nThis error doesn't seem to be reproducible on Stackblitz so I have included a [github repo](https://github.com/tobychidi/nuxt-utils-import-error)\n\n### Describe the bug\n\nWhen functions are auto-imported from utils/ composables and used in Vue SFC Template, VsCode throws and error. Yes, I use the latest volar. This error appeared after `pnpm up` That bumped my Vue version to 3.3.1.\n\nI have not tried reverting Vue versions though. \n\n### Additional context\n\nExample: \n```\nProperty 'useShowSnack' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: { key?: string | number | symbol | undefined; ref?: VNodeRef | undefined; ref_for?: boolean | undefined; ... 8 more ...; style?: unknown; }; ... 10 more ...; $watch\u003CT extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (arg...'.ts(2339)\n```\n\n_No response_\n\n### Logs\n\n_No response_",[3020,3021,3024,3027],{"name":2956,"color":2957},{"name":3022,"color":3023},"workaround available","11376d",{"name":3025,"color":3026},"upstream","E8A36D",{"name":2959,"color":2960},20827,"TS Error with auto-imports from composables and utils in Vue Template after 3.3","2024-11-07T20:13:37Z","https://github.com/nuxt/nuxt/issues/20827",0.7138507,{"description":3034,"labels":3035,"number":3044,"owner":2931,"repository":2932,"state":2947,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### Description\n\nNow that nuxt by default doesn't enable shamefully-hoist we cannot import from tailwind directly because it is a subdependancy of @nuxt/ui.\r\n\r\n```ts\r\nimport type { Config } from \"tailwindcss\";\r\n\r\n// - or -\r\n\r\n/** @type {import('tailwindcss').Config} */\r\n```\r\n So this gives `Cannot find module 'tailwindcss' or its corresponding type declarations.` error. This means that we get no typesafety in our tailwind.config.[ts|js] files.\r\n\r\nDocumentation specifically [3.theming.md](https://github.com/nuxt/ui/blob/dev/docs/content/1.getting-started/3.theming.md) would also need to be updated to reflect these changes.\r\n\r\n\r\nThe same issue also effects the `icon`, `colorMode` and `tailwindcss` keys in the `nuxt.config.ts`.\r\n\r\n```ts\r\nexport default defineNuxtConfig({\r\n compatibilityDate: \"2024-04-03\",\r\n devtools: { enabled: true },\r\n modules: [\"@nuxt/ui\"],\r\n ui: {},\r\n icon: {}, // \u003C- typed any\r\n});\r\n```\r\n\r\n`.nuxt/types/schema.d.ts` file is the file that defines the types for the `nuxt.config.ts` and because it is a part of our project. The imports from the individual subdependency modules like `@nuxt/icon` are broken.\r\n\r\n```ts\r\n// .nuxt/types/schema.d.ts\r\ninterface NuxtConfig {\r\n [\"icon\"]?: typeof import(\"@nuxt/icon\").default extends NuxtModule\u003Cinfer O> ? Partial\u003CO> : Record\u003Cstring, any>, .....\r\n // ^? any\r\n}\r\n```\r\n\r\nIf it is the case that we cannot manipulate the output of `schema.d.ts` file to import the re-exported types rather than the original ones we can add a [type template](https://nuxt.com/docs/api/kit/templates#addtypetemplate) that would import and declare the default export of the respective module like this \r\n\r\n```ts\r\nimport type { ReExportedIconModuleType } from \"@nuxt/ui/types\"\r\ndeclare module \"@nuxt/icon\" {\r\n export default ReExportedIconModuleType;\r\n}\r\n```\n\n### Additional context\n\n_No response_",[3036,3039,3042,3043],{"name":3037,"color":3038},"enhancement","a2eeef",{"name":3040,"color":3041},"triage","ffffff",{"name":2943,"color":2944},{"name":2946,"color":2944},2032,"Re-export types of subdependencies","2025-06-18T09:06:37Z","https://github.com/nuxt/ui/issues/2032",0.7156074,{"labels":3050,"number":3055,"owner":2931,"repository":2931,"state":2947,"title":3056,"updated_at":3057,"url":3058,"score":3059},[3051,3052],{"name":2956,"color":2957},{"name":3053,"color":3054},"pending triage","E99695",14561,"Type errors in generated `components.d.ts`","2023-01-19T17:37:13Z","https://github.com/nuxt/nuxt/issues/14561",0.7171305,{"description":3061,"labels":3062,"number":3066,"owner":2931,"repository":2932,"state":2947,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-beta.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-beta.2\n\n### Reproduction\n\nHere's a demo (https://codesandbox.io/p/devbox/nuxtui3-bug-3432-sphrpl)\n\n**index.vue**\n```\n\u003Ctemplate>\n \u003CUContainer>\n \u003CFooModal @some-action=\"fnHandleAction\" /> \u003Cbr />\n \u003CUButton @click=\"fnOpenModal\">Open FooModal from code\u003C/UButton>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n import { FooModal } from '#components';\n\n const overlay = useOverlay();\n\n const foo = overlay.create(FooModal);\n\n const fnOpenModal = async () => {\n foo.open();\n };\n\n const fnHandleAction = (action) => {\n console.log(\"Handle FooModal action: \", action);\n };\n\u003C/script>\n```\n\n**FooModal**\n```\n\u003Ctemplate>\n \u003CUModal v-model:open=\"open\" title=\"Foobar\">\n \u003CUButton label=\"Open FooModal from modal\" color=\"neutral\" variant=\"subtle\" />\n\n \u003Ctemplate #body>\n \u003CUButton @click=\"click()\" >Submit\u003C/UButton>\n \u003C/template>\n \u003C/UModal>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n const open = ref(false);\n\n const emits = defineEmits(['some-action']);\n\n const click = () => {\n console.log(\"clicked from inside the modal\");\n emits('some-action', 'closing'); //emits does not work if Modal opened using useOverlay.\n open.value = false; //closing modal does not work if Modal opened using useOverlay.\n };\n\u003C/script>\n```\n\n### Description\n\nHello Nuxt UI team,\n\nThank you for providing a high-quality UI library. I truly appreciate the effort you put into creating and maintaining it.\n\nI have encountered an issue while using `UModal` in my application. The modal is used to create and/or update database entries, and it needs to be opened in two different ways:\n\n1. Via a `UButton` that is always present on the screen (provided by the modal itself).\n2. Programmatically, through a link in a dropdown menu, using `useOverlay`.\n\nWhen the modal is opened using the first method, everything works as expected. However, when it is opened programmatically using the second method, the modal does not behave the same way. Specifically:\n\n- I am unable to trigger an `emit` to notify the parent component that the update was successful.\n- The modal does not close properly using the `open.value = false` technique.\n\nI am unsure if this behavior is intentional or a bug. I was under the impression that `UModal` and `useOverlay` should work seamlessly together and exhibit consistent behavior. Could you please confirm whether this is a valid concern?\n\nThank you for your time and attention to this matter. I look forward to your guidance.\n\n**Note**: You'll also notice that the button within the modal appears on the screen when opened using `useOverlay`. It would be helpful if it could be hidden automatically, but I believe this is something I can control easily. As such, I do not consider this to be a bug.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3063,3064,3065],{"name":2922,"color":2923},{"name":2928,"color":2929},{"name":3040,"color":3041},3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.7171353,["Reactive",3072],{},["Set"],["ShallowReactive",3075],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ftz1hWnkLANBkg7ioKOHVAZP1T3KIH5q0B1yBShuVF_U":-1},"/nuxt/ui/2968"]