\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\nlet event2 = null\r\nevent2.dummy\r\n\u003C/script>\r\n```\r\n\r\nI get the following error.\r\n`Cannot read properties of null (reading 'dummy')`\r\n\r\nconsole works with v3.3.2 but not after v3.3.3.\r\nWhen testing, Vue version is fixed to v3.3.4.\r\n\r\n### Additional context\r\n\r\n\r\n\r\nsimilar issue #20347\r\n\r\n### Logs\r\n\r\n_No response_",[3173,3176,3177,3180],{"name":3174,"color":3175},"workaround available","11376d",{"name":3156,"color":3157},{"name":3178,"color":3179},"🔨 p3-minor","FBCA04",{"name":3181,"color":3182},"✨ good reproduction","fbca04",22691,"nuxtApp.vueApp.config.errorHandler doesn't work","2024-11-19T16:20:54Z","https://github.com/nuxt/nuxt/issues/22691",0.70548993,{"description":3189,"labels":3190,"number":3194,"owner":3146,"repository":3165,"state":3147,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.5.0\n- Nuxt Version: 3.17.6\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: devtools, typescript, modules, css, future, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.2.0, @nuxt/eslint@1.5.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://github.com/harkor/nuxt-ui-form-errors-reproduction\n\n[stackblitz](https://stackblitz.com/github/harkor/nuxt-ui-form-errors-reproduction)\n\n### Description\n\nIf I write this\n\n```ts\nformRef.value?.setErrors([\n {\n name: \"pathForACustomError\",\n message: \"This is a custom error message.\",\n },\n ]);\n```\n\nThe error will be set in formRef?.getErrors('pathForACustomError')\n\nBut if I watch a state like this and clear the error\n\n```ts\nwatch(\n () => state.hello,\n () => {\n console.log(\"Hello changed:\", state.hello);\n formRef.value?.clear(\"pathForACustomError\");\n },\n);\n```\n\nIf the UFormField component have a name (the component change the value), formRef?.getErrors('pathForACustomError') will not be cleared, it will for 1 or two tick but after that, the error is still there.\n\nIn my reproduction you have 3 URadioGroup\n\nHello, World and Hi\n\nIf you change\n- \"Hello\", error not cleared\n- \"World\", error cleared\n- \"Hi\", error cleared\n\nWhat change between these 3 fields\n- \"Hello\" have a name attribute in the UFormField\n- \"World\" don't have a name attribute in the UFormField\n- \"Hi\" have a name in attribute BUT with a @change will clear \"again\" the error\n\n**PS: Don't forget to click on \"Set custom error\" button before change values on URadioGroup's components**\n\nBonus: Since version 3.2.0, I have a typescript error for getErrors(path) with typecheck enabled\n\n**Expectations**\n- First UFormField \"hello\" clear the error when state change with a watch\n- No typescript error on getErrors\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nERROR 11:39:08 AM\n ERROR(vue-tsc) Argument of type '\"pathForACustomError\"' is not assignable to parameter of type 'undefined'.\n FILE /home/projects/xoriallzvx.github/app/components/MyForm.vue:127:36\n\n 125 | \u003C/UFormField>\n 126 | \u003Cdiv\n > 127 | v-if=\"!!formRef?.getErrors('pathForACustomError').length\"\n | ^^^^^^^^^^^^^^^^^^^^^\n 128 | class=\"text-red-400\"\n 129 | >\n 130 | {{ formRef?.getErrors(\"pathForACustomError\")[0]?.message }}\n\n ERROR(vue-tsc) Argument of type '\"pathForACustomError\"' is not assignable to parameter of type 'undefined'.\n FILE /home/projects/xoriallzvx.github/app/components/MyForm.vue:130:29\n\n 128 | class=\"text-red-400\"\n 129 | >\n > 130 | {{ formRef?.getErrors(\"pathForACustomError\")[0]?.message }}\n | ^^^^^^^^^^^^^^^^^^^^^\n 131 | \u003C/div>\n 132 | \u003C/UForm>\n 133 | \u003C/template>\n\n[vue-tsc] Found 2 errors. Watching for file changes.\n```",[3191,3192,3193],{"name":3156,"color":3157},{"name":3159,"color":3160},{"name":3162,"color":3163},4455,"SetErrors with a ref and clear this error from a watcher don't work + TS Error","2025-07-03T09:49:23Z","https://github.com/nuxt/ui/issues/4455",0.706775,{"description":3200,"labels":3201,"number":3205,"owner":3146,"repository":3165,"state":3206,"title":3207,"updated_at":3208,"url":3209,"score":3210},"### Description\n\nBased on https://ui.nuxt.com/components/form#error-event there is a way to attach things \"on form error\", like scroll the an element into view.\n\nThis does not help on back-end logic escalating a validation error or something some other logic coming from an external source.\n\nI tried\n\n- throwing an exception within submit, did not trigger the error handler\n- add errors through form refs `setErrors()`, then follow up with a `validate()` but that did nothing as well.\n\nIt would be nice to have a way to trigger the `@error` handler within the `@submit` handler, something in the spirit of:\n\n```js\nasync function onSubmit(event: FormSubmitEvent\u003C...>) {\n try { await api.doLogin() }\n catch (e) { event.fail() }\n}\n```\n\nNot sure this would be a good pattern though. Maybe if an exception is thrown within the submit handler, it could trigger the error handler as well?\n\n### Additional context\n\n_No response_",[3202,3204],{"name":3140,"color":3203},"a2eeef",{"name":3159,"color":3160},4124,"closed","UForm: Retrigger error handler on backend errors","2025-07-11T11:01:02Z","https://github.com/nuxt/ui/issues/4124",0.6535166,{"description":3212,"labels":3213,"number":3220,"owner":3146,"repository":3146,"state":3206,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.15.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: typescript, app, modules, nitro, runtimeConfig, css, vue, build, imports, pinia, piniaPersistedstate, i18n, devtools\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @pinia-plugin-persistedstate/nuxt@1.1.1, @nuxtjs/i18n@8.0.0-beta.13, @unocss/nuxt@0.53.5, @vueuse/nuxt@10.2.1, @nuxtjs/device@3.1.0, @nuxt/content@2.7.0\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\n```\r\n// plugins/hook.ts\r\n// code from doc's example\r\nexport default defineNuxtPlugin((nuxtApp) => {\r\n nuxtApp.hook('vue:error', (..._args) => {\r\n console.log('vue:error')\r\n // if (process.client) {\r\n // console.log(..._args)\r\n // }\r\n })\r\n nuxtApp.hook('app:error', (..._args) => {\r\n console.log('app:error')\r\n // if (process.client) {\r\n // console.log(..._args)\r\n // }\r\n })\r\n nuxtApp.vueApp.config.errorHandler = (..._args) => {\r\n console.log('global error handler')\r\n // if (process.client) {\r\n // console.log(..._args)\r\n // }\r\n }\r\n})\r\n```\r\n\r\n```\r\n// server/api/someapi/index.get.ts\r\nexport default defineEventHandler(async (event) => {\r\n const data = getSomeData()\r\n if (!data)\r\n throw createError({statusCode: 404, statusMessage: 'errors.404_notfound'})\r\n})\r\n```\r\n\r\n```\r\nerror message from console:\r\nUncaught (in promise) Error: errors.404_notfound\r\n```\r\n\r\n```\r\n// layout/alert.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n $t('some error messages')\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n### Describe the bug\r\n\r\nI want to popup error message when error occurs,\r\nand was hoping nuxt hook would catch all the errors created by createError(),\r\nso I can place popup alert function inside nuxt hook,\r\nbut it doesn't catch anything.\r\n\r\nI have alert function ready for successful / failed api result,\r\njust don't know how I can globally catch errors and handle them.\r\n\r\nI don't want to render a full page of error and let user go back by using clearError,\r\nI just want to simply catch it and show them what's wrong\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3214,3217],{"name":3215,"color":3216},"3.x","29bc7f",{"name":3218,"color":3219},"pending triage","E99695",22109,"error hook not catching errors?","2024-01-26T10:52:58Z","https://github.com/nuxt/nuxt/issues/22109",0.6670554,{"description":3226,"labels":3227,"number":3232,"owner":3146,"repository":3146,"state":3206,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Environment\r\n\r\n```\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.18.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `imports`, `typescript`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\n1. Create a module\r\n2. write this code:\r\n ```ts\r\n import { defineNuxtModule } from \"@nuxt/kit\"\r\n \r\n export default defineNuxtModule\u003C{}>({\r\n meta: {\r\n name: \"my-module\",\r\n configKey: \"myModule\",\r\n },\r\n defaults: {},\r\n setup(options: {}, nuxt: Nuxt) {\r\n nuxt.hooks.hook(\"vue:error\", (...args: Parameters\u003CParameters\u003Ctypeof onErrorCaptured>[0]>) => {\r\n console.log(\"vue got an error\")\r\n })\r\n \r\n nuxt.hooks.hook(\"app:error\", () => {\r\n console.log(\"app got an error\")\r\n }\r\n },\r\n })\r\n ```\r\n\r\n### Describe the bug\r\n\r\nIn the [Error handling guide](https://nuxt.com/docs/getting-started/error-handling), both hooks `vue:error` and `app:error` are refered to. However, none of them are found anywhere. How am I supposed to use them if they just don't exist?\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3228,3231],{"name":3229,"color":3230},"documentation","5319e7",{"name":3215,"color":3216},15733,"Some hooks listed in the documentation aren't in NuxtHooks interface","2023-01-19T18:20:25Z","https://github.com/nuxt/nuxt/issues/15733",0.66772455,{"description":3238,"labels":3239,"number":3241,"owner":3146,"repository":3146,"state":3206,"title":3242,"updated_at":3243,"url":3244,"score":3245},"### What problem does this feature solve?\n\nThe new fetch-hook uses a global try/catch in the nuxt core, and exposes the error only as a property inside `$fetchState.error`. Upstream, the error is now also emitted to the console on dev enviroments by default.\n\nFor production environments, currently the `$fetchState.error` can easily be used to handle errors in per component by checking for `$fetchState.error` in the component. However, there is no API available to have any sort of generic error reporting for any fetch-hook in the app.\n\nHowever, for integrating with error-reporting tools like Bugsnag or Sentry, I'd want to be able to easily report any exceptions from *any* fetch-hook inside the App.\n\nIt would be great if there was a hook here we could use to add a specific implementation for Bugsnag, Sentry or another tool to any $fetch hook used in the app, while retaining the graceful error handling that's there now.\n\n### What does the proposed changes look like?\n\nI don't really know how to implement hooks in the nuxt source, but I'd imagine the consumer API could look like this:\n\n```\nimport Bugsnag from 'bugsnag';\nthis.nuxt.hook('app:onFetchError', (app, err) => Bugsnag.notifyException(err));\n```\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c10773\">#c10773\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3240],{"name":3218,"color":3219},7517,"Allow hooking into $fetch (specifically for generic error reporting)","2025-06-05T13:37:21Z","https://github.com/nuxt/nuxt/issues/7517",0.6734551,{"labels":3247,"number":3252,"owner":3146,"repository":3146,"state":3206,"title":3253,"updated_at":3254,"url":3255,"score":3256},[3248,3249],{"name":3140,"color":3141},{"name":3250,"color":3251},"2.x","d4c5f9",9031,"How can one log and catch all uncaught Nuxt errors?","2023-01-22T15:52:51Z","https://github.com/nuxt/nuxt/issues/9031",0.6899618,{"labels":3258,"number":3261,"owner":3146,"repository":3146,"state":3206,"title":3262,"updated_at":3263,"url":3264,"score":3265},[3259,3260],{"name":3140,"color":3141},{"name":3250,"color":3251},7416,"Custom html/template rendering on nuxt server error","2023-01-22T16:54:05Z","https://github.com/nuxt/nuxt/issues/7416",0.69378823,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fD1sq7e_rN-h-tCJcvmPScBxu13HogRysAGW-uuPbR2E":-1},"/nuxt/ui/4626"]