Please optimize the size of libs

Question

Accepted Answer

Hi Guys, I want to provide some updates on what we are thinking about the size optimization. We had a lot of discussion about it recently. While it’s not completely settled, I can share some ideas we have discussed.

At the root of the issue, firebase components expose the entire API surface in the component instance. For example, all Firebase Auth APIs hang off the firebase.auth() object. Bundler Hi Guys, I want to provide some updates on what we are thinking about the size optimization. We had a lot of discussion about it recently. While it’s not completely settled, I can share some ideas we have discussed. At the root of the issue, firebase components expose the entire API surface in the component instance. For example, all Firebase Auth APIs hang off the firebase.auth() object. Bundlers can’t tree shake them because they can’t be statically analyzed. To solve the problem, we need to export functions/classes as top level module exports to expose the APIs, so you can explicitly import what you need. For example: Just to clarify, this is just an example to illustrate the idea. The functions and their names are likely to be different in the final product. Besides the API changes, we also have a lot of work to do to refactor the implementation in order to decouple components and separate interconnected logics, otherwise you might run into a situation where you import just a few symbols but end up pulling in 80% of the codebase.

Please optimize the size of libs

Problem

1 Fix

Solution: Please optimize the size of libs

Hi Guys, I want to provide some updates on what we are thinking about the size o

At the root of the issue, firebase components expose the entire API surface in t

Just to clarify, this is just an example to illustrate the idea. The functions a

Besides the API changes, we also have a lot of work to do to refactor the implem

Validation

Verification Summary

Environment

Submitted by

Tags