ERROR [unhandledRejection] read/write ECONNRESET

[cdwmhcc]

Version

18.17.1 18.18.0 18.18.1 20.8.0

Platform

Microsoft Windows NT 10.0.22621.0 x64

Subsystem

No response

What steps will reproduce the bug?

1. npx nuxi@latest init my-app
2. select pnpm
3. init git
4. cd my-app
5. pnpm dev

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

I'm not sure if this is a Nodejs issue or a nuxt.js issue. it happens almost every time.

What do you see instead?

 ERROR  [unhandledRejection] write ECONNABORTED                                                               13:33:13

  at afterWriteDispatched (node:internal/stream_base_commons:160:15)
  at writeGeneric (node:internal/stream_base_commons:151:3)
  at Socket._writeGeneric (node:net:952:11)
  at Socket._write (node:net:964:8)
  at writeOrBuffer (node:internal/streams/writable:447:12)
  at _write (node:internal/streams/writable:389:10)
  at Writable.write (node:internal/streams/writable:393:10)
  at Socket.ondata (node:internal/streams/readable:817:22)
  at Socket.emit (node:events:514:28)
  at addChunk (node:internal/streams/readable:376:12)


 ERROR  [unhandledRejection] read ECONNRESET                                                                  13:33:16

  at TCP.onStreamRead (node:internal/stream_base_commons:217:20)


 ERROR  [unhandledRejection] read ECONNRESET                                                                  13:33:16

  at TCP.onStreamRead (node:internal/stream_base_commons:217:20)

Additional information

---

• Operating System: Windows_NT
• Node Version: v20.8.0
• Nuxt Version: 3.7.4
• CLI Version: 3.9.0
• Nitro Version: 2.6.3
• Package Manager: pnpm@8.9.0
• Builder: -
• User Config: devtools
• Runtime Modules: -
• Build Modules: -

---

[bnoordhuis]

Converted to a discussion. Not a bug (in node) because it simply bubbles up the errors that the operating system reports. It's your job to handle those.

I'm going to guess nuxt sprinkles promises on top but in plain node you listen for 'error' events. Not handling those is (usually) a fatal error.

[Foddie2]

What about on Linuxt environment. Am getting the same error

` ERROR [unhandledRejection] read ECONNRESET

at TCP.onStreamRead (node:internal/stream_base_commons:217:20)`