Skip to content
This repository has been archived by the owner on Aug 24, 2021. It is now read-only.

Using import() function for code splitting #42

Open
mikeal opened this issue Apr 2, 2019 · 1 comment
Open

Using import() function for code splitting #42

mikeal opened this issue Apr 2, 2019 · 1 comment

Comments

@mikeal
Copy link
Contributor

mikeal commented Apr 2, 2019

In order to reduce the impact not the default bundle size, each method should use the import() function to get the crypto library it needs. Since all the methods are already async this wouldn’t require an API change and would result in some very code splitting for the consumers.

@mikeal
Copy link
Contributor Author

mikeal commented Apr 2, 2019

Just to be clear, until esm comes out from under a flag this would be very annoying to implement. Not sure what the timeline is for that, but I think it’s actually pretty aggressive.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant