No bundle size changes

Generated by 🚫 dangerJS against 6c61127

@luminaxster Which breaking change did you identify?

@luminaxster I have tried to improve the changes to mention the breaking change coming from v5.0.0-alpha.17. Could you have a look to see if it matches your expectation? Thanks

Cool to see that. But I have a question. Now the recommended order is JSS > emotion, this order seems not breaking our app currently. But what if I use a JSS based (not migrated yet) MUI component and style it with emotion? By this order, my customization will not work.

But what if I use a JSS based (not migrated yet) MUI component and style it with emotion? By this order, my customization will not work.

@Jack-Works Yeah, you are right. We have a couple of visual regression tests in our codebase that is broken because of this (I believe). You could use import { styled } from '@material-ui/core/styles' (JSS) then switch to experimentalStyled (emotion). The two should have the same API.

It seems like this belongs in the migration guide even more-so than the change log.

It seems like this belongs in the migration guide even more-so than the change log.

This is most relevant during the phase where the codebase still mix JSS and emotion. We have it in the migration guide: https://next.material-ui.com/guides/migration-v4/#styled-engine.

I followed your changes @oliviertassinari, It works like a charm now. Since that was the first migrated component and I was not customizing it, I lazily skipped over the emotion details. Following on @mbrookes, indeed, what is missing is mentioning the guide when components are migrated, a compromise may be to add a note like this each time a component has been migrated to emotion:
[Emotion] [More details on setting up your migration to emotion (if you haven't already)](https://next.material-ui.com/guides/interoperability/#css-injection-order) in the documentation..
It may keep the "troubleshooting" of the migration changes self-contained as the changelogs pile up.

Thank you so much for your time and patience! =P.

@luminaxster Thanks for the confirmation. Yeah, this migration period will be challenging to handle. The good news that it will only get better over time.