Modular SDK (v9+) tree-shaking in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is tree-shaking in the context of Firebase Modular SDK (v9+)?

Tree-shaking is a process that removes unused code from the final app bundle, making the app smaller and faster by only including the Firebase features you actually use.

beginner

How does the Modular SDK (v9+) help with tree-shaking compared to older Firebase SDK versions?

The Modular SDK uses individual function imports instead of a big namespace, so bundlers can detect and remove unused parts easily, unlike older SDKs that imported everything at once.

beginner

Why should you import only the Firebase functions you need in Modular SDK (v9+)?

Importing only needed functions helps tree-shaking work well, reducing app size and improving load speed by excluding unused Firebase code.

beginner

Example: How to import Firestore's getDoc function in Modular SDK (v9+) for tree-shaking?

Use: import { getDoc } from 'firebase/firestore'; This imports only the getDoc function, allowing unused Firestore code to be removed.

beginner

What is the main benefit of tree-shaking for mobile users of Firebase apps?

Smaller app size means faster downloads, quicker startup, and less data usage, which improves user experience especially on slow or limited networks.

What does tree-shaking do in Firebase Modular SDK (v9+)?

A Removes unused Firebase code from the app bundle

B Adds extra Firebase features automatically

C Encrypts Firebase data

D Updates Firebase SDK to the latest version

Tree-shaking removes unused code to reduce app size and improve performance.

Which import style helps tree-shaking in Firebase Modular SDK (v9+)?

A Importing only the specific functions you use

B Importing Firebase using require()

C Importing Firebase via CDN script tag

D Importing the whole Firebase namespace

Importing only specific functions allows bundlers to remove unused code.

Why is tree-shaking important for Firebase apps on mobile devices?

A It increases app size

B It slows down app startup

C It disables Firebase features

D It reduces app size and speeds up loading

Tree-shaking reduces app size, making apps load faster and use less data.

Which Firebase SDK version introduced the Modular SDK with tree-shaking support?

A v7

B v8

C v9

D v10

Firebase Modular SDK with tree-shaking was introduced in version 9.

What happens if you import the entire Firebase SDK instead of specific functions in Modular SDK?

A Tree-shaking removes all unused code anyway

B App bundle size increases because unused code stays

C App runs faster

D Firebase features stop working

Importing the whole SDK prevents tree-shaking from removing unused code, increasing bundle size.

Explain how tree-shaking works in Firebase Modular SDK (v9+) and why it matters.

Think about how only the code you use stays in your app.

Describe best practices for importing Firebase features to maximize tree-shaking benefits.

Focus on how to write your import statements.