\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```",[3180,3181,3182],{"name":3151,"color":3152},{"name":3154,"color":3155},{"name":3157,"color":3158},3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.6619146,{"description":3189,"labels":3190,"number":3191,"owner":3140,"repository":3141,"state":3172,"title":3192,"updated_at":3193,"url":3194,"score":3195},"### 📚 Description\r\n\r\nI got a 404 error when I accessed the **learn more** link on the [cloudflare](https://nuxt.com/deploy/cloudflare) page.\r\nI investigated the cause and found that the URL path was incorrect.",[],1520,"bug: wrong link to Zero-Config Providers","2024-03-03T08:40:08Z","https://github.com/nuxt/nuxt.com/issues/1520",0.6619498,{"description":3197,"labels":3198,"number":3200,"owner":3140,"repository":3160,"state":3172,"title":3201,"updated_at":3202,"url":3203,"score":3204},"### Environment\n\n- Node version: 22.9.0 (Docker image 22.9.0-alpine)\n- Nuxt version: 3.14.1592\n- Package manager: pnpm@9.14.2\n- nuxt/ui module version: 2.19.2\n- package.json\n ```\n {\n \"name\": \"nuxt-app\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\"\n },\n \"dependencies\": {\n \"@nuxt/ui\": \"^2.19.2\",\n \"nuxt\": \"^3.14.1592\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n },\n \"packageManager\": \"pnpm@9.14.2+sha512.6e2baf77d06b9362294152c851c4f278ede37ab1eba3a55fda317a4a17b209f4dbb973fb250a77abc463a341fcb1f17f17cfa24091c4eb319cda0d9b84278387\"\n }\n ```\n- Dockerfile\n ```\n ARG NODE_DOCKER_IMAGE=22.9.0-alpine\n FROM node:$NODE_DOCKER_IMAGE AS base\n \n ARG PORT=3000\n \n ENV NODE_ENV=production\n \n WORKDIR /app\n # Build\n FROM base AS builder\n \n RUN npm install -g pnpm\n \n COPY --link package.json .\n COPY --link pnpm-lock.yaml .\n \n RUN pnpm install --production=true\n \n COPY --link . .\n \n RUN pnpm build\n \n # Run\n FROM base\n \n ENV PORT=$PORT\n \n COPY --from=builder /app/.output /app/.output\n \n COPY --from=builder /app/docker-entrypoint.sh /usr/local/bin/docker-entrypoint\n \n RUN chmod +x /usr/local/bin/docker-entrypoint\n \n ENTRYPOINT [\"docker-entrypoint\"]\n ```\n\n\n### Version\n\nv2.19.2\n\n### Reproduction\n\n1. Create the \"frontend\" Nuxt app `pnpx nuxi@latest init frontend`\n2. `cd frontend`\n3. Add the \"nux/ui\" module `pnpx nuxi@latest module add ui`\n4. Put the Dockerfile described inside the frontend folder\n5. `docker build .`\n\n### Description\n\nThe build fails:\n```\n=> ERROR [builder 6/6] RUN pnpm build 3.4s\n------ \n > [builder 6/6] RUN pnpm build: \n0.512 \n0.512 > nuxt-app@ build /app \n0.512 > nuxt build \n0.512 \n0.658 Nuxt 3.14.1592\n1.374 [nuxt:tailwindcss] ℹ Using default Tailwind CSS file\n1.589 ℹ Nuxt Icon server bundle mode is set to local\n3.009 ℹ Building client...\n3.018 ℹ vite v5.4.11 building for production...\n3.040 ℹ transforming...\n3.350 ℹ ✓ 57 modules transformed.\n3.351 \n3.351 ERROR x Build failed in 331ms\n3.351 \n3.351 \n3.351 ERROR Nuxt Build Error: [vite:css] [postcss] Cannot find module 'tailwindcss/lib/lib/defaultExtractor.js'\n3.351 Require stack:\n3.351 - /app/.nuxt/nuxtui-tailwind.config.cjs\n3.351 file: /app/node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/tailwind.css:undefined:NaN\n3.351 \n3.351 Require stack:\n3.351 - .nuxt/nuxtui-tailwind.config.cjs\n3.351 file: node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/tailwind.css:undefined:NaN\n3.351 at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)\n3.351 at Function.resolve (node:internal/modules/helpers:145:19)\n3.351 at _resolve (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:241814)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:244531)\n3.351 at .nuxt/nuxtui-tailwind.config.cjs:2:60\n3.351 at evalModule (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:247313)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:245241)\n3.351 at .nuxt/tailwind.config.cjs:7:1\n3.351 at evalModule (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:247313)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:245241)\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/load-config.js:56:30\n3.351 at loadConfig (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/load-config.js:58:6)\n3.351 at getTailwindConfig (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:71:116)\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:100:92\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/processTailwindFeatures.js:46:11\n3.351 at plugins (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/plugin.js:38:69)\n3.351 at LazyResult.runOnRoot (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:329:16)\n3.351 at LazyResult.runAsync (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:258:26)\n3.351 at LazyResult.async (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:160:30)\n3.351 at LazyResult.then (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:404:17)\n3.351 \n3.370 ELIFECYCLE Command failed with exit code 1.\n```\n\n### Additional context\n\nMaybe I'm facing the same problem stated in https://github.com/nuxt/ui/issues/1689\n\n### Logs\n\n```shell-script\n\n```",[3199],{"name":3151,"color":3152},2785,"Nuxt Build Error at build time with Docker","2024-11-27T10:23:20Z","https://github.com/nuxt/ui/issues/2785",0.666398,{"description":3206,"labels":3207,"number":3212,"owner":3140,"repository":3160,"state":3172,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### Description\n\nBefore using `nuxt ui`, I briefly skimmed through the repository and found an already closed issue: [3018](https://github.com/nuxt/ui/issues/3018)\n\nThe error and solution mentioned in this issue (the [v2 documentation](https://ui.nuxt.com/getting-started/installation) indeed did not mention the solution) can actually be resolved by adding `tailwindcss@next` to the `peerDependencies` section in the `package.json` file.\n\nThis is because when [nuxi module add](https://github.com/nuxt/cli/blob/1afc06e8d08ea781fc5fede343de8d68865c2b4e/packages/nuxi/src/commands/module/add.ts#L134) installs a module, it not only installs the module itself but also scans the module package's `peerDependencies`.\n\nFor example, when using `nuxi module add pinia`, since `@pinia/nuxt` has `pinia` listed in its `peerDependencies` in the [package.json](https://github.com/vuejs/pinia/blob/3b21e08b6a068d18112b915b83f702fb5504ab73/packages/nuxt/package.json#L51C4-L51C20), both `@pinia/nuxt` and `pinia` will be automatically installed during the module installation.\n\nIf there are dependencies in `peerDependencies` that you do not want `nuxi module` to install automatically, you can use `peerDependenciesMeta` to ignore them, for [example](https://github.com/atinux/nuxt-auth-utils/blob/6b61b8888e3b3c6f60fd5ff767b7f0aa6cf09fc9/package.json#L57):\n\n```\n\"peerDependenciesMeta\": {\n \"pinia\": {\n \"optional\": true\n }\n },\n```\n\nTherefore, Nuxt UI can specify `tailwindcss@next` in the `peerDependencies` of `package.json`, ensuring Tailwind CSS is automatically installed when the Nuxt UI module is installed.\n\nThis solution applies to both v3 and v2.\n\n> PS: I noticed `typescript` in the `peerDependencies` of the v3 package.json. Is this a necessary dependency similar to `tailwindcss`? If not, after adding tailwindcss, perhaps `peerDependenciesMeta` could be used to ignore it.",[3208,3211],{"name":3209,"color":3210},"question","d876e3",{"name":3154,"color":3155},3349,"Add \"tailwindcss@next\" to the \"peerDependencies\" section in the package.json file.","2025-02-21T17:05:10Z","https://github.com/nuxt/ui/issues/3349",0.66851646,{"description":3218,"labels":3219,"number":3222,"owner":3140,"repository":3160,"state":3172,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Description\n\nHello, I just wanted to overwrite shadow-sm with another shadow in the card root slot.\nBut I failed to do so. I tried the :ui way and the app.config.ts way but in both cases the new class \"shadow-card\" ended up BEHIND \"shadow-sm\".\n\n```\n card: {\n slots: {\n root: \"shadow-card\",\n },\n },\n```\n\nSo shadow-card always gets overwritten by shadow-sm cause the code always ends up like this:\n```\n\u003Cdiv class=\"bg-[var(--ui-bg)] ring ring-[var(--ui-border)] divide-y divide-[var(--ui-border)] rounded-[calc(var(--ui-radius)*2)] shadow-sm shadow-card\">\n```\n\nso how can I overwrite shadow-sm here?",[3220,3221],{"name":3209,"color":3210},{"name":3154,"color":3155},2936,"Overwrite css classes of slots","2025-01-08T16:26:22Z","https://github.com/nuxt/ui/issues/2936",0.6688218,{"description":3228,"labels":3229,"number":3232,"owner":3140,"repository":3160,"state":3172,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Description\n\nI want to configure my Nuxt UI v3 project only to use black and white colors with the neutral palette from Tailwind, similar to the one found in shadcn. I understand Nuxt UI supports Tailwind CSS theming, but I’m unsure of the best/recommended way to override all component colors globally",[3230,3231],{"name":3209,"color":3210},{"name":3154,"color":3155},3200,"How to create a black & white only theme in Nuxt UI v3","2025-02-09T12:59:38Z","https://github.com/nuxt/ui/issues/3200",0.6714419,{"description":3238,"labels":3239,"number":3245,"owner":3140,"repository":3160,"state":3172,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/image@1.8.1, @nuxt/content@2.13.4, @nuxthq/studio@1.1.2, @nuxt/ui-pro@3.0.0-alpha.10, @nuxtjs/plausible@1.2.0, @nuxtjs/seo@2.0.2, @vueuse/nuxt@12.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0.alpha10\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/button#loading (example with `loading-auto`)\n\n### Description\n\nWhen using a `UIButton` component with an `@click` event, the cursor does not change to `cursor-pointer`, which may confuse users about the button's clickability.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3240,3241,3244],{"name":3151,"color":3152},{"name":3242,"color":3243},"duplicate","cfd3d7",{"name":3154,"color":3155},2940,"`cursor-pointer` is missing on `UButton` with an `@click` event","2025-04-02T09:37:12Z","https://github.com/nuxt/ui/issues/2940",0.6784144,["Reactive",3251],{},["Set"],["ShallowReactive",3254],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$faYhKd9U9z6jlZRm4Ql15B7iIXp7kiVbLQj1Dwax443Y":-1},"/nuxt/ui/2398"]