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
First of all, thank you for this incredible library! timers in web workers are wonderful and much more reliable
MDN says Passing an invalid ID to clearTimeout() silently does nothing; no exception is thrown but workers-timers throw an error when i pass a invalid id to clearInterval or clearTimeout and this error cannot caught by try-catch, this has caused me some strange infinite loop problems
Hi @luccasr73, thanks for reporting this. When looking into it I realized that this behavior even caused a memory on the worker. I aligned the behavior with the one of the native timers. I published the changes as v8.0.0.
The only remaining difference should be that intervals and timeouts are handled separately.
The native WindowTimers only maintain a single list of timers. But `worker-timers` maintains two separate lists to store the ids of intervals and timeouts internally. WindowTimers allows intervals to be cancelled by calling `clearTimeout()` and the other way round because it stores all timers in a single list. This is not possible with `worker-timers`.
First of all, thank you for this incredible library! timers in web workers are wonderful and much more reliable
MDN says
Passing an invalid ID to clearTimeout() silently does nothing; no exception is thrown
butworkers-timers
throw an error when i pass a invalid id to clearInterval or clearTimeout and this error cannot caught by try-catch, this has caused me some strange infinite loop problemsrepro: https://stackblitz.com/edit/vitejs-vite-sg1zde?file=src%2FApp.tsx
The text was updated successfully, but these errors were encountered: