New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subexports and treeshaking #128
Comments
@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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?)The text was updated successfully, but these errors were encountered: