VSCode supports inlay hints for that (but I'm not a fan of them):

`"javascript.inlayHints.parameterNames.enabled": "all"`

Just migrate to Vitest Browser Mode 😉

How is this measured? For me (iOS 16 / iPhone 8) it shows a total app startup time of 1.3s, but if I record the screen and check the time it's actually 2.5s (from iOS app-icon-zoom animation completed - "New Tab" page is visible).

Yes, maybe. We'll see it when it's released.

Not sure how this would work with Parent and Child being in different files. We'll end up with circular dependencies.

And if we see context as a kind of dependency injection, I don't really care *where* the context is coming from, so binding it to a specific component doesn't feel right.

We use errors for critical things/potential bugs (e.g. button without type attribute) and warnings for things that that are okay while coding (e.g. debugger statement). Both need to be fixed before merging (max-warnings=0). Just looks a bit nicer with the different colors in the IDE.

yep, so weird 🤯

> If an attribute name is not a valid JS identifier (like a data-* attribute), it is not considered to be an error if it is not found in the element attributes type.

It's not even typed as `any`, JSX just allows them without type-checking 😕

Here's the code

Lucky you - we use a component library that often re-creates DOM elements when unstable values or callbacks are passed in 🤷‍♂️ 😢

Isn't that expected as Recoil is no longer maintained?

> Reproduction: I'm not lying

😂

I don't have many email newsletters and just keep them in Readwise Reader. What's your workflow? Maybe you can use Kill the Newsletter.

Here we go 🥳

I'm struggling a lot with that 🤔 I use Readwise for RSS and email, but it’s not great for code-heavy articles or long-term bookmarking. Raindrop is good for bookmarks but lacks RSS/email. Obsidian + Clipper sounds nice for archiving, but syncing from Readwise is manual (and I'm lazy).

You can already display properties 🤨

Nice setup 👍 We use Vitest + happy-dom but we'll evaluate Vitest's browser mode when it's stable.

We have units tests for transition-heavy machines that are not fully covered by UI tests. UI tests give as much more confidence, they test everything together (just API request are mocked).