Tree-shaking

[onexdata]

Adding tree-shaking is low hanging fruit since this module will have every component registered globally.

You can go through each components template and log where it is called and how many times.
You can go through each components $options and see where state is called and how many times.

If a component is not called, or an action/mutation is not called, it can be flagged for removal, or at least warn the developer that a component is being bundled that is never actually used.

In a production build, the unused components can simply be left out of the final build.

[AmirrezaNasiri]

This is a great idea indeed! Unfortunately I'm currently busy with my projects but I'll definitely consider this one. For now, a pull request would be very very welcome ✌