Reselect 5 switched memoization strategy from using fixed size LRU caching (1 by default) to a WeakMap strategy, relying on the GC to clean stuff up. But when one of the selectors’ arguments is a JS primitive like a string, it doesn’t get cleared.

Which brand is it? I assume the others you mentioned running Android are Garmin or maybe Wahoo? I’m also a bit annoyed by my Wahoo Elements' boot time, even though it’s a minor inconvenience.

Why not look at P90 load times? They should stay consistent no matter the hardware.

I’ve never had problems with unit tests in Node. E2E we do run in the browser though.

Context7 to load library docs

We’ve had a scenario where an AudioWorklet (separate environment, different stacktrace) would throw an error, pass it to the main thread, wrap it in a more generic error with { cause }, log to Sentry. You’ll see two separate errors stacktraces, but the errors are linked 👌

Oh no.. I might have been using it wrong as well. How did you measure the difference in perf? Some hints where to look at? React devtool extension profiler?

Any idea why?

Shout out to @lit.dev. I should try and experiment with it, but unfortunately stuck with React at work.

Declarative UI patterns are the biggest raison d'être for JS UI libs and frameworks.

Sounds good. One question, would it still be effective if everyone would use this? Wouldn’t compromised or broken packages just get noticed later?