Evan Jacobs

Just another thought, you could provide an untyped initial component and then retype it using `as`. e.g. ```tsx ``` It's equivalent to your sandbox but types properly since it doesn't...

@Dron007 I think this is a different issue. @anksuthar need a better reproduction to be able to help you

I prepared an [alternate implementation](https://github.com/styled-components/styled-components/pull/4242) that will not leak the `theme` prop in normal scenarios. Passing `theme` always would be kind of a breaking change for v6 since the current...

This issue is fixed in 6.1.4 when using `attrs` to provide an alternate theme prop https://codesandbox.io/p/sandbox/styled-component-with-react-select-forked-m62nj4?file=%2Fexample.js%3A7%2C18 I don't think we can let `theme` through as a normal prop without a...

I provided the setup in the forked sandbox I linked in my comment. You need to provide the theme as a different prop and then alias it inside attrs

I think ultimately the right fix is to deprecate passing a styled-components `theme` over props and use `$theme` instead. Then `theme` can just be a normal prop.

> It would be nice if we could get a full list of what's prefixed and possibly even pick and choose which ones we want or to specify which browsers...

> user-select: none Aside, shocked that `user-select` still needs prefixing in 2023.

The functionality isn't removed, it's just not on by default: https://styled-components.com/docs/faqs#vendor-prefixes-are-omitted-by-default

Yeah... my intention here was to default to shipping less CSS to the client. I get that it could be confusing though. I wonder if we could somehow combine browserslist...