vercel / vercel/next.js

Next `^16.3.0` emit `MaxListenersExceededWarning`

Open
#97,757 8 comments 15 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Runtime Server Actions
Dominant language
JavaScript
Stars
142k
Forks
32.5k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

Link to the code that reproduces this issue

https://github.com/RSickenberg/nextjs-httpxy-listener-leak

To Reproduce

Readme on the repo provided.

Current vs. Expected behavior

Before 16.3.x, issues were not dispatched. This is probably a regression.

Provide environment information
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.6.0: Fri Jul 31 19:18:49 PDT 2026; root:xnu-12377.161.14~5/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 24.18.0
  npm: 12.0.1
  Yarn: 1.22.17
  pnpm: N/A
Relevant Packages:
  next: 16.3.2
  eslint-config-next: N/A
  react: 19.2.8
  react-dom: 19.2.8
  typescript: 6.0.3
Next.js Config:
  output: standalone
Which area(s) are affected? (Select all that apply)

Not sure, Server Actions, Runtime

Which stage(s) are affected? (Select all that apply)

Other (Deployed), next dev (local), next start (local)

Additional context

Tested until ^16.3.1-canary.26 or 16.3.2.

Related discussion: https://github.com/vercel/next.js/discussions/96973 & https://x.com/timneutkens/status/2090399274525655458

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README in the linked reproduction repository and run it against Next 16.3.2, then compare the behavior with the earlier versions listed in the issue. Done means confirming the MaxListenersExceededWarning and narrowing the regression to the affected runtime or Server Actions path.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nextjs, node.js, react
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.