Remove Rollup and just use Webpack

[d3dc]

Rollup is an additional dependency, that has its own set of problems and plugins.

I didn't use Webpack initially, because I just went with what works.

To use Webpack, we have to remove the HTML plugin, and change the inputs/outputs. This doesn't seem like that much work using the craco utils?

Update: and then the bundled code needs to be built in a format that allows the most flexible use - it seems like we would want ESM bundles to let motherships use treeshaking across the fleet

[d3dc]

It looks like ES modules may not be possible until Webpack 5

Is tree-shaking a must-have?

• yes - rollup can bundle CommonJS inside ESM
• no - Its much simpler to output a production library build from Webpack - which has an IIFE until v5

[d3dc]

Why not just transpile with babel and do nothing else?

[d3dc]

For now using rollup as a "task runner" lets us emit ESM.

If we just run babel, aliases won't be resolved in stylesheets. Relative paths in stylesheets may also break. I used rollup-plugin-rebase to address this in a hacky way.

[d3dc]

This leaves us with the question:

• Specializing for ESM means we are targeting an environment that gets bundled.
• Do we need to create a UMD build along-side the module?

[d3dc]

For now, rollup is used to create an ESM and a UMD bundle both with peer dependencies, instead of tackling questions with CommonJS etc.