Bundle preloading in Firebase - Commands & Configuration

Introduction

Bundle preloading helps your web app load faster by telling the browser to start downloading important files early. This reduces waiting time when users navigate your app.

When you want your app's main JavaScript files to load quickly on first visit.

When you have large code bundles that delay page rendering.

When you want to improve user experience by reducing loading spinners.

When you want to optimize performance on slow internet connections.

When you want to prepare the browser to fetch code chunks before they are needed.

Config File - firebase.json

firebase.json

{
  "hosting": {
    "public": "public",
    "headers": [
      {
        "source": "/static/js/main.js",
        "headers": [
          {
            "key": "Link",
            "value": "</static/js/main.js>; rel=preload; as=script"
          }
        ]
      }
    ]
  }
}

This configuration tells Firebase Hosting to add a Link header for the /static/js/main.js file.

The header uses rel=preload to tell browsers to start loading main.js early as a script.

This helps the browser fetch important code bundles faster, improving app load speed.

Commands

Deploys your Firebase Hosting site with the updated preload headers so browsers can start loading bundles early.

Terminal

firebase deploy --only hosting

Expected Output

=== Deploying to 'your-project-id'...



i  deploying hosting

i  hosting[your-project-id]: beginning deploy...

✔  hosting[your-project-id]: deployed successfully



✔  Deploy complete!

→

--only hosting - Deploy only the hosting part without affecting other Firebase services

Checks the HTTP headers of the main.js file to verify the preload header is present.

Terminal

curl -I https://your-project-id.web.app/static/js/main.js

Expected Output

HTTP/2 200 

content-type: application/javascript

link: </static/js/main.js>; rel=preload; as=script

cache-control: public, max-age=31536000

...

Key Concept

If you remember nothing else from this pattern, remember: preload headers tell browsers to fetch important files early, speeding up your app load.

Common Mistakes

Not specifying the correct file path in the preload header source.

The browser won't preload the intended files if the path doesn't match the actual file location.

Ensure the source path in firebase.json matches the exact location of your JavaScript bundles.

Forgetting to redeploy Firebase Hosting after changing the preload configuration.

Changes won't take effect until you deploy, so preload headers won't be sent to browsers.

Always run 'firebase deploy --only hosting' after updating preload settings.

Summary

Add preload headers in firebase.json to tell browsers which bundles to load early.

Deploy the hosting configuration with 'firebase deploy --only hosting'.

Verify headers with curl to ensure preload is active.

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