\n\n\u003Cimg width=\"942\" height=\"183\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2da0790d-e85e-406e-9f27-ee10cfa7efee\" />\n\nI would just ignore them, but sometimes they crash the Nuxt entirely, triggering full restart (not just server but whole Nuxt):\n\nhttps://github.com/user-attachments/assets/b581504f-842a-46d2-8c57-301c79b302be\n\n### Additional context\n\nWould not say it is critical, but indeed it is annoying and happens even without fast refreshing.\nIt also errors only in dev mode. In build or generate mode I did not manage to reproduce it no matter how fast I spam page refresh.\n\nAlso it seems I started to notice it only yersterday and fell like everything was alright before... Maybe have not noticed or did not payed attention earlier...\n",[],1081,"nuxt","cli","open","Page reload causes stream/headers errors and crashes on clean Nuxt install ","2025-10-09T14:03:21Z","https://github.com/nuxt/cli/issues/1081",0.55023557,{"description":3180,"labels":3181,"number":3185,"owner":3172,"repository":3172,"state":3174,"title":3186,"updated_at":3187,"url":3188,"score":3189},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.15.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.11.0\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n(tested with node v20.18.1 too)\n\n### Reproduction\n\n1. Initialize fresh nuxt project: \n\n`npx nuxi@latest init project`\n\n2. Build and launch with --inspect:\n\n`pnpm i && pnpm build && node --expose-gc --inspect .output/server/index.mjs`\n\n3. Launch chrome inspect on chrome://inspect\n\n4. Launch 10000 request with ab:\n\n`ab -n 10000 -c 100 -k http://localhost:3000/`\n\n5. Garbage collector and take a snapshot 1\n\n6. Relaunch 10000 request with ab:\n\n`ab -n 10000 -c 100 -k http://localhost:3000/`\n\n7. Garbage collector and take a snapshot 2\n\n8. Compare snapshot\n\n### Describe the bug\n\n\n\n\nI see multiple object (maybe generated by unhead ?) that are still present between snapshot 1 and 2\n\n### Additional context\n\nMaybe cause by [#281](https://github.com/unjs/unhead/issues/281), but i'm not sure \n\n### Logs\n\n```shell-script\n\n```",[3182],{"name":3183,"color":3184},"pending triage","E99695",30164,"Memory leak with empty project","2024-12-05T16:14:30Z","https://github.com/nuxt/nuxt/issues/30164",0.6811162,{"description":3191,"labels":3192,"number":3194,"owner":3172,"repository":3172,"state":3174,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Environment\n\nPS C:\\Me\\Projects\\retrack> npx nuxt info\nWorking directory: C:/Me/Projects/retrack nuxi 5:02:23 PM\nNuxt project info: (copied to clipboard) nuxi 5:02:24 PM\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.17.0\n- Nuxt Version: 4.1.2\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.6\n- Package Manager: npm@10.2.1\n- Builder: -\n- User Config: compatibilityDate, devtools, build, css, vite, fonts, runtimeConfig, modules, experimental, tiptap, app, image, routeRules\n- Runtime Modules: @nuxtjs/tailwindcss@6.14.0, @vueuse/nuxt@13.9.0, @nuxt/fonts@0.11.4, nuxt-tiptap-editor@2.3.1, @nuxt/icon@1.15.0, @nuxt/image@1.11.0\n- Build Modules: -\n------------------------------\n\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new?template=bug-report.yml\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\n👉 Read documentation: https://nuxt.com\n\nPS C:\\Me\\Projects\\retrack> \n\n### Reproduction\n\nI understand that reproduction is necessary but I literally have no error trace to actually understand why is it happening or I would have tried to fix it myself. Tried refreshing nuxt cache, using --no-fork but randomly on any file save, 2 main things happen\n- Either it crashes without any error\n- Or it says `ℹ nuxt.config.ts updated. Restarting Nuxt... 4:54:55 PM` and crashes but the fact is nuxt.config.ts is not even updated. It doesnt happen all the times but 9/10 times it is happening.\n\n### Describe the bug\n\nThe bug is that nuxt dev server is crashing on any kind of hmr update after updating from NUXT 3 to Nuxt4. I understand that it maybe specific to my environment but no error is scary and I have no clue why is it happening. Would love to be provided with some diagnostic steps to find the issue. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3193],{"name":3183,"color":3184},33457,"HMR CRASHING WHEN UPGRADED PROJECT FROM NUXT3 to NUXT4","2025-10-11T11:36:11Z","https://github.com/nuxt/nuxt/issues/33457",0.6816512,{"description":3200,"labels":3201,"number":3212,"owner":3172,"repository":3172,"state":3213,"title":3214,"updated_at":3215,"url":3216,"score":3217},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.18.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.4\n- Nitro Version: 2.11.1\n- Package Manager: bun@1.2.4\n- Builder: -\n- User Config: ssr, routeRules, scripts, vite, modules, headlessui, devtools, css, build, tailwindcss, fonts, icon, i18n, imports, runtimeConfig, compatibilityDate\n- Runtime Modules: @nuxtjs/tailwindcss@6.13.1, nuxt-headlessui@1.2.0, @nuxtjs/i18n@8.5.1, @nuxt/fonts@0.7.2, @vueuse/nuxt@11.0.3, @pinia/nuxt@0.5.4, nuxt-svgo@4.0.4, @nuxt/icon@1.4.10, @nuxt/scripts@0.9.5\n- Build Modules: -\n------------------------------\n\n### Describe the bug\n\nAt my wits end, can't even run my app locally anymore. Using bun run dev, getting this: \n```\n$ nuxt dev\nNuxt 3.15.4 with Nitro 2.11.1 nuxi 3:22:51 PM\n 3:22:51 PM\n ➜ Local: http://localhost:3000/\n ➜ Network: use --host to expose\n\nℹ Using default Tailwind CSS file nuxt:tailwindcss 3:22:53 PM\n ➜ DevTools: press Shift + Alt + D in the browser (v1.7.0) 3:22:55 PM\n\nℹ Nuxt Icon server bundle mode is set to local 3:22:56 PM \n✔ Vite client built in 80ms 3:22:57 PM \n✔ Vite client built in 80ms 3:22:57 PM \n✔ Vite server built in 1613ms 3:22:58 PM \n✔ Vite server built in 1613ms 3:22:58 PM \n✔ Nuxt Nitro server built in 1017 ms nitro 3:23:00 PM \n✔ Nuxt Nitro server built in 1017 ms nitro 3:23:00 PM \nℹ Vite client warmed up in 2ms 3:23:00 PM \n\n WARN force closing dev worker after 5 seconds... \n```\n\nBrowser tab for some reason says Error: cannot access 'Hasher' before initialization. I only see the nuxt splash page (not the usual 500 error page or anything)\n\nWhen building/deploying, I get Cannot access 'nativeFuncLength' before initialization.\n\nI don't know where to begin! I rolled back to a commit that worked last week and getting the same error. Same on my coworkers machine. \n\nPlease help! I can't reproduce this and can't really provide my app because its a work thing and huge anyway so no idea where things went wrong. But as I said, things were fine last week (after fixing an issue with ohash/h3 and using override to use version 1.15.0)\n\n\n### Additional context\n\nAdditional context to my previous issue from last week, if related, can be found at this link to the nuxt discord help thread: https://discord.com/channels/473401852243869706/1343546685938208799\n\n### Logs\n\n```shell-script\n\n```",[3202,3203,3206,3209],{"name":3183,"color":3184},{"name":3204,"color":3205},"nitro","bfd4f2",{"name":3207,"color":3208},"needs reproduction","FBCA04",{"name":3210,"color":3211},"possible regression","B90A42",31222,"closed","WARN force closing dev worker after 5 seconds...","2025-03-17T08:38:05Z","https://github.com/nuxt/nuxt/issues/31222",0.66379225,{"labels":3219,"number":3224,"owner":3172,"repository":3172,"state":3213,"title":3225,"updated_at":3226,"url":3227,"score":3228},[3220,3223],{"name":3221,"color":3222},"3.x","29bc7f",{"name":3183,"color":3184},26642,"Request Error [SharedArrayBuffer, ArrayBuffer or ArrayBufferView.]","2024-04-04T11:59:57Z","https://github.com/nuxt/nuxt/issues/26642",0.66637635,{"description":3230,"labels":3231,"number":3234,"owner":3172,"repository":3172,"state":3213,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.18.0`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.5.4`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nIv been struggling to reproduce this on smaller projects, but its definitely only a problem on RC 12, RC 11 works fine.\r\n\r\nI noticed on larger projects that when requesting the router page nuxt RC12 produces a header overflow error on h3. which then causes the entire dev server to crash\n\n### Describe the bug\n\nit seems sometimes when going to routes we get a header overflow error from h3. \r\n\r\nthis also seems to only be a problem on nuxt dev, nuxt generate seems to handle everything ok for some reason\n\n### Additional context\n\n\r\n\r\n\n\n### Logs\n\n```shell\nERROR [h3] [unhandled] Parse Error: Header overflow 13:58:55\r\n\r\n at Socket.socketOnData (node:_http_client:534:22)\r\n at Socket.emit (node:events:513:28)\r\n at Socket.emit (node:domain:489:12)\r\n at addChunk (node:internal/streams/readable:315:12)\r\n at readableAddChunk (node:internal/streams/readable:289:9)\r\n at Socket.Readable.push (node:internal/streams/readable:228:10)\r\n at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)\n```\n",[3232,3233],{"name":3221,"color":3222},{"name":3183,"color":3184},15248,"RC12 header overflow","2023-01-19T17:46:42Z","https://github.com/nuxt/nuxt/issues/15248",0.6708851,{"description":3240,"labels":3241,"number":3247,"owner":3172,"repository":3172,"state":3213,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v22.11.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.6`\n- Package Manager: `pnpm@9.14.4`\n- Builder: `-`\n- User Config: `modules`, `css`, `future`, `robots`, `site`, `sitemap`, `app`, `runtimeConfig`, `auth`, `imports`, `components`, `$development`, `$production`, `ui`, `viewport`, `hooks`, `compatibilityDate`, `devtools`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `nuxt-viewport@2.2.0`, `@vueuse/nuxt@11.3.0`, `@nuxtjs/sitemap@7.2.7`, `@nuxtjs/robots@5.2.6`, `@sidebase/nuxt-auth@0.10.1`\n- Build Modules: `-`\n\n\n### Reproduction\n\nnormal use\n\n### Describe the bug\n\nWhen using nuxt normally and hot reloading from time to time. At some point the given error comes up on the website and in the console. Restarting nuxt will solve this bug temporarily but after some time it keeps happening again. It's seems to be only happening in development. \n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n[unhandledRejection] connect EADDRNOTAVAIL 127.0.0.1:32835 - Local (0.0.0.0:0) 11:14:27 AM\n\n at internalConnect (node:net:1097:16)\n at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)\n at node:net:1327:9\n at process.processTicksAndRejections (node:internal/process/task_queues:85:11)\n\n\n ERROR [request error] [unhandled] [GET] http://localhost:3000/albums/finn-test\n\n\nℹ Error: [GET] \"http://127.0.0.1:32835/__nuxt_vite_node__/invalidates\": \u003Cno response> fetch failed\n\n ⁃ at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n ⁃ at async $fetchRaw2 (node_modules/.pnpm/ofetch@1.4.1/node_modules/ofetch/dist/shared/ofetch.03887fc3.mjs:270:14)\n\n 265 ┃ await callHooks(\n 266 ┃ context,\n 267 ┃ context.options.onRequestError\n 268 ┃ );\n 269 ┃ }\n ❯ 270 ┃ return await onError(context);\n 271 ┃ } finally {\n 272 ┃ if (abortTimeout) {\n 273 ┃ clearTimeout(abortTimeout);\n 274 ┃ }\n 275 ┃ }\n\n ⁃ at async $fetch2 (node_modules/.pnpm/ofetch@1.4.1/node_modules/ofetch/dist/shared/ofetch.03887fc3.mjs:316:15)\n ⁃ at async default (node_modules/.pnpm/@nuxt+vite-builder@3.16.0_@types+node@22.13.10_eslint@9.22.0_jiti@2.4.2__lightningcss@1.29.2__q3uqehtdb7bjpxzyrfsc6xlhim/node_modules/@nuxt/vite-builder/dist/runtime/vite-node.mjs:23:23)\n ⁃ at async Object.renderToString (node_modules/.pnpm/vue-bundle-renderer@2.1.1/node_modules/vue-bundle-renderer/dist/runtime.mjs:173:19)\n ⁃ at async Object.render (node_modules/.pnpm/nuxt@3.16.0_@parcel+watcher@2.5.1_@types+node@22.13.10_db0@0.3.1_eslint@9.22.0_jiti@2.4.2__io_gfija2yyyxqt3oafwjkz4e3aki/node_modules/nuxt/dist/core/runtime/nitro/handlers/renderer.js:121:21)\n ⁃ at async Object.handler (node_modules/.pnpm/nitropack@2.11.6_typescript@5.8.2/node_modules/nitropack/dist/runtime/internal/renderer.mjs:25:22)\n ⁃ (async file://node_modules/.pnpm/h3@1.15.1/node_modules/h3/dist/index.mjs:2009:19)\n ⁃ at async Object.callAsync (node_modules/.pnpm/unctx@2.4.1/node_modules/unctx/dist/index.mjs:72:16)\n ⁃ at async Server.toNodeHandle (node_modules/.pnpm/h3@1.15.1/node_modules/h3/dist/index.mjs:2301:7)\n\n[CAUSE]\nTypeError {\n stack: 'fetch failed\\n' +\n ' at node:internal/deps/undici/undici:13392:13\\n' +\n ' at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\\n' +\n 'at async $fetchRaw2 (./node_modules/.pnpm/ofetch@1.4.1/node_modules/ofetch/dist/shared/ofetch.03887fc3.mjs:258:26)\\n' +\n 'at async $fetchRaw2 (./node_modules/.pnpm/ofetch@1.4.1/node_modules/ofetch/dist/shared/ofetch.03887fc3.mjs:270:14)\\n' +\n 'at async $fetch2 (./node_modules/.pnpm/ofetch@1.4.1/node_modules/ofetch/dist/shared/ofetch.03887fc3.mjs:316:15)\\n' +\n 'at async default (./node_modules/.pnpm/@nuxt+vite-builder@3.16.0_@types+node@22.13.10_eslint@9.22.0_jiti@2.4.2__lightningcss@1.29.2__q3uqehtdb7bjpxzyrfsc6xlhim/node_modules/@nuxt/vite-builder/dist/runtime/vite-node.mjs:23:23)\\n' +\n 'at async Object.renderToString (./node_mod'... 710 more characters,\n message: 'fetch failed',\n cause: Error {\n stack: 'connect EADDRNOTAVAIL 127.0.0.1:32835 - Local (0.0.0.0:0)\\n' +\n ' at internalConnect (node:net:1097:16)\\n' +\n ' at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)\\n' +\n ' at node:net:1327:9\\n' +\n ' at process.processTicksAndRejections (node:internal/process/task_queues:85:11)',\n message: 'connect EADDRNOTAVAIL 127.0.0.1:32835 - Local (0.0.0.0:0)',\n errno: -99,\n code: 'EADDRNOTAVAIL',\n syscall: 'connect',\n address: '127.0.0.1',\n port: 32835,\n },\n}\n```",[3242,3243,3246],{"name":3183,"color":3184},{"name":3244,"color":3245},"vite","3574D1",{"name":3207,"color":3208},31429,"Nuxt vite_node invalidates gives 500 Error","2025-08-10T20:14:09Z","https://github.com/nuxt/nuxt/issues/31429",0.67198944,{"description":3253,"labels":3254,"number":3257,"owner":3172,"repository":3172,"state":3213,"title":3258,"updated_at":3259,"url":3260,"score":3261},"While working on a Nuxt 4.0.0 project, the development server **unexpectedly crashes after saving a file** — typically after Hot Module Replacement (HMR) is triggered.\n\n🟡 **The crash does not occur every time** I save a file, but it starts happening **after a while**, and I can't identify a consistent cause. Once it starts, saving a file (which triggers HMR) often causes the dev server to shut down with the following error:\n\n---\n\n### 🧨 Error Output\n\n\n\n```\n✔ Vite server hmr 15 files in 42.47ms 2:22:20 AM\n\n ERROR [unhandledRejection] write EPIPE 2:22:28 AM\n\n at afterWriteDispatched (node:internal/stream_base_commons:159:15)\n at writeGeneric (node:internal/stream_base_commons:150:3)\n at Socket._writeGeneric (node:net:971:11)\n at Socket._write (node:net:983:8)\n at writeOrBuffer (node:internal/streams/writable:572:12)\n at _write (node:internal/streams/writable:501:10)\n at Writable.write (node:internal/streams/writable:510:10)\n at Socket.ondata (node:internal/streams/readable:1009:22)\n at Socket.emit (node:events:518:28)\n at addChunk (node:internal/streams/readable:561:12)\n```\n\n**Notes**\n\n- Issue began after upgrading to nuxt@4.0.0 and @nuxt/schema@4.0.0.\n- Possibly related to a recent change in how Vite handles streams or socket communication.\n- No custom server or middleware logic has been added.\n\nNpm version:\n```\n{\n \"npm\": \"10.9.2\",\n \"node\": \"22.16.0\",\n \"v8\": \"12.4.254.21-node.26\",\n \"uv\": \"1.51.0\",\n \"zlib\": \"1.2.12\",\n \"openssl\": \"3.5.0\"\n}\n```\n\nPackages:\n@commitlint/cli@19.8.1 \n@element-plus/nuxt@1.1.4 \n@nuxt/devtools@2.6.2 \n@nuxt/module-builder@1.0.1 \n**@nuxt/schema@4.0.0** \n@nuxt/test-utils@3.19.2 \n@nuxt/types@2.18.1 \n@nuxtjs/i18n@10.0.0 \n@nuxtjs/tailwindcss@6.14.0 \n@pinia/nuxt@0.11.2 \n@types/markdown-it@14.1.2 \n@types/moment-timezone@0.5.30 \n@types/sortablejs@1.15.8 \n@vitest/coverage-v8@3.2.4 \n@vue/test-utils@2.4.6 \napexcharts@5.2.0 \naxios@1.10.0 \neslint@8.57.1 \neslint-plugin-vue@10.3.0 \nhusky@9.1.7 \nmarkdown-it@14.1.0 \nmitt@3.0.1 \n**nuxt@4.0.0** \nopenai@5.9.0 \nsass@1.89.2 \nstylelint@16.21.1 \ntypescript@5.8.3 \nvite-tsconfig-paths@5.1.4 \nvitest@3.2.4 \n**vue@3.5.17** \nvue-router@4.5.1 \nvue3-apexcharts@1.8.0 \n\n\n### Reproduction\n\nRun npm install.\nRun npm run dev.\n",[3255,3256],{"name":3183,"color":3184},{"name":3210,"color":3211},32689,"❗ Nuxt 4.0.0 - Dev Server Crashes After Random Hot Reload (`write EPIPE` Error)","2025-07-20T08:11:08Z","https://github.com/nuxt/nuxt/issues/32689",0.67402387,{"labels":3263,"number":3271,"owner":3172,"repository":3172,"state":3213,"title":3272,"updated_at":3273,"url":3274,"score":3275},[3264,3267,3268],{"name":3265,"color":3266},"stale","ffffff",{"name":3183,"color":3184},{"name":3269,"color":3270},"2.x","d4c5f9",7736,"Loading chunk pages/index failed. (timeout: http://localhost:3000/_nuxt/pages/index.js)","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7736",0.6753973,{"labels":3277,"number":3281,"owner":3172,"repository":3172,"state":3213,"title":3282,"updated_at":3283,"url":3284,"score":3285},[3278,3279,3280],{"name":3265,"color":3266},{"name":3183,"color":3184},{"name":3269,"color":3270},5909,"Nuxt goes crazy when disabling eslint-module (mixing of generate/start and dev)","2023-01-22T15:33:07Z","https://github.com/nuxt/nuxt/issues/5909",0.67662436,["Reactive",3287],{},["Set"],["ShallowReactive",3290],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f1XTQJiL2DVSmtloJ9Vk0uI-ruRxlJKkBWBAaTHNJAYI":-1},"/nuxt/nuxt/33437"]