\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_",[3048,3051,3054,3057],{"name":3049,"color":3050},"workaround available","11376d",{"name":3052,"color":3053},"bug","d73a4a",{"name":3055,"color":3056},"🔨 p3-minor","FBCA04",{"name":3058,"color":3059},"✨ good reproduction","fbca04",22691,"nuxtApp.vueApp.config.errorHandler doesn't work","2024-11-19T16:20:54Z","https://github.com/nuxt/nuxt/issues/22691",0.6609782,{"description":3066,"labels":3067,"number":3069,"owner":3022,"repository":3022,"state":3070,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v22.8.0\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.14.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.3.0\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nTo reproduce the bug, set up a minimal environment with a NuxtLink that points to a page containing:\r\n`throw createError({ statusCode: 404 });`\r\n\r\nWhen you navigate to this page, no 404 error appears, and in the console, you'll find the following error:\r\n`index.mjs?v=6f706544:78 Uncaught (in promise) H3Error`\r\n\r\nHowever, if you refresh the 404 page, it is displayed correctly. This suggests that the issue occurs only on the client side.\r\n\r\nHere a reproduction (click the link ERROR TRIGGER and check the console):\r\nhttps://stackblitz.com/edit/github-cwjr13?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nOn the client side, if I throw an error, I'm not redirected to the 404 page.\r\nHowever, it works correctly on the server side.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nindex.mjs?v=ae07b3d2:78 Uncaught (in promise) H3Error\r\n at createError (index.mjs?v=ae07b3d2:78:15)\r\n at createError (error.js?v=ae07b3d2:33:21)\r\n at setup (about.vue:6:7)\r\n at callWithErrorHandling (runtime-core.esm-bundler.js?v=ae07b3d2:197:19)\r\n at setupStatefulComponent (runtime-core.esm-bundler.js?v=ae07b3d2:7864:25)\r\n at setupComponent (runtime-core.esm-bundler.js?v=ae07b3d2:7825:36)\r\n at mountComponent (runtime-core.esm-bundler.js?v=ae07b3d2:5186:7)\r\n at processComponent (runtime-core.esm-bundler.js?v=ae07b3d2:5152:9)\r\n at patch (runtime-core.esm-bundler.js?v=ae07b3d2:4668:11)\r\n```\r\n```\r\n",[3068],{"name":3019,"color":3020},29228,"closed","Uncaught (in promise) H3Error when I `throw createError({ statusCode: 404 })`","2024-09-30T11:28:48Z","https://github.com/nuxt/nuxt/issues/29228",0.60900533,{"description":3076,"labels":3077,"number":3079,"owner":3022,"repository":3022,"state":3070,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Environment\n\nFollowing stackblitz repro env:\n\nWorking directory: /home/projects/nbwiyxyjmw.github nuxi 13:18:40\nNuxt project info: nuxi 13:18:40\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.2\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-hge4algc?file=pages%2Findex.vue,pages%2Fpage2.vue\n\n1. click `Here's the CSR problem...` link, errors in console, nothing happens \n2. hit `refresh` button in stackblitz preview - proper error page is displayed \n\n### Describe the bug\n\nAs written in the Error handling - `throw CreateError` is a recommended way to stop displaying current page due to problems and show error page instead, source: https://nuxt.com/docs/getting-started/error-handling#createerror\n\nIn SSR mode it works correctly - user is shown with `error.vue` page which can display the details of the erorr\n\nDuring CSR mode the app crushes with Vue warning:\n`[Vue warn]: Unhandled error during execution of setup function ` \nand H3 error\n`Uncaught (in promise) H3Error`\n\n### Additional context\n\nExpected behaviour would be to have the same result on the CSR as is on SSR - an error page with passed details from the `createError` util\n\n### Logs\n\n```shell-script\n\n```",[3078],{"name":3019,"color":3020},30706,"`createError` is crashing app on CSR navigation","2025-01-22T19:57:40Z","https://github.com/nuxt/nuxt/issues/30706",0.6249437,{"description":3085,"labels":3086,"number":3096,"owner":3022,"repository":3097,"state":3070,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.12.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.2\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.0.0-alpha.12\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/bug-report-ubutton-8st7kw\n\n### Description\n\nWhen I throw an error within the click event of `UButton`, the `NuxtErrorBoundary` component does not catch the error as expected. However, if I use a standard `\u003Cbutton>` tag instead of `UButton`, the error is caught correctly by the NuxtErrorBoundary.\n\n### Additional context\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[3087,3088,3091,3094],{"name":3052,"color":3053},{"name":3089,"color":3090},"v3","49DCB8",{"name":3092,"color":3093},"closed-by-bot","ededed",{"name":3095,"color":3093},"stale",3237,"ui","[UButton] is not working with NuxtErrorBoundary","2025-06-18T09:02:19Z","https://github.com/nuxt/ui/issues/3237",0.62977976,{"description":3103,"labels":3104,"number":3109,"owner":3022,"repository":3022,"state":3070,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### 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_",[3105,3108],{"name":3106,"color":3107},"3.x","29bc7f",{"name":3019,"color":3020},22109,"error hook not catching errors?","2024-01-26T10:52:58Z","https://github.com/nuxt/nuxt/issues/22109",0.630064,{"description":3115,"labels":3116,"number":3123,"owner":3022,"repository":3022,"state":3070,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Environment\r\n\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `yarn@1.22.10`\r\n- Builder: `vite`\r\n- User Config: `build`, `modules`, `loadingIndicator`, `app`, `css`\r\n- Runtime Modules: `nuxt-windicss@2.5.2`, `@pinia/nuxt@0.4.3`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nWhen I enter a page directly via the browser e.g: 192.168.1.1/test (it shows me an 404 page error, which is fine). But when I navigate to an existing page (which loads normally) and then click on a button with a internal link like: 192.168.1.1/hello it provides an error. It is unable to create an error.\r\n\r\nhttps://stackblitz.com/edit/github-dk8jtl?file=app.vue\r\n\r\nClick on the two buttons named \"Team\" and \"Contact\". Everything working fine. Click then on \"Error\" button. Please check console for the error message which I provided.\r\n\r\n### Describe the bug\r\n\r\nUncaught (in promise) Error: Page Not Found\r\n at createError (index.mjs?v=f2c40dfc:35:15)\r\n\r\n`const err = new H3Error(input.message ?? input.statusMessage, input.cause ? { cause: input.cause } : void 0);`\r\n\r\n### Additional context\r\n\r\nI generate the error with the following line; `throw createError({ statusCode: 404, statusMessage: 'Page Not Found' })`\r\n\r\n### Logs\r\n\r\n_No response_",[3117,3118,3119,3122],{"name":3106,"color":3107},{"name":3052,"color":3053},{"name":3120,"color":3121},"pages","00DFB5",{"name":3055,"color":3056},15432,"`throw createError` does not show error page on client-side (in development)","2025-02-19T12:24:50Z","https://github.com/nuxt/nuxt/issues/15432",0.6447547,{"description":3129,"labels":3130,"number":3135,"owner":3022,"repository":3022,"state":3070,"title":3136,"updated_at":3137,"url":3138,"score":3139},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.14.0\r\n- Nuxt Version: 3.5.3\r\n- Nitro Version: 2.4.1\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite 11:49:48 AM\r\n- User Config: css, app, build, runtimeConfig, vue, ssr, nitro, routeRules, vite, experimental, devtools\n\n### Reproduction\n\nJust throwing an error with createError in a client plugin\n\n### Describe the bug\n\nTrying to throw a non fatal error I can access in the app with useError(), but it always renders the error.vue component.\r\n\r\n`throw createError({message: 'non fatal error'})`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3131,3132,3133],{"name":3106,"color":3107},{"name":3019,"color":3020},{"name":3134,"color":3056},"needs reproduction",21725,"createError() always shows full-screen error.vue even without fatal: true","2023-07-12T15:08:43Z","https://github.com/nuxt/nuxt/issues/21725",0.64633507,{"labels":3141,"number":3146,"owner":3022,"repository":3022,"state":3070,"title":3147,"updated_at":3148,"url":3149,"score":3150},[3142,3143],{"name":3019,"color":3020},{"name":3144,"color":3145},"2.x","d4c5f9",6869,"Error page does not work in production mode","2023-01-22T15:34:48Z","https://github.com/nuxt/nuxt/issues/6869",0.6491881,["Reactive",3152],{},["Set"],["ShallowReactive",3155],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$foLuo_hLZFg5syy4YfDYNfuU00jHCC5kBJmKNTKqTf_w":-1},"/nuxt/ui/4237"]