resolve max event listeners warning

[thescientist13]

Current State

As part of the recent v0.33.0 release, the Greenwood website started showing this message when building the site for production

(node:85019) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 Symbol(kWorkerFreedEvent) listeners added to [WorkerPool]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)

Desired State

Not sure how bad of an issue it is to have, but it wasn't there before, so would like to understand what's happening and resolve it.

Additional Context

Not sure if it was re-introduced as part of #1546 ? Or maybe as part of the upgrade to Node 22.18.0

This was an issue we've seen before and fixed / removed, but it was kind of a brute force solution, so not sure if that's what we want to again 🙈

• MaxListenersExceededWarning: Possible EventEmitter memory leak detected #141
• clear up max event listeners warning #145
• remove setMaxListeners suppression call #1046

Or maybe we need to do more about parallel serialization as part of #970 / #720 ?

[KaiPrince]

Based on the warning message including kWorkerFreedEvent, I believe the issue originated in #983, not #1546

[KaiPrince]

My guess is it's happening here:

greenwood/packages/cli/src/lib/threadpool.js

Line 62 in f5d0efd

this.once(kWorkerFreedEvent, () => this.runTask(task, callback));

Could try either capping the numThreads or raising the listener limit to equal numThreads

[thescientist13]

Interesting, I wonder why it only started showing up (again) in the website repo as part of the v0.33.0 release line? 🤔
ProjectEvergreen/www.greenwoodjs.dev#211 (comment)

But yeah, any thoughts you have feel free to give them a try! Here's the website repo, where I am able to reproduce
https://github.com/ProjectEvergreen/www.greenwoodjs.dev

edit: I wonder if it's because this operation should also be run in the thread pool as well?