Skip to content
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

Investigate tree-shaking of library #13

Open
CDDelta opened this issue Sep 5, 2020 · 0 comments
Open

Investigate tree-shaking of library #13

CDDelta opened this issue Sep 5, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@CDDelta
Copy link
Owner

CDDelta commented Sep 5, 2020

The way the library currently namespaces actions likely prevents tree-shaking of unused code. We should investigate how to make the library more tree-shakeable.

Firebase does this by having each of its components as separate packages and a singleton which all the components retrieve config from. If we go down this route it would mean that apps that use this library can only have a single config at once.

@CDDelta CDDelta added the enhancement New feature or request label Sep 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant