Lucas Eckman

Re-posting this from the [issue](https://github.com/styled-components/babel-plugin-styled-components/issues/379). >We have run into this issue using module federation and our in-house component library. babel-plugin-styled-components successfully namespaces styled components written within each app, preventing class...

We have run into this issue using module federation and our in-house component library. babel-plugin-styled-components successfully namespaces styled components written within each app, preventing class name collision when multiple apps...

EDIT: Sorry, I meant to mention in my comment that for the menuPortal approach to work, you need to be working with portals, and pass e.g. `document.body` to the `menuPortalTarget`...

Sorry, I meant to mention in my comment that for the menuPortal approach to work, you need to pass e.g. `document.body` to the `menuPortalTarget` in the Select. If you are...

You can certainly accomplish handling z-index without portals, but portals are the most straightforward way without actually understanding z-index and stacking context. Setting a very high (even the highest possible)...

I agree that the react-select docs don't give an in-depth explanation of what portaling is or why you'd need it, or how do deal with z-index. [From their docs](https://react-select.com/advanced#portaling) >React-select...

The bottom line is that the default menu z-index of 1 already does work for almost every situation where you're not setting your own z-index on other elements. `z-index: 1;`...