Aside: I’ve always found the timers APIs to be a little tricky, anyway. They aren’t “hard”, per se, but it’s a lot like implementing a binary search: easy, but also easy to mess up.
I feel similarly to the whole EventEmitter approach. Every EventEmitter has its own semantics about what events are emitted and when, and it can be very easy to accidentally assume certain behaviors will or won’t happen, or that certain event orders are guaranteed, etc. And then it’s also easy to cause memory leaks by not removing event listeners when you’re done with them. I’ve seen a lot of slightly-incorrect StackOverflow answers when it comes to dealing with Node.js’s various EventEmitters.
Looks like they’re planning to release the fix in Next.js in v15:
https://github.com/vercel/next.js/commit/7208535786581ca17d4f8ca3bc5e752d6b2e474b
We haven’t observed any problem with memory usage in the framework.
Aside: I’ve always found the timers APIs to be a little tricky, anyway. They aren’t “hard”, per se, but it’s a lot like implementing a binary search: easy, but also easy to mess up.
I feel similarly to the whole EventEmitter approach. Every EventEmitter has its own semantics about what events are emitted and when, and it can be very easy to accidentally assume certain behaviors will or won’t happen, or that certain event orders are guaranteed, etc. And then it’s also easy to cause memory leaks by not removing event listeners when you’re done with them. I’ve seen a lot of slightly-incorrect StackOverflow answers when it comes to dealing with Node.js’s various EventEmitters.