\r\n \u003Ctemplate #error=\"{ error }\">\r\n \u003Cp>An error occurred: {{ error }}\u003C/p>\r\n \u003Cbutton @click=\"() => clearError({ redirect: '/' })\">\r\n This will clear the error.\r\n \u003C/button>\r\n \u003C/template>\r\n \u003C/NuxtErrorBoundary>\r\n\u003C/template>\r\n```\r\n\r\n**Problem 1:**\r\n\r\nThe error is **NOT** cleared at all when the button is clicked. The error message still can be seen on the screen.\r\n\r\n**Problem 2:**\r\n\r\nThe Home page is **NOT** rendered at all when the route is redirected to `/` successfully. It is still rendering the error component and message.\r\n\r\nAny ideas? ",[3145,3148],{"name":3146,"color":3147},"bug","d73a4a",{"name":3149,"color":3150},"🔨 p3-minor","FBCA04",15781,"nuxt","open","Bug: Handling errors with the NuxtErrorBoundary component","2024-12-28T01:48:12Z","https://github.com/nuxt/nuxt/issues/15781",0.65551996,{"description":3159,"labels":3160,"number":3168,"owner":3152,"repository":3169,"state":3153,"title":3170,"updated_at":3171,"url":3172,"score":3173},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future, css\n- Runtime Modules: @nuxt/ui@3.1.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/gallant-margulis-h6zfnn?file=%2Fapp%2Fpages%2Findex.vue%3A11%2C9&workspaceId=ws_F4rkTtdti87aBypib7R95k\n\n### Description\n\nI'm migrating from v2 to v3 and noticed my global Nuxt error handler no longer works when using v3 components. In the reproduction when I'm calling `throw createError()` on a Nuxt UI button the event doesn't propagate to my `error-handler.js` plugin, however it does when I call the same click handler on a regular `\u003Cbutton>` tag.\nWhen inspecting the console I can see the click handler attached to the Nuxt UI button throws `Uncaught (in promise) H3Error` whereas with a normal button it's not a promise.\nThis used to work just fine with v2 as per this reproduction: https://stackblitz.com/edit/nuxt-ui-ofbazd6t?file=app.vue,plugins%2Ferror-handler.js\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3161,3162,3165],{"name":3146,"color":3147},{"name":3163,"color":3164},"v3","49DCB8",{"name":3166,"color":3167},"triage","ffffff",4237,"ui","throw createError handling in v3 components","2025-05-27T18:04:58Z","https://github.com/nuxt/ui/issues/4237",0.6720621,{"description":3175,"labels":3176,"number":3180,"owner":3152,"repository":3152,"state":3153,"title":3181,"updated_at":3182,"url":3183,"score":3184},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v21.3.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: pnpm@8.12.1\r\n- Builder: -\r\n- User Config: runtimeConfig, ssr, telemetry, imports, app, modules, content, devtools, pinia, piniaPersistedstate, pwa, vueuse, lodash, vuetify, vite, build, postcss, typescript, vue, experimental, nitro, router, routeRules\r\n- Runtime Modules: @nuxt/content@2.9.0, @nuxt/devtools@1.0.6, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @vite-pwa/nuxt@0.3.5, @vueuse/nuxt@10.7.0, nuxt-lodash@2.5.3, vuetify-nuxt-module@0.7.3\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nI will update this reproduction in a bit: https://stackblitz.com/edit/github-6maenb?file=app.vue,pages%2Fhello.vue,server%2Fapi%2Fhello.post.ts\r\n\r\n```vue\r\n\u003CNuxtErrorBoundary>\r\n \t\u003Ctemplate #error=\"{ error, clearError }\">\r\n\t\t\u003Cp>Data: {{ error.data }}\u003C/p>\r\n\t\u003C/template>\r\n \t\u003CNuxtPage />\r\n\u003C/NuxtErrorBoundary>\r\n```\r\n\r\n### Describe the bug\r\n\r\n- use `NuxtErrorBoundary` to handle global errors\r\n- use `$fetch` to access remote data or anything which throws (with `data` in response with status 400)\r\n- `data` prop will be missing from slot variables `error` i.e. `error.data` is null\r\n\r\n### Additional context\r\n\r\nmaybe related: https://github.com/nuxt/nuxt/issues/15390\r\n\r\n### Logs\r\n\r\n_No response_",[3177],{"name":3178,"color":3179},"pending triage","E99695",24774,"data property of error is lost when handling error in `NuxtErrorBoundary`","2024-06-30T11:06:34Z","https://github.com/nuxt/nuxt/issues/24774",0.67936003,{"description":3186,"labels":3187,"number":3193,"owner":3152,"repository":3169,"state":3194,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 4.0.3\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: pnpm@10.15.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv3.x\n\n### Version\n\nlatest\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/frosty-goodall-2wn4kw\n\n### Description\n\nIf we make a condition for the appearance of a slot and it is initially false, then we will never see it. This is because slots are not reactive.\n\nComponents that contain an error:\n\n- CheckboxGroup\n- DropdownMenu\n- DropdownMenuContent\n- ContextMenu\n- ChangelogVersions\n- ChatMessages\n- ChatPrompt\n- DashboardSearch\n- DashboardSearchButton\n- content/ContentSearch\n- content/ContentSearchButton\n\n### Solutions\n\nOne way to solve this is to not create a variable, but to immediately write `omit(slots, [‘...’])` in the template. This will fix the rendering error, but vue will still not show the number of available slots. ",[3188,3189,3190],{"name":3146,"color":3147},{"name":3163,"color":3164},{"name":3191,"color":3192},"p3-low","0E8A16",4947,"closed","No re-rendering in proxySlots","2025-09-14T06:40:03Z","https://github.com/nuxt/ui/issues/4947",0.6357647,{"description":3200,"labels":3201,"number":3206,"owner":3152,"repository":3152,"state":3194,"title":3207,"updated_at":3208,"url":3209,"score":3210},"### Describe the feature\n\nIf you use the current `\u003CNuxtErrorBoundary>` it will always render the `error`-slot on error, even if you do not provide a template to the slot. So if an error occurs inside the boundary, and no slot is provided, the component will just render a blank slot.\r\n\r\nWould it be smart to have an option to disable this, so that `\u003CNuxtErrorBoundary>` can be used to just catch the errors without doing any changes in the template? 😄 \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).",[3202,3205],{"name":3203,"color":3204},"3.x","29bc7f",{"name":3178,"color":3179},19140,"Possible to render default slot in `\u003CNuxtErrorBoundary>` on error","2023-04-14T21:38:24Z","https://github.com/nuxt/nuxt/issues/19140",0.64837766,{"description":3212,"labels":3213,"number":3219,"owner":3152,"repository":3169,"state":3194,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v23.10.0`\n- Nuxt Version: `3.17.0`\n- CLI Version: `3.25.0`\n- Nitro Version: `2.11.10`\n- Package Manager: `pnpm@10.10.0`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nAny use of tabs slots\n\n### Description\n\nAfter upgrading all dependencies to the latest version and keeping NuxtUI v3.0.2 everything is ok but when in addition to other dependencies I also upgrade NuxtUI to the latest version v3.1.0 then TS errors appear as in the attached screen shot so I guess again a step backwards from the recent fixes with slots ;p\n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3214,3215,3218],{"name":3146,"color":3147},{"name":3216,"color":3217},"duplicate","cfd3d7",{"name":3163,"color":3164},4005,"Tab slots types error","2025-04-28T10:54:47Z","https://github.com/nuxt/ui/issues/4005",0.6505759,{"description":3225,"labels":3226,"number":3228,"owner":3152,"repository":3152,"state":3194,"title":3229,"updated_at":3230,"url":3231,"score":3232},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.17.0`\n- Nuxt Version: `3.13.2`\n- CLI Version: `3.14.0`\n- Nitro Version: `2.9.7`\n- Package Manager: `npm@10.8.2`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n### Reproduction\n\nMake a layout with noticeable parts (such as header). Add this to `error.vue`:\n```\n\u003Cscript setup lang=\"ts\">\nimport { useHead } from '#app'\nimport type { NuxtError } from '#app'\n\nconst props = defineProps\u003C{\n error: NuxtError\n}>()\n\nuseHead({\n title: `Error ${props.error.statusCode || 'Unknown'}`\n})\n\nconst handleError = () => {\n clearError({ redirect: '/' })\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CNuxtLayout name=\"default\">\n \u003Cdiv class=\"error-container\">\n \u003Ch1>Error {{ props.error.statusCode || 'Unknown' }}\u003C/h1>\n \u003Cp>{{ props.error.message || 'An unexpected error occurred' }}\u003C/p>\n \u003Cbutton @click=\"handleError\">Go back to homepage\u003C/button>\n \u003C/div>\n \u003C/NuxtLayout>\n\u003C/template>\n```\nCause a 404 error to happen by going to a non-existent route.\n\nMy `layouts/default.vue` file:\n```\n\u003Ctemplate>\n \u003CNuxtLoadingIndicator color=\"#FFBC59\" />\n \u003CNavbar :language=\"language\" />\n \u003CNuxtPage :language=\"language\" />\n \u003CFooter :language=\"language\" />\n\u003C/template>\n// some other code\n```\n\nReproduction as a project: https://stackblitz.com/edit/github-nprqx2?file=layouts%2Fdefault.vue,error.vue,app.vue,pages%2Findex.vue,.gitignore\n\n### Describe the bug\n\nThe error message does not appear on the page unless I remove `\u003CNuxtLayout name=\"default\">` and `\u003C/NuxtLayout>` from error page. This is not what I want, I want error message inside the layout. I can achieve this by replacing `\u003CNuxtPage>` with `\u003Cslot>`, but that causes other problems (probably because props don't pass into the slot – should I make another bug report for that too?).\n\n### Additional context\n\nUsing a layout on an error page is supposed to work because documentation states:\n\n> you can still use layouts in the error file, by utilizing the [NuxtLayout](https://nuxt.com/docs/api/components/nuxt-layout) component and specifying the name of the layout\n\nBut I haven't found an example of that working. I am not 100% sure it's a bug, maybe I missed something.\n\n### Logs\n\n_No response_",[3227],{"name":3178,"color":3179},29284,"Using layout on error page causes error info to not appear","2024-10-05T18:46:02Z","https://github.com/nuxt/nuxt/issues/29284",0.6579562,{"description":3234,"labels":3235,"number":3240,"owner":3152,"repository":3169,"state":3194,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nI'm using the FormGroup component, and I've set the error to true, however unless it contains a non-empty text value the error slot won't render. Is this intentional or a bug? I would tend to think it's the latter.\n\n```\n\u003CUFormGroup :error=\"true\">\n \u003Ctemplate #error>\n \u003Cdiv>I will not render\u003C/div>\n \u003Ctemplate>\n\u003C/UFormGroup>\n```\n\n```\n\u003CUFormGroup :error=\"true && 'some error'\">\n \u003Ctemplate #error>\n \u003Cdiv>I will render\u003C/div>\n \u003Ctemplate>\n\u003C/UFormGroup>\n```",[3236,3237],{"name":3146,"color":3147},{"name":3238,"color":3239},"stale","ededed",2634,"FormGroup error with error slot","2025-06-14T15:36:58Z","https://github.com/nuxt/ui/issues/2634",0.6589771,{"description":3246,"labels":3247,"number":3250,"owner":3152,"repository":3152,"state":3194,"title":3251,"updated_at":3252,"url":3253,"score":3254},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.0\r\n- CLI Version: 3.9.1\r\n- Nitro Version: 2.7.0\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: ssr\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nHere is the reproduction example on [stackblitz](https://stackblitz.com/edit/github-wg3yu6-xyvmf5?file=pages%2Findex.vue)\n\n### Describe the bug\n\nWhen wrapping components in the **NuxtErrorBoundary** and one of the children throws an error (with createError but not fatal, or with a simple throw new Error() ) the error message is logged within the console but the error template does not take over the default slot.\r\n\r\nThis mostly when **ssr:false** is set in the config\r\n\r\n\u003Cimg width=\"367\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/48969740/ef169319-90ca-40c5-a899-0d41b78168ac\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3248,3249],{"name":3203,"color":3204},{"name":3178,"color":3179},23917,"NuxtErrorBoundary not rendering the error on ssr:false","2023-10-24T19:22:40Z","https://github.com/nuxt/nuxt/issues/23917",0.65974545,{"description":3256,"labels":3257,"number":3262,"owner":3152,"repository":3152,"state":3194,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.13.0`\r\n- Nuxt Version: `3.6.2`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `css`, `plugins`, `components`, `app`, `srcDir`, `build`, `devServer`, `modules`, `i18n`, `runtimeConfig`, `devtools`\r\n- Runtime Modules: `@nuxtjs/i18n@8.0.0-beta.13`, `nuxt-mapbox@1.3.9`, `@pinia/nuxt@0.4.11`, `@nuxt/content@2.7.0`, `@nuxtjs/robots@3.0.0`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nCreate a new Nuxt project. Create a vue.error in the root folder. Try throwing errors or go to a non existing url\n\n### Describe the bug\n\nIt seems that after the update that error.vue does not work anymore. I used this for an earlier project in the exact same way and that worked just fine. I did not use any specific setup but I just don't get the basic error page provided by the documentation to work. [](https://nuxt.com/docs/getting-started/error-handling#rendering-an-error-page)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3258,3259,3260],{"name":3203,"color":3204},{"name":3178,"color":3179},{"name":3261,"color":3150},"needs reproduction",22065,"Error.vue page not working","2024-03-18T17:10:36Z","https://github.com/nuxt/nuxt/issues/22065",0.65986747,["Reactive",3268],{},["Set"],["ShallowReactive",3271],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fhZ690E1dyxRTY-AGLwtSIZm_mjCRbfOikefOajPLYy0":-1},"/nuxt/ui/4486"]