\r\n \u003C/UFormGroup>\r\n \u003C/UForm>\r\n\u003C/template>\r\n```\r\n\r\n\u003Cimg width=\"1239\" alt=\"chrome\" src=\"https://github.com/user-attachments/assets/750c2b77-79a2-4aa1-b29c-1fd36db0cfa0\">\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2031],{"name":1998,"color":1999},2126,"Chrome: Label 'for' attribute mismatch with form field IDs in URadioGroup","2024-09-06T16:59:18Z","https://github.com/nuxt/ui/issues/2126",0.71941715,{"description":2038,"labels":2039,"number":2046,"owner":1988,"repository":1988,"state":2023,"title":2047,"updated_at":2048,"url":2049,"score":2050},"If any error occurs inside component's `data()` an ugly and unhanded SSR error occurs like this:\r\n\r\nTypeError: Converting circular structure to JSON\r\n\r\n\r\nAlso trying to handle errors in every single page seems so extra work and not possible always consider my dashboard's data :\r\n```js\r\nasync data({redirect, error}){\r\n try {\r\n let {stats} = await $http.get('admin/dashboard');\r\n return { stats: stats }\r\n } catch {\r\n error({message:'Something bad happened!'}); \r\n return {stats: {} }\r\n }\r\n },\r\n``` \r\n\r\n**Suggestion:** Why we don't simply catch all returned promises in data and passing proper error object to user land?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c112\">#c112\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2040,2043],{"name":2041,"color":2042},"enhancement","8DEF37",{"name":2044,"color":2045},"2.x","d4c5f9",134,"[Enhancement] Handle data() promise errors","2023-01-18T15:38:30Z","https://github.com/nuxt/nuxt/issues/134",0.73353606,{"description":2052,"labels":2053,"number":2056,"owner":1988,"repository":2057,"state":2023,"title":2058,"updated_at":2059,"url":2060,"score":2061},"",[2054],{"name":2041,"color":2055},"1ad6ff",675,"nuxt.com","[Docs] Improve prose design","2022-07-07T12:30:55Z","https://github.com/nuxt/nuxt.com/issues/675",0.7382623,{"description":2063,"labels":2064,"number":2065,"owner":1988,"repository":2057,"state":2023,"title":2066,"updated_at":2067,"url":2068,"score":2069},"The docs do not have styles for h5 headers, you can see it in posts with a lot of sections and sub-sections, like the [v4 Migration guide](https://nuxt.com/docs/getting-started/upgrade#testing-nuxt-4).\r\n\r\nI suggest at least making those titles bold so they stand out a bit more.",[],1596,"Missing styles for h5","2024-06-17T14:49:04Z","https://github.com/nuxt/nuxt.com/issues/1596",0.7389839,{"description":2071,"labels":2072,"number":2074,"owner":1988,"repository":1988,"state":2023,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Environment\n\nStackblitz Sandbox\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-7wcdxads?file=app.vue,components%2FErrorContent.vue\n\n### Describe the bug\n\nI want to intercept errors within the component as much as possible, so that they only affect the current component and do not cause the entire page to crash. However, I tried the following three methods (all based on onErrorCaptured), and they work fine when useFetch is not used on the page. But once useFetch is used, the page directly returns a 500 status code, and I am unable to intercept the relevant errors to prevent the page from crashing.\n\nhttps://cn.vuejs.org/api/composition-api-lifecycle#onerrorcaptured\nhttps://nuxt.com/docs/getting-started/error-handling#vue-errors\nhttps://nuxt.com/docs/api/components/nuxt-error-boundary\n\nI hope there is a way to intercept errors within the component when using useFetch, so that it doesn't cause the entire page to display a 500 error, thanks.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2073],{"name":1985,"color":1986},30917,"fetchData causes onErrorCaptured to be unable to capture errors","2025-02-22T20:46:13Z","https://github.com/nuxt/nuxt/issues/30917",0.7394791,{"description":2080,"labels":2081,"number":2085,"owner":1988,"repository":2057,"state":2023,"title":2086,"updated_at":2087,"url":2088,"score":2089},"All information on this form : https://docs.google.com/forms/d/1wj_8SJSKsBbAl2LHP_FXN1hmX2F9q0exgnMgnqItOew/edit#response=ACYDBNj8ub8yiV2ml4eURll0EIlnVxRXYg_nwSfTVm6OTB6vu5kUz1faMLBhj56dEuVe3cQ",[2082],{"name":2083,"color":2084},"marketing","f5c828",1028,"[Partner] Build BrainPlatform partner page","2023-06-06T12:14:26Z","https://github.com/nuxt/nuxt.com/issues/1028",0.7506585,{"labels":2091,"number":2096,"owner":1988,"repository":1988,"state":2023,"title":2097,"updated_at":2098,"url":2099,"score":2100},[2092,2095],{"name":2093,"color":2094},"3.x","29bc7f",{"name":1985,"color":1986},13930,"Unhandled error when navigating to a route that doesn't exist","2023-01-19T17:09:58Z","https://github.com/nuxt/nuxt/issues/13930",0.75808597,["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"Ych03RNodoT10MXV14jNwVOb1g2Gpy2cm2YeyPIoPFI":-1},"/nuxt/nuxt.com/566"]