\n \u003C/UTooltip>\n \u003CUTooltip text=\"Delete\">\n \u003CUButton color=\"neutral\" variant=\"ghost\" size=\"xs\" icon=\"i-lucide-trash-2\" />\n \u003C/UTooltip>\n \u003CUDropdownMenu size=\"sm\" :items=\"exportItems\">\n \u003CUTooltip text=\"Export as...\">\n \u003CUButton color=\"neutral\" variant=\"ghost\" size=\"xs\" icon=\"i-lucide-file-down\" />\n \u003C/UTooltip>\n \u003C/UDropdownMenu>\n\u003C/template>\n\u003Cscript setup>\n const exportItems = [\n [\n {\n label: 'Export as...',\n type: 'label'\n },\n ],\n [\n {\n label: 'Markdown',\n onSelect () {\n \n }\n },\n {\n label: 'Plain Text',\n onSelect () {\n \n }\n },\n ]\n]\n\u003C/script>\n```\nin this case, UDropdownMenu can not work, if remove UTooltip element, it works.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2035,2038],{"name":2036,"color":2037},"bug","d73a4a",{"name":1988,"color":1989},3339,"closed","DropdownMenu cannot be nested with Tooltip components","2025-02-19T15:23:15Z","https://github.com/nuxt/ui/issues/3339",0.6919234,{"description":2046,"labels":2047,"number":2049,"owner":1991,"repository":1992,"state":2040,"title":2050,"updated_at":2051,"url":2052,"score":2053},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.8.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.17.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.38\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Version\n\n^2.19.2\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-umrnyur4?file=app.vue\n\n### Description\n\nI am using Zod for the \u003CUForm /> validation. In the minimal reproduction, since I provided two paths for the error, the message should appear on both fields. However, the error message only shows if only 1 path is specified.\n\n### Additional context\n\n### Logs\n\n```shell-script\n\n```",[2048],{"name":2036,"color":2037},2981,"`UForm` does not show error for multiple paths","2025-01-09T14:53:06Z","https://github.com/nuxt/ui/issues/2981",0.72501093,{"description":2055,"labels":2056,"number":2059,"owner":1991,"repository":2060,"state":2040,"title":2061,"updated_at":2062,"url":2063,"score":2064},"Resolves #385 \r\nFixes #412 ",[2057],{"name":2036,"color":2058},"ff281a",412,"nuxt.com","When changing color mode, editor slots are broken","2023-06-06T12:14:51Z","https://github.com/nuxt/nuxt.com/issues/412",0.7295982,{"description":2066,"labels":2067,"number":2059,"owner":1991,"repository":2069,"state":2040,"title":2070,"updated_at":2071,"url":2072,"score":2064},"### Environment\n\n```\n------------------------------\n- Operating System: Darwin\n- Node Version: v23.9.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.5\n- Package Manager: bun@1.2.4\n- Builder: -\n- User Config: compatibilityDate, css, app, modules, htmlValidator, nitro, postcss, image, prismic, runtimeConfig, site, turnstile, vite\n- Runtime Modules: @nuxt/image@1.9.0, @nuxt/ui@3.0.0-beta.3, @nuxtjs/device@3.2.4, @nuxtjs/html-validator@2.1.0, @nuxtjs/prismic@4.1.0, @nuxtjs/robots@5.2.6, @nuxtjs/turnstile@0.9.12, nitro-cloudflare-dev@0.2.2, nuxt-link-checker@4.1.1, nuxt-seo-experiments@4.0.1\n- Build Modules: -\n------------------------------\n```\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/wizardly-hertz-gyk77v\n\n### Describe the bug\n\nSince the `3.16.0` release, my project doesn't build anymore. I isolated the issue to a component using `Turnstile` which seems to depend on `@nuxt/scripts` which is mentioned in the error logs.\n\nThe reproduction is very small, just a Turnstile component without configuration.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nERROR ✗ Build failed in 1.79s 5:04:16 PM\n\n\n[ nuxi 5:04:16 PM] ERROR Nuxt Build Error: [vite]: Rollup failed to resolve import \"unenv/runtime/mock/noop\" from \"/project/workspace/node_modules/@nuxt/scripts/dist/runtime/validation/mock.js\".\nThis is most likely unintended because it can break your application at runtime.\nIf you do want to externalize this module explicitly add it to\nbuild.rollupOptions.external\n\n This is most likely unintended because it can break your application at runtime.\n If you do want to externalize this module explicitly add it to\n build.rollupOptions.external\n at viteLog (node_modules/vite/dist/node/chunks/dep-glQox-ep.js:51589:15)\n at onRollupLog (node_modules/vite/dist/node/chunks/dep-glQox-ep.js:51639:5)\n at onLog (node_modules/vite/dist/node/chunks/dep-glQox-ep.js:51287:7)\n at node_modules/rollup/dist/es/shared/node-entry.js:20487:32\n at Object.logger [as onLog] (node_modules/rollup/dist/es/shared/node-entry.js:22230:9)\n at ModuleLoader.handleInvalidResolvedId (node_modules/rollup/dist/es/shared/node-entry.js:21113:26)\n at node_modules/rollup/dist/es/shared/node-entry.js:21071:26\n\nerror Command failed with exit code 1.\n```",[2068],{"name":2036,"color":2037},"scripts","Build fails since 3.16.0 due to failed import","2025-03-14T18:00:08Z","https://github.com/nuxt/scripts/issues/412",{"description":2074,"labels":2075,"number":2079,"owner":1991,"repository":1991,"state":2040,"title":2080,"updated_at":2081,"url":2082,"score":2083},"### Describe the feature\n\nIn https://nuxt.com/docs/api/composables/use-fetch#usefetch, there are some types statically written in markdown, which are outdated (if you compare them to the types in nuxt 3.3.1). e.g. the `header` property accepts different values now.\r\n\r\nI could add a PR to fix these static types, or maybe it would be better to not include them into the docs hand-written, and refer to the file in the git? Or maybe it's possible to include the file dynamically from git?\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2076,2078],{"name":1985,"color":2077},"8DEF37",{"name":2002,"color":2003},18637,"sync types from code base into docs","2024-08-01T07:15:47Z","https://github.com/nuxt/nuxt/issues/18637",0.73148936,{"description":2085,"labels":2086,"number":2093,"owner":1991,"repository":1991,"state":2040,"title":2094,"updated_at":2095,"url":2096,"score":2097},"Should we publish index.d.ts to `@types` so others can include it in their package.json dev dependencies ? \r\n\r\nhttps://github.com/nuxt/nuxt.js/blob/dev/examples/typescript/index.d.ts\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c680\">#c680\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2087,2090],{"name":2088,"color":2089},"question","cc317c",{"name":2091,"color":2092},"2.x","d4c5f9",795,"TS : Should we publish Types ? ","2023-01-18T15:39:48Z","https://github.com/nuxt/nuxt/issues/795",0.7328884,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"nVfW_O430FAdItuWiQDDBF1IdMiO8WOJ645Tg_wzwlE":-1},"/nuxt/ui/3655"]