Post

Why doesn't React have slots?

I would argue that React already has slots with a different syntax via component props. It's not a perfectly ideal syntax, but, arguably, it's better than the string-matching chaos of web components. After all, I can write <ProfileCardRaw name="BellCube" description={<p>A very cool person!</p>} />

Imo <ProfileCardRaw description={<p>A very cool person!</p>}/> (especially if there are more props/render props!) is a lot harder to read/parse than <ProfileCardRaw> <p slot="description">A very cool person!</p> </ProfileCardRaw> This is an opinion, other peoples opinions may differ.

perhaps, I think that's only really true if you have one or few props. when you have many, it's nicer to more quickly see slots imo. but for slots, I'd do this syntax:

(counter to an earlier point I made) I think the platform kinda messed up on the syntax of slots, and the above is way better than: <arbitrary-element slot="whatever"> additionally, many slots don't even need or want a host element (p in your example).

Respectfully disagree, I think the platforms implementation of slots is fine

that's fine. But how do you explain the goofy semantics of the arbitrary `<p>` tag?

What goofy semantics? Using the slot attribute? I just don't think that's goofy.

Why is an element required? What if i don't want an arbitrary element wrapping the slot? 🤔

You have an element wrapping the content in your proposed JSX syntax, it's just not a DOM element, it's a JSX thing. Elements are containers for other nodes. Especially with `display: contents`, it's really not bad to use a container when you need to group nodes.

Wait, isn't <>...</> a document fragment, not an element?