In #7032 we have added a script that creates a bundle with tree-shaking enabled. We have also added tests that show which components are pulled together, which highlights some problems we have with tree-shaking. Next task is to debug 1. why these components are pulled together and 2. if it is a problem

The task is:

1. Add a visualization tool that shows which file contributes how much kB.
2. Add a debug trace tool that shows why does component A include component B. For example, if I import Area component, the final bundle has Pie in it. Why?

This visualization and trace can run only on-demand, it does not need to be integrated with CI. If you need to add any dependencies make sure they are dev-only, and none of this ends up in the npm package.