Evan Jacobs

> As I would assume styled components wants to support ES modules and CommonJS in a hybrid approach, @probablyup how can we support you in going forward? Thank you very...

To complicate things, I think there needs to be separate entries in "exports" for the `styled-components/macro` and `styled-components/native` entrypoints. I'm preparing a commit to add those to this PR. We'll...

I've published the code on this branch at `styled-components@test` for verification

How was this handled prior to v6?

> Just though I'd share the workaround I'm using in the interim, in case it's of use to others; > > ```tsx > type DataAttributes = { > [K in...

> Is the intention to update Styled Components so this workaround isn't required on usage? It would seem odd to have to specify types for valid native HTML attributes like...

The error in your linked sandbox is just because you added a non-optional prop and then didn't compose the prop.

This should be fixed with 6.1.5, sorry about that!

Confirmed https://codesandbox.io/p/sandbox/wizardly-kapitsa-forked-7lcnhc?file=%2Fsrc%2FApp.tsx%3A11%2C1 Seems like the type is incorrectly widening, maybe because `Props` defaults to `object`.

The `styled` wrapper exposes a generic that intercepts passed props in order to determine a runtime target and extract types. I don't think a generic component assembled in this fashion...