Michał Dudak

We're gradually removing the usage of `cloneElement` across the library and relying on context for communication between components. With it, it'll be possible to place children on any level below...

Thanks! I'll see what I can do about it.

Sorry, the notification must have slipped through the cracks. I have other things on my plate right now, so feel free to take a stab at it.

The Popper runs well and does not complain about `styled` not being a function when bundled with Webpack - this leads me to believe it's a problem on Vite's side,...

I'm not able to reproduce it. @pavsidhu, could you please share details about your environment?

I couldn't reproduce it on Edge (I've got v111), but it happened once in Safari. I couldn't repeat it, though. It seems there is a subtle bug somewhere.

Thanks for investigating it. Let's wait for 18.3, then. I'm labelling it as "external dependency".

See #35489 for an explanation of what happened. Long story short - the current format is the one we had before 5.10.3. So it should work the same way as...

I meant that it has the same issue as @KevinVandy's code - it imports from a path three levels deep.

Looks good! I do have one remark about naming, but apart from that it's good to go.