Nobodys wants to rescript code in the interest of rewriting code. A constant proficiency is one of the main reasons for top decision features when you opt to invest in a library. We always take that seriously. Allegiance to a constant API has been an in-progress balance of adopting new techniques for better performance and maintaining existing patterns and developer know-how. But as you know Firebase brings down more features, the SDK itself becomes vast. To fit the modern web and reduce the size, and decides to make changes that need a break in our longstanding API.
In 2012 the original firebase was authored and was the only way to contend a module system in the browser. A common way to attach an “a namespace” for the library on the window, therefore window. firebase.
The benefit , which can put an end to unused code from applications and libraries we import. What is Firebase? How does it work? Well, It is changing to follow up a modular sample that gives tree shaking and hence do performance better for your sites. This modular approach eliminates the side effects isolates and imports factors as single functions.
Services & Namespaces
Firebase has known as a namespace that contains the firestore service. services like Authentication, real-time database, remote config, and messaging is also live on the namespace. Every service is a namespace as well. It has a set of methods attached like the collection.
New modular library
Upgrade one library at one time