Bundle preloading in Firebase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to preload a Firebase bundle using the SDK.

Firebase

const bundleTask = firebase.firestore().bundle('[1]');

Drag options to blanks, or click blank then click option'

Apreload

BloadBundle

CbundleName

DmyBundle

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names instead of the bundle name string.

Passing an undefined variable instead of a string.

The bundle name is passed as a string to the bundle() method to start preloading.

2fill in blank

medium

Complete the code to listen for progress updates while loading a Firebase bundle.

Firebase

bundleTask.onProgress(([1]) => { console.log('Progress:', [1]); });

Drag options to blanks, or click blank then click option'

Aprogress

Bsnapshot

Cevent

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic names like 'event' or 'status' instead of 'snapshot'.

Not matching the parameter name inside the callback.

The onProgress callback receives a snapshot object with progress details.

3fill in blank

hard

Fix the error in the code to correctly load a Firebase bundle from a Uint8Array.

Firebase

firebase.firestore().loadBundle([1]).then(() => console.log('Bundle loaded'));

Drag options to blanks, or click blank then click option'

AbundleBytes

BbundleData

CbundleName

DbundleUint8Array

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the bundle name string instead of the bytes.

Using a variable name that does not hold the Uint8Array.

The loadBundle method expects a Uint8Array containing the bundle bytes, commonly named bundleBytes.

4fill in blank

hard

Fill both blanks to create a listener that handles bundle loading progress and completion.

Firebase

bundleTask.onProgress(([1]) => {
  if ([2].taskState === 'Success') {
    console.log('Bundle loaded successfully');
  }
});

Drag options to blanks, or click blank then click option'

AtaskState

Bsnapshot

Cprogress

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names for the parameter and inside the function.

Checking a property on an undefined variable.

The callback receives a snapshot object, which has a taskState property to check if loading succeeded.

5fill in blank

hard

Fill all three blanks to preload a bundle, listen for progress, and handle completion.

Firebase

const bundleTask = firebase.firestore().bundle('[1]');
bundleTask.onProgress(([2]) => {
  console.log('Progress:', [2].bytesLoaded);
  if ([2].taskState === '[3]') {
    console.log('Bundle fully loaded');
  }
});

Drag options to blanks, or click blank then click option'

AmyBundle

Bsnapshot

CSuccess

Dprogress

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up parameter names and property names.

Using incorrect strings for task state.

Use the bundle name string for bundle(), snapshot as the progress parameter, and check if taskState equals 'Success' to confirm loading.

Practice

1. What is the main purpose of bundle preloading in Firebase Hosting?

easy

A. To download important code bundles early for faster app loading

B. To increase the size of the app bundle for better caching

C. To delay loading of all code until user interaction

D. To disable code splitting in the app

Solution

1. Step 1: Understand bundle preloading concept

   Bundle preloading downloads code bundles early before they are needed to speed up app loading.

2. Step 2: Identify the main benefit

   This early download improves user experience by reducing wait time when features are accessed.

3. Final Answer:

   To download important code bundles early for faster app loading -> Option A

4. Quick Check:

   Bundle preloading = early download for speed [OK]

Hint: Preloading means downloading code before it's needed [OK]

Common Mistakes:

• Thinking preloading delays code loading
• Confusing preloading with disabling code splitting
• Assuming preloading increases bundle size

2. Which is the correct way to configure bundle preloading in firebase.json under hosting?

easy

A. "preloadBundles": {"bundle1.js": true, "bundle2.js": true}

B. "preloadBundles": "bundle1.js, bundle2.js"

C. "preloadBundles": ["bundle1.js", "bundle2.js"]

D. "preloadBundles": [bundle1.js, bundle2.js]

Solution

1. Step 1: Review JSON array syntax for preloadBundles

   The correct syntax uses an array of strings listing bundle filenames.

2. Step 2: Identify correct JSON format

   "preloadBundles": ["bundle1.js", "bundle2.js"] correctly uses an array of quoted strings, which is valid JSON.

3. Final Answer:

   "preloadBundles": ["bundle1.js", "bundle2.js"] -> Option C

4. Quick Check:

   Preload bundles = array of strings [OK]

Hint: Use array of quoted strings for bundle names in JSON [OK]

Common Mistakes:

• Using unquoted bundle names causing syntax errors
• Passing bundles as a single string instead of array
• Using object instead of array for bundles

3. Given this firebase.json snippet:

{
  "hosting": {
    "preloadBundles": ["main.js", "feature.js"]
  }
}

What happens when a user visits the site?

medium

A. Only 'main.js' loads immediately; 'feature.js' loads on demand

B. Both 'main.js' and 'feature.js' start downloading early to speed up usage

C. Neither bundle loads until user clicks a feature

D. 'feature.js' loads first, then 'main.js' after

Solution

1. Step 1: Understand preloadBundles effect

   Bundles listed in preloadBundles start downloading early when the site loads.

2. Step 2: Apply to given bundles

   Both 'main.js' and 'feature.js' will preload to improve speed when features are used.

3. Final Answer:

   Both 'main.js' and 'feature.js' start downloading early to speed up usage -> Option B

4. Quick Check:

   Preload means early download of all listed bundles [OK]

Hint: Preload bundles download early, not on demand [OK]

Common Mistakes:

• Assuming only main bundle preloads
• Thinking bundles load only after user action
• Believing preload order is reversed

4. You configured preloadBundles in firebase.json as:

{
  "hosting": {
    "preloadBundles": ["app.js", app2.js"]
  }
}

What is the problem with this configuration?

medium

A. Bundle names must include full URL paths

B. Using preloadBundles inside hosting is not supported

C. Bundles must be objects, not strings

D. Missing quotes around 'app2.js' causes JSON syntax error

Solution

1. Step 1: Check JSON syntax for bundle names

   All bundle names must be strings enclosed in double quotes.

2. Step 2: Identify error in given config

   'app2.js' is missing quotes, causing invalid JSON syntax.

3. Final Answer:

   Missing quotes around 'app2.js' causes JSON syntax error -> Option D

4. Quick Check:

   JSON strings need quotes [OK]

Hint: Always quote bundle names as strings in JSON [OK]

Common Mistakes:

• Forgetting quotes around bundle names
• Placing preloadBundles outside hosting
• Using objects instead of string arrays

5. You want to preload bundles only for features users often visit first, but not preload large rarely used bundles. How should you configure firebase.json to optimize loading?

hard

A. List only frequently used bundles in preloadBundles to download early

B. Preload all bundles regardless of usage to avoid delays

C. Do not use preloadBundles; load all bundles on demand

D. Preload only the largest bundles to improve caching

Solution

1. Step 1: Understand preload strategy

   Preloading bundles that users access often improves perceived speed without wasting bandwidth.

2. Step 2: Apply selective preloading

   Only list frequently used bundles in preloadBundles to optimize loading and avoid unnecessary downloads.

3. Final Answer:

   List only frequently used bundles in preloadBundles to download early -> Option A

4. Quick Check:

   Preload important bundles only for best performance [OK]

Hint: Preload only bundles users need early to save bandwidth [OK]

Common Mistakes:

• Preloading all bundles causing slow initial load
• Ignoring usage patterns when preloading
• Preloading large unused bundles wasting resources