firebase-js-sdk

Firebase is Google’s official JavaScript SDK for building apps on top of Firebase’s managed backend services. Published from the firebase-js-sdk monorepo, the firebase npm package bundles modular client libraries for Authentication, Cloud Firestore, the Realtime Database, Cloud Storage, Cloud Functions, Cloud Messaging, Performance Monitoring, Remote Config, App Check, and Google Analytics behind a single install.

Since version 9, the SDK exposes a fully modular, tree-shakeable API - each service is imported as named functions operating on an app or service instance rather than through chained namespaced objects, so bundlers can eliminate unused code. It targets browsers, mobile web (Ionic, Cordova, React Native), and server-side Node.js, with a legacy compat layer retained for apps still migrating off the pre-v9 namespaced API.

What You Get

• Modular imports for Authentication, Firestore, Realtime Database, Storage, Functions, Messaging, Performance, Remote Config, App Check, and Analytics under one package
• A shared FirebaseApp / component-container runtime that lazily wires each service to your project’s config
• Tree-shakeable ESM builds alongside CommonJS builds for Node.js, plus a compat layer for pre-v9 namespaced code
• TypeScript types generated via API Extractor for every public surface
• Cross-environment support: browser, mobile web (Cordova, web-extension), and privileged Node.js contexts via FirebaseServerApp

Common Use Cases

• Adding email/password, phone, or OAuth authentication to a web or mobile-web app
• Storing and querying app data in real time with Cloud Firestore or the Realtime Database
• Uploading and serving user-generated files through Cloud Storage
• Triggering backend logic with Cloud Functions and tracking usage with Analytics or Performance Monitoring

Under The Hood

Architecture The SDK is a yarn/lerna/nx-managed monorepo of ~50 independently versioned @firebase/* packages (auth, firestore, storage, functions, messaging, performance, remote-config, app-check, analytics, ai, data-connect), unified by the packages/firebase umbrella package that re-exports each one behind its own exports map entry (e.g. firebase/auth, firebase/firestore). Each service registers itself as a Component into a ComponentContainer owned by a FirebaseAppImpl instance (see packages/app/src/firebaseApp.ts and registerCoreComponents.ts) - services are resolved lazily through this container rather than imported and wired directly, which is what lets unrelated services stay decoupled while sharing one app instance. A parallel FirebaseServerApp type in the same package supports privileged Node.js contexts that need to act on behalf of an authenticated user, distinct from the client-only FirebaseApp.

Tech Stack Everything is TypeScript, compiled and bundled per-package with Rollup into ESM, CJS, and browser-ESM variants declared through package.json exports conditions. The monorepo itself is orchestrated with Yarn workspaces, Lerna, and Nx; api-extractor generates and enforces public .d.ts surfaces per package (api-report script), and patch-package applies local dependency patches on install. The umbrella firebase package has no runtime logic of its own - it is purely a re-export/build surface over the individual @firebase/* packages, which in turn depend on shared internal packages like @firebase/component, @firebase/util, and @firebase/logger.

Code Quality Testing is extensive and dual-target: each package runs a Karma-driven browser suite (test:browser) and a Mocha/ts-node/nyc Node suite (test:node) against files matched by *.test.ts, with coverage collected via nyc/lcov and merged across packages in CI. ESLint (via a shared .eslintrc.js) and Prettier enforce style, and a large .github/workflows set (test-all, lint, format, check-changeset, per-service changed-file test workflows, e2e-test) gates every change. Errors are handled through a typed ErrorFactory/ErrorMap pattern (see packages/app/src/errors.ts) rather than ad-hoc throws, giving consumers stable, parameterized error codes.

API Design The public API is deliberately function-first and tree-shakeable: initializeApp() returns an app, and each service is obtained via a getX(app) call before invoking further functions on it, replacing the pre-v9 namespaced firebase.auth()-style chains (still available via the compat sub-path for migrating apps). This keeps per-service boilerplate low and lets bundlers eliminate unused services, though the up-front firebaseConfig object and per-service getX(app) call are still required scaffolding for every project.