You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(node:458793) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 eleventy.resourceModified listeners added to [AsyncEventEmitter]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
Running node --trace-warnings opens a node prompt. I'm afraid I don't know how to proceed from there.
I searched the web, and found a Stack Overflow post that said,
This is typically an indication that some code is repeatedly adding the same event handler over and over again....
I don't really know if the problem is with 11ty itself, or something I'm doing with my configuration.
If there is anything I can do to provide more information, let me know.
Reproduction steps
I have been unable to duplicate the error, so I cannot list reproduction steps.
Expected behavior
No response
Reproduction URL
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Operating system
Ubuntu 22
Eleventy
3.0.0-alpha.5
Describe the bug
I got this error when running 11ty in watch mode:
(node:458793) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 eleventy.resourceModified listeners added to [AsyncEventEmitter]. Use emitter.setMaxListeners() to increase limit (Use `node --trace-warnings ...` to show where the warning was created)Running
node --trace-warnings
opens a node prompt. I'm afraid I don't know how to proceed from there.I searched the web, and found a Stack Overflow post that said,
I don't really know if the problem is with 11ty itself, or something I'm doing with my configuration.
If there is anything I can do to provide more information, let me know.
Reproduction steps
I have been unable to duplicate the error, so I cannot list reproduction steps.
Expected behavior
No response
Reproduction URL
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered: