Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@nestjs/common@^10.0.0(node:47898) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit #12696

Closed
3 of 15 tasks
aasisdhakal opened this issue Nov 6, 2023 · 4 comments
Labels
needs triage This issue has not been looked into

Comments

@aasisdhakal
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

While setting up a new project and running the npm install command, I encountered the following error message:

@nestjs/common@^10.0.0(node:47898) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit

Minimum reproduction code

https://github.com/nestjs/typescript-starter

Steps to reproduce

  1. Clone [email protected]:nestjs/typescript-starter.git
  2. Switch to node version v20.9.0
  3. npm install

Expected behavior

It works perfectly on node 18

Package

  • I don't know. Or some 3rd-party package
  • @nestjs/common
  • @nestjs/core
  • @nestjs/microservices
  • @nestjs/platform-express
  • @nestjs/platform-fastify
  • @nestjs/platform-socket.io
  • @nestjs/platform-ws
  • @nestjs/testing
  • @nestjs/websockets
  • Other (see below)

Other package

No response

NestJS version

10.0.0

Packages versions

[System Information]
OS Version : Linux 6.2
NodeJS Version : v20.9.0
NPM Version : 10.2.1

[Nest CLI]
Nest CLI Version : 10.2.1

[Nest Platform Information]
platform-express version : 10.2.8
schematics version : 10.0.3
testing version : 10.2.8
common version : 10.2.8
core version : 10.2.8
cli version : 10.2.1

Node.js version

20.9.0

In which operating systems have you tested?

  • macOS
  • Windows
  • Linux

Other

No response

@aasisdhakal aasisdhakal added the needs triage This issue has not been looked into label Nov 6, 2023
@micalevisk
Copy link
Member

micalevisk commented Nov 6, 2023

I didn't managet to reproduce this here on my Ubuntu using nodejs v20.9.0.

So I don't think that this is something we can fix on our side.

Try it out using npm i --ignore-scripts

@Tony133
Copy link
Contributor

Tony133 commented Nov 6, 2023

I also tried it on macOS but could not replicate it ( see screenshot ), maybe try reinstalling node

screen-node-v20 9 0

@micalevisk
Copy link
Member

thanks Tony

@micalevisk micalevisk closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2023
@sgarner
Copy link

sgarner commented Dec 13, 2023

FYI, this was a bug in Node.js: nodejs/node#50136

Fixed in node v20.10.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue has not been looked into
Projects
None yet
Development

No branches or pull requests

4 participants