Open dukedhx opened 4 years ago
I have same problem
I am also experiencing this. I don't know if it's related but I am also using Vuetify
Also experiencing this and also using Vuetify
Also experiencing this and I'm also using Vuetify here, specifically vuetify@2.2.34
.
By adding require('events').EventEmitter.defaultMaxListeners = 50;
in vue.config.js
(source) I'm able to ignore this warning because I couldn't fix it and it's polluting my console output all around.
Still need a real fix for this.
Edit: I've only got one entry in the devServer.proxy
section in my vue.config.js
Also experiencing this with Vuetify. In my case it's caused specifically by adding a 10th proxy object in vue.config.js to devServer.proxy
. The warning does not occur with 9 or fewer kv pairs in devServer.proxy
.
Not seeing any info related to this in the relevant docs.
It's Nov 2022 and I'm also getting this 🤕
(node:28946) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 upgrade listeners added to [Server]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
Version
3.11.0
Reproduction link
https://github.com/Autodesk-Forge/forge-digital-catalog
Environment info
Steps to reproduce
run "vue-cli-service serve" and got multiple MaxListenersExceededWarning during compilation - this seems to be on and off but 9 out 10 the warnings would be thrown like below:
40% building 48/58 modules 10 active ...s/@mdi/font/css/materialdesignicons.css(node:1761) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 VElement listeners added. Use emitter.setMaxListeners() to increase limit (node:1761) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 VElement listeners added. Use emitter.setMaxListeners() to increase limit (node:1761) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 VElement listeners added. Use emitter.setMaxListeners() to increase limit 40%
What is expected?
No MaxListenersExceededWarning should be thrown
What is actually happening?
The project seems to be compiled and the dev serve seems to run as expected despite the warnings