-
Notifications
You must be signed in to change notification settings - Fork 930
FR: Module is huge, consider splitting it into many submodules (inside same repo) and lazy loading, bundle size #4862
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
Comments
Have you tried the v9 beta SDK, which is modular and tree shakable? See #4791 for our announcement |
duplicate of #332. |
Thanks, it decreased 56.6KB(!) but it's still 166.5 KB for handling login (in our case).. so better but not awesome |
@OZZlE what sorts of authentication are you using? My OAuth-only chunk is ±80 KB uncompressed (generated by Rollup with terser plugin) and ±22 KB brotli compressed. |
We use OAuth, magic email link and login with username/pw. We use webpack. Maybe not huge gzipped but still the biggest node module we have as far as I can see. we use now use:
|
From your
I think the small size reduction you're experiencing only comes from the complete Firebase rewrite. To get the benefits of tree shaking you have to use the "real" modular V9 version. |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
Steps to reproduce:
This is by far the biggest third party module we use and it's not easily replaceable by own code.
If it's because the module is very framework generic, perhaps making specific versions is better, like react-firebase, angular-firebase, vue-firebase etc.
The text was updated successfully, but these errors were encountered: