[core] More aggressive transpilation

[oliviertassinari]

Try @goto-bus-stop's idea out #11358

   {
     name: 'The initial cost people pay for using one component',
     webpack: true,
     path: 'packages/material-ui/build/Paper/index.js',
-    limit: '26.0 KB',
+    limit: '18.0 KB',
   },

[TrySound]

Update size snapshot please to see the whole picture.

[oliviertassinari]

This is very encouraging, we save almost 10kB gzipped when importing a single component 😍. However, I have found a first issue on IE11. CSS precedence is all wrong. I have found the root cause 🐰

[oliviertassinari]

@TrySound Alright, I'm updating it. But I don't think that we can ask people to update it everytime they commit a change.

[TrySound]

@oliviertassinari We can actually. There is matchSnapshot option which may fail in CI :)

[TrySound]

Would you like me to send a PR with it?

[oliviertassinari]

@TrySound Technically, yes we can. But I mean from an operational point of view. I don't think that it worth the pain. Most of the time, we don't work on the bundling pipeline.
For instance, it's why I have moved the visual regression tests to an external service. It was a real pain in the ass to have to update all the baseline images every time we were changing a single line of CSS. An approve button streamline the experience.

[TrySound]

What if we will just update snapshot on precommit hook?

[oliviertassinari]

@TrySound I have never used a single pre-commit hook. I have always found it to slow me down. Updating the snapshot takes ~30s end-to-end unless I'm missing something.

[TrySound]

For prettier precommit hooks are quite fast. But yeah bundling on every commit will be noisy.

[TrySound]

So let's just update snapshot manually when some changes are happened.

[goto-bus-stop]

should be negative?

[oliviertassinari]

😆

[oliviertassinari]

IE 11, Safari 10, Edge 15, Firefox 45 seems OK.
This type of change is scaring me out.