unhandledRejection Error when running npm run dev

[dhavalveera]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home Single Language
    Binaries:
      Node: 16.14.2
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.2.3
      eslint-config-next: 12.1.6
      react: 18.1.0
      react-dom: 18.1.0

What browser are you using? (if relevant)

Chrome 103.0.5060.134

How are you deploying your application? (if relevant)

next dev

Describe the Bug

event - compiled client and server successfully in 394 ms (1715 modules)
error - unhandledRejection: Error: aborted
    at connResetException (node:internal/errors:683:14)
    at abortIncoming (node:_http_server:592:17)
    at socketOnClose (node:_http_server:586:3)
    at Socket.emit (node:events:406:35)
    at TCP.<anonymous> (node:net:661:12) {
  code: 'ECONNRESET'
}

Expected Behavior

it should not throw the error

Link to reproduction

.

To Reproduce

I updated the nextjs version to 12.2.3 and also updated the react & react-dom package, but still the issue persist.

[ijjk]

Hi, this should be fixed in the latest canary of Next.js v12.2.4-canary.8, specifically this PR.

[blackwizard111]

I am getting the same error and couldn't find the solution.. Help me

[kereh]

@ijjk wow thank you, it works for me :)

[marcelobitorical]

Thank you! Works great

[mrLuisFer]

Hi, this should be fixed in the latest canary of Next.js v12.2.4-canary.8, specifically this PR.

I had the same error, and this fixed it
Thanks 👍🏻

[Yorkshireman]

v12.2.4 fixes this now

[xiaocai-rookie]

Hi, this should be fixed in the latest canary of Next.js v12.2.4-canary.8, specifically

I has this question,I use version 12.3.1,but Error is [error - unhandledRejection: undefined]

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.