Reduce bundle size for Material-UI

[sdellis]

Explore babel-plugin-import option (or even better, webpack treeshaking) discussed here.

[sdellis]

With Webpack resolve/alias was able to reduce it by around 7K. LOL.

So, it looks like we should be targeting ES6, not umd for our builds if we want to do tree shaking... these should be separate builds. Oh, also there's this:

If you want to create a tree-shakable library, you cannot bundle it with webpack.

[camillevilla]

@sdellis I'm sure you're already a pro at bundle analysis, but Jack added a lil' script nicety in #1708 that might be useful.

[sdellis]

@camillevilla I'm definitely not a pro on this. I tried out the size-limit script @mejackreed added. Are we ok with the minimized bundle being > 1MB if gzipped at under < 300KB? When running with the --why argument, I only see the mirador bundle, not all the dependencies. I think this is because a umd build doesn't allow for that kind of insight. We will need to use the Material-UI ES6 distribution to get tree shaking to work like that. We will need to produce our own ES6 distribution if we want to allow tree shaking of the Mirador 3 library.

[sdellis]

Additional discussion around tree shaking the Material-UI bundle can be found here:
#1635 (comment)