\r\n\u003C/template>\r\n\u003Cscript setup>\r\nconst show = ref(false)\r\n\u003C/script>\r\n\u003Cscript setup>\r\nconst {error, data} = await useFetch('https://ord.uib.no/bm/fil/article100new.json')\r\n\u003C/script>\r\n```\r\n\r\n\r\n#### **`app.vue`**\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cbutton @click=\"show=!show\">toggle\u003C/button>\r\n \u003CPage v-if=\"show\"/>\r\n\u003C/template>\r\n\u003Cscript setup>\r\nconst show = ref(false)\r\n\u003C/script>\r\n```\r\n\r\nAfter the page has finished loading in the browser, disconnect from the internet, or select 'offline' in the browser devtools. Then click the button to render the Page-component. The error message will be \"\u003Cno response> Failed to fetch\", with status code 500.\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nWhen internet connection is lost, useFetch returns it as an internal server error when using an external API:\r\n{ \"cause\": \"TypeError: Failed to fetch\", \"message\": \"[GET] \\\"https://ord.uib.no/bm/fil/article100new.json\\\": \u003Cno response> Failed to fetch\", \"name\": \"Error\", \"statusCode\": 500 }\r\n\r\nIn the browser devtools I see an error code in fetch.js that makes more sense: net::ERR_INTERNET_DISCONNECTED, but I'm unable to capture this with useFetch.\r\n\r\n### Additional context\r\nThe error code is 500 even if SSR is disabled.\r\n\r\n### Logs\r\n\r\n_No response_",[2883,2886,2889,2892],{"name":2884,"color":2885},"enhancement","8DEF37",{"name":2887,"color":2888},"workaround available","11376d",{"name":2890,"color":2891},"upstream","E8A36D",{"name":2893,"color":2894},"馃嵃 p2-nice-to-have","0E8A16",24334,"Misleading error message in useFetch","2024-06-30T11:06:51Z","https://github.com/nuxt/nuxt/issues/24334",0.76947135,{"description":2901,"labels":2902,"number":2910,"owner":2874,"repository":2874,"state":2911,"title":2912,"updated_at":2913,"url":2914,"score":2915},"I think we should swallow errors stringifying fetch error states as any unhandled axios errors (for example) will completely break sites because we stringify error by default, yet these error objects contain circular references and the node `res` object.\n\n",[2903,2906,2907],{"name":2904,"color":2905},"stale","ffffff",{"name":2871,"color":2872},{"name":2908,"color":2909},"2.x","d4c5f9",8824,"closed","Fetch errors that can't be stringified aren't handled","2023-01-22T15:38:40Z","https://github.com/nuxt/nuxt/issues/8824",0.7478981,{"description":2917,"labels":2918,"number":2922,"owner":2874,"repository":2874,"state":2911,"title":2923,"updated_at":2924,"url":2925,"score":2926},"\u003C!-- 馃挌 Thanks for your time to make Nuxt better with your feedbacks 馃挌\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n馃憤 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: ^2.15.3\r\n\r\nhello i'm using fetch and i have an issue with status code here is my code when process is on the server : \r\n\r\n` this.$nuxt.context.redirect(302, {\r\n path:'my path',\r\n query: this.$route.query\r\n }) `\r\n\r\n### What is Expected?\r\nset status code to 302 when requesting with postman\r\n\r\n### What is actually happening?\r\nredirect work fine in the browser but status code dos not set as expected\r\n",[2919,2920,2921],{"name":2904,"color":2905},{"name":2871,"color":2872},{"name":2908,"color":2909},9259,"issue with redirect in fetch","2023-01-22T15:44:52Z","https://github.com/nuxt/nuxt/issues/9259",0.7525509,{"description":2928,"labels":2929,"number":2933,"owner":2874,"repository":2934,"state":2911,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.16.0`\r\n- Nuxt Version: `3.13.0`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `bun@1.1.2`\r\n- Builder: `-`\r\n- User Config: `srcDir`, `compatibilityDate`, `devtools`, `modules`\r\n- Runtime Modules: `@nuxt/ui@2.18.4`, `@nuxt/eslint@0.5.5`, `@pinia/nuxt@0.5.4`, `@nuxt/image@1.8.0`\r\n- Build Modules: `-`\r\n\n\n### Version\n\n2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-1fp2ap\r\n\r\nplease open Preview in new tab\n\n### Description\n\nI can't change position of UNotifications component because when I pass props it doesn't override tailwind class it just add my classes right to default classes.\r\n\r\nSolution which helped me: \r\nset class which you don't want to unset like this bottom-[unset]\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2930],{"name":2931,"color":2932},"bug","d73a4a",2128,"ui","UNotifications position","2024-10-10T10:16:14Z","https://github.com/nuxt/ui/issues/2128",0.7532839,{"description":2940,"labels":2941,"number":2946,"owner":2874,"repository":2874,"state":2911,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.17.0`\r\n- Nuxt Version: `3.11.2`\r\n- CLI Version: `3.11.1`\r\n- Nitro Version: `2.9.6`\r\n- Package Manager: `bun@1.1.4`\r\n- Builder: `-`\r\n- User Config: `devtools`, `alias`, `app`, `runtimeConfig`, `css`, `build`, `modules`, `experimental`, `features`, `vite`, `nitro`\r\n- Runtime Modules: `@pinia/nuxt@0.4.11`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\n-\r\n\r\n### Describe the bug\r\n\r\nI have a $fetch that checks inside an api route a recaptcha response:\r\n\r\n````\r\n const r = await $fetch\u003C{\r\n success: boolean\r\n hostname?: string\r\n 'error-codes'?: string[]\r\n }>('https://www.google.com/recaptcha/api/siteverify', {\r\n method: 'post',\r\n headers: {\r\n 'Content-Type': 'application/x-www-form-urlencoded'\r\n },\r\n body: new URLSearchParams({\r\n secret: captchaKey.re,\r\n response: val\r\n })\r\n });\r\n````\r\n\r\nFor some reason the build in my ssh server gets:\r\n\r\n```\r\nApi error: FetchError: [POST] \"https://www.google.com/recaptcha/api/siteverify\": \u003Cno response> fetch failed\r\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n at r (file:///var/www/server/index.mjs:1:59455)\r\n ... 5 lines matching cause stack trace ...\r\n at Object.handler (file:///var/www/server/index.mjs:1:51201)\r\n at Server.\u003Canonymous> (file:///var/www/server/index.mjs:1:54023) {\r\n [cause]: TypeError: fetch failed\r\n at Object.fetch (node:internal/deps/undici/undici:11730:11)\r\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n at $fetchRaw (file:///var/www/server/index.mjs:1:58493)\r\n at r (file:///var/www/server/index.mjs:1:59455)\r\n at Object.refinement (file:///var/www/server/utils/zod.ts:264:1)\r\n at file:///var/www/server/node_modules/zod-abort-failed/lib/index.mjs:1971:39\r\n at ZodObject.safeParseAsync (file:///var/www/server/node_modules/zod-abort-failed/lib/index.mjs:655:24)\r\n at ZodObject.password (file:///var/www/server/node_modules/zod-abort-failed/lib/index.mjs:628:24)\r\n at Object.handler (file:///var/www/server/api/auth/index.post.ts:17:1)\r\n at Object.handler (file:///var/www/server/index.mjs:1:51201) {\r\n cause: ConnectTimeoutError: Connect Timeout Error\r\n at onConnectTimeout (node:internal/deps/undici/undici:6869:28)\r\n at node:internal/deps/undici/undici:6825:50\r\n at Immediate._onImmediate (node:internal/deps/undici/undici:6857:13)\r\n at processImmediate (node:internal/timers:476:21) {\r\n code: 'UND_ERR_CONNECT_TIMEOUT'\r\n }\r\n }\r\n} undefined undefined\r\n```\r\nI did the same request with curl and has no problem so I guess is some package issue...\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_",[2942,2945],{"name":2943,"color":2944},"3.x","29bc7f",{"name":2871,"color":2872},26883,"TypeError: fetch failed","2025-05-18T10:25:50Z","https://github.com/nuxt/nuxt/issues/26883",0.7551419,{"labels":2952,"number":2956,"owner":2874,"repository":2874,"state":2911,"title":2957,"updated_at":2958,"url":2959,"score":2960},[2953,2954,2955],{"name":2904,"color":2905},{"name":2871,"color":2872},{"name":2908,"color":2909},8092,"Throwing error from new fetch does not redirect to custom error page","2023-01-22T15:36:08Z","https://github.com/nuxt/nuxt/issues/8092",0.7582837,{"description":2962,"labels":2963,"number":2965,"owner":2874,"repository":2934,"state":2911,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Environment\n\n\"nuxt\": \"^3.13.0\"\r\n\"@nuxt/ui\": \"^2.18.4\"\r\n\"vue\": \"latest\"\r\n\r\nnode js 20.9.0\r\n\r\nChip Apple M1 Pro\r\nMacOS Sonoma 14.2.1\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\n\r\n1. Run this Page\r\n```typescript\r\n\u003Ctemplate>\r\n \u003CUTable v-model=\"selected\" :rows=\"rows\" />\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\n definePageMeta({\r\n layout: '',\r\n })\r\n const rows = [{\r\n id: 1,\r\n name: 'John Doe',\r\n amount: 12.54,\r\n }, {\r\n id: 2,\r\n name: 'Jane Roe',\r\n amount: 45.12,\r\n }]\r\n const selected = ref([]);\r\n watch(selected, async (selections) => {\r\n const idMap = selections.map((item) => item.id);\r\n console.info('You checked', idMap)\r\n });\r\n\u003C/script>\r\n```\r\n\r\n2. Notice that when you check the check all box on the table that watch does not get called and nothing is printed to console\r\n\r\n\r\n\r\n\r\n\n\n### Description\n\nWhen you uncheck check all (false) watch updates correctly\r\nWhen you individually check boxes logic also works correctly\r\nIt is only when check all is checked (true) that the event does not propagate to watch correctly\r\n\r\nI also tried the @select function on the table as per example (https://ui.nuxt.com/components/table) and this function is even worse, it only executes some times\r\n\r\nI can see values being pushed here `/node_modules/@nuxt/ui/dist/runtime/components/data/Table.vue > selectAllRows()` but it does not propogate back to my app, maybe the push function does not work correctly on the array value?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2964],{"name":2931,"color":2932},2170,"UTable 'Select all' not updating ref events correctly","2024-09-18T08:42:41Z","https://github.com/nuxt/ui/issues/2170",0.76028234,{"description":2971,"labels":2972,"number":2976,"owner":2874,"repository":2874,"state":2911,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Versions\r\n\r\n- nuxt: 2.14.7\r\n- node: 12.16.1\r\n\r\n### Steps to reproduce\r\n\r\nBug is intermittent, I personally cannot reproduce on an emulated device.\r\n\r\n1. Site is built with `ssr: true` and `target: 'static'`\r\n2. `fetchKey` is not set\r\n3. `fetchOnServer: true`\r\n4. `fetch` is a function that returns a Promise\r\n\r\nOnly occurs on [this page](https://www.carbmanager.com) and only on Safari `14.0.1` or higher (seeing 87% of occurrences on `14.0.3`). Seeing on iOS 14.4 mostly.\r\n\r\n### What is Expected?\r\nThe error not to occur\r\n\r\n### What is actually happening?\r\nAn error is thrown during hydration\r\n\r\n```\r\nTypeError undefined is not an object (evaluating 'f.fetch[this._fetchKey]') \r\n https://www.carbmanager.com/_nuxt/f7c09ed.js:2:904036 d\r\n https://www.carbmanager.com/_nuxt/6413c5a.js:2:14962 Vt\r\n https://www.carbmanager.com/_nuxt/6413c5a.js:2:28812 Qe\r\n```",[2973,2974,2975],{"name":2904,"color":2905},{"name":2871,"color":2872},{"name":2908,"color":2909},9071,"TypeError undefined is not an object (evaluating 'f.fetch[this._fetchKey]') ","2023-01-22T15:38:48Z","https://github.com/nuxt/nuxt/issues/9071",0.7661635,{"description":2982,"labels":2983,"number":2988,"owner":2874,"repository":2934,"state":2911,"title":2989,"updated_at":2990,"url":2991,"score":2992},"### Environment\n\n- Operating System: `Windows 11`\n- Node Version: `v20.18.0`\n- Nuxt Version: `4 (nightly release), 4.0.0-28826831.b619b35e`\n- Nitro Version: `2.6.3`\n- CLI Version: 3.15.1-20241022-160139-45801c0\n- Nuxt Version: 4.0.0-28826831.b619b35e\n- Package Manager: `npm@10.8.0 or bun@1.1.33`\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.6\n- Build Modules: -\n\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nhttps://github.com/kashiarain/nuxt4-nuxtui3-repro\n\n### Description\n\nI am experiencing issues with NuxtUI3 alpha when using it alongside the nightly release of Nuxt 4. When I try to run the development server, I encounter persistent loading and error messages.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2984,2985],{"name":2931,"color":2932},{"name":2986,"color":2987},"v3","49DCB8",2436,"NuxtUI3 Alpha Not Working with Nuxt 4 Nightly Release","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/2436",0.76626927,["Reactive",2994],{},["Set"],["ShallowReactive",2997],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQlI45FYfZZFDMqtDbr2Tk3B3J3wEHtiGgcQu_Kp30bY":-1},"/nuxt/ui/2521"]