AtlasKit migration from SC to Emotion introduces breaking changes

Hey Remie!

Just responded to your comment in this thread and created a follow-up ticket for you here: DS-7725

Can we continue the conversation there :pray:

Here’s some context for others that might come across this issue:

Thanks for the heads up, I definitely want to figure out why you’re seeing that error! To add some background, react-select (used by @atlaskit/select ) includes its own version of emotion (v11) where we in Atlaskit are depending on v10. So far we’ve expected these two versions to be interoperable after collaboration with the emotion authors. We have also tested and shipped these to our products with no issue, however It’s possible that we’re not using the same code-paths or environment that you might be.

4 Likes