You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: