Repository navigation
Errors on node versions after 22.13.0 #76900
Description
Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/quizzical-shaw-5qj8pk?workspaceId=ws_LyqK2TEkFjjDL6sZSuBF9w
To Reproduce
Bug in nodejs introduced in this commit nodejs/node@81c94a32e4
Here is the fix nodejs/node#56807
You can temporarily add workaround for this here:
const symbols = Object.getOwnPropertySymbols(signal)
const kMaxEventTargetListeners = symbols.find(
s => s.description === 'events.maxEventTargetListeners'
)
if (kMaxEventTargetListeners) {
// The default events.defaultMaxListeners value is 10.
// https://nodejs.org/api/events.html#eventsdefaultmaxlisteners
signal[kMaxEventTargetListeners] = 10
}Current vs. Expected behavior
I faced errors in catchall api routes
Provide environment information
Operating System:
Platform: linux
Arch: x64
Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023
Available memory (MB): 4242
Available CPU cores: 2
Binaries:
Node: 20.9.0
npm: 9.8.1
Yarn: 1.22.19
pnpm: 8.10.2
Relevant Packages:
next: 15.2.2-canary.3 // Latest available version is detected (15.2.2-canary.3).
eslint-config-next: N/A
react: 19.0.0
react-dom: 19.0.0
typescript: 5.3.3
Next.js Config:
output: N/AWhich area(s) are affected? (Select all that apply)
Runtime
Which stage(s) are affected? (Select all that apply)
Other (Deployed)
Additional context
No response
Activity
github-actions commentedon Mar 7, 2025
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.
Why was this issue closed?
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.
The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.
What should I do?
Depending on the reason the issue was closed, you can do the following:
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.
My repository is private and cannot make it public
In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
I did not open this issue, but it is relevant to me, what can I do to help?
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.
I think my reproduction is good enough, why aren't you looking into it quickly?
We look into every Next.js issue and constantly monitor open issues for new comments.
However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.
Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.
Useful Resources