Closed as not planned
Closed as not planned
Description
Self-service
- I'd be willing to implement a fix
Describe the bug
Upon installing a repo (previously managed using Yarn 3) with Yarn 4, I got hit with these warnings:
➤ YN0000: · Yarn 4.0.0
➤ YN0000: ┌ Resolution step
➤ YN0000: │ MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
➤ YN0000: │ MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
➤ YN0000: │ MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
(and it goes on for 100s of lines)
To reproduce
I can't reliably reproduce that. I was under poor network conditions at a time, though, so maybe it's related?
Environment
System:
OS: macOS 14.0
CPU: (8) arm64 Apple M2
Binaries:
Node: 20.7.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-abf151ce/node
Yarn: 4.0.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-abf151ce/yarn
npm: 10.1.0 - /opt/homebrew/bin/npm
Additional context
No response