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?

Seems legit though! Cool 🖤 blog.burrard-lucas.com/2021/03/star...

Tragedy of the modern world.. I find it super hard to believe it’s a real photo.

The underlying issue maybe is that we as js/ts devs shouldn’t have the need to switch linter or formatter every year.

Everything Altman and Amodei say is pure marketing. They’re prepping for more funding. Listening to them for honest predictions doesn’t make any sense.

And a flag to use eslint.config.ts

Install docs for many js libraries start with examples showing how to install it in different package managers; npm, pnpm, yarn, bun, deno. I know they’re not all solving exactly the same things, but I’d also maybe expect fewer “winners” to remain after a while.