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/cli MaxListenersExceededWarning with node.js 12.9.0 version #2783

Closed
neverhesitate opened this issue Aug 20, 2019 · 4 comments
Closed

Comments

@neverhesitate
Copy link

Bug Report

npm i -g @nestjs/cli install command gives the below warning with the latest node.js release;

Current behavior

(node:15352) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit

Environment

Nest version: 6.6.4

  • Node version: v12.9.0
  • Platform: Windows 10
@neverhesitate neverhesitate added the needs triage This issue has not been looked into label Aug 20, 2019
@BrunnerLivio
Copy link
Member

BrunnerLivio commented Aug 21, 2019

FYI: I can not reproduce this error on Ubuntu 18.04 with Node v12.9.0:

$ nest new my-app -p npm && cd my-app
$ npm run start &
$ curl localhost:3000
Hello World!

$ nest info

[System Information]
OS Version     : Linux 4.15
NodeJS Version : v12.9.0
NPM Version    : 6.10.2
[Nest Information]
platform-express version : 6.0.0
common version           : 6.0.0

Seems like either a Windows-only problem or something else.

Edit: Seems like a Windows-only Node.js bug. Therefore closing here, since it is not related to Nest. nodejs/node#29239

@BrunnerLivio BrunnerLivio removed the needs triage This issue has not been looked into label Aug 21, 2019
@jayakusumah
Copy link

same issue with mojave , nodejs v10.16.0

@ddehghan
Copy link

It happens also on docker node:12.10.0-alpine

@lock
Copy link

lock bot commented Dec 15, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants