Subexports and treeshaking

[Tahul]

While discussing whether or not we should move to monorepo with @cpreston321 and @alex-eliot; I thought that maybe instead we should only improve the exports and start testing the package for treeshaking.

That would also be a great opportunity for both of you to make a tour of all package exports and maybe start thinking of some improvements that could be made to general structure.

What I would expect:

• @vueuse/motion exports everything "user-facing" at component level like <Motion />, useMotion and other composables
• @vueuse/motion/presets exports all the presets and related purposes
• @vueuse/motion/plugin would maybe only export the plugin (could also be exposed from @vueuse/motion but maybe we can promote a "plugin-less" usage in long term?)

[cpreston321]

@Tahul; I actually like this take of making smaller improvements to exports! I think this might be a better approach. I can see what I can do by making small improvements first.