Service workers in Svelte - Mini Project: Build & Apply

Registering a Service Worker in Svelte

📖 Scenario: You are building a simple Svelte app that needs to work offline. To do this, you will register a service worker that can cache files and serve them when the network is unavailable.

🎯 Goal: Create a Svelte component that registers a service worker located at /service-worker.js when the app loads.

📋 What You'll Learn

Create a Svelte component with a script block

Check if the browser supports service workers

Register the service worker from /service-worker.js

Handle successful registration and errors with console messages

💡 Why This Matters

🌍 Real World

Service workers help web apps work offline and load faster by caching resources. This is useful for apps that need to work without internet or improve performance.

💼 Career

Knowing how to register and use service workers is important for frontend developers building progressive web apps (PWAs) and improving user experience.

1

Create the Svelte component skeleton

Create a Svelte component with an empty <script> block and a simple <main> section containing the text Service Worker Demo.

Svelte

// Your code here



  Service Worker Demo

Hint

Start by writing the basic Svelte component structure with a <script> block and a <main> tag.

2

Add a variable to check service worker support

Inside the <script> block, create a constant called supportsSW that checks if 'serviceWorker' is a property of navigator.

Svelte

// Create a constant called supportsSW to check if 'serviceWorker' is in navigator
// Your code here



  Service Worker Demo

Hint

Use const supportsSW = 'serviceWorker' in navigator; to check support.

3

Register the service worker on component mount

Inside the <script> block, import onMount from 'svelte'. Use onMount to run a function that registers the service worker at /service-worker.js only if supportsSW is true. Log 'Service Worker registered' on success and 'Service Worker registration failed' on error.

Svelte

const supportsSW = 'serviceWorker' in navigator;

// Import onMount from 'svelte'
// Use onMount to register the service worker if supportsSW is true
// Your code here



  Service Worker Demo

Hint

Use onMount to run code after the component loads. Register the service worker only if supported.

4

Add a simple message in the UI about service worker status

Below the Service Worker Demo text inside the <main> tag, add a paragraph that says Service Worker is supported if supportsSW is true, otherwise Service Worker is not supported. Use Svelte's curly braces and ternary operator.

Svelte

import { onMount } from 'svelte';

const supportsSW = 'serviceWorker' in navigator;

onMount(() => {
  if (supportsSW) {
    navigator.serviceWorker.register('/service-worker.js')
      .then(() => {
        console.log('Service Worker registered');
      })
      .catch(() => {
        console.log('Service Worker registration failed');
      });
  }
});



  Service Worker Demo
  
  

Hint

Use Svelte's curly braces with a ternary operator inside the <p> tag to show the message.

Practice

1. What is the main purpose of a service worker in a Svelte app?

easy

A. To enable offline support and faster loading by caching files

B. To handle user authentication and sessions

C. To manage component state and props

D. To style components dynamically

Solution

1. Step 1: Understand service worker role

   Service workers run in the background and cache files to allow offline use and faster loading.

2. Step 2: Differentiate from other app features

   User authentication, state management, and styling are handled by other parts of the app, not service workers.

3. Final Answer:

   To enable offline support and faster loading by caching files -> Option A

4. Quick Check:

   Service workers = offline support and caching [OK]

Hint: Service workers cache files for offline use [OK]

Common Mistakes:

• Confusing service workers with authentication
• Thinking service workers manage UI state
• Assuming service workers handle styling

2. Which is the correct way to register a service worker in a Svelte app?

easy

A. navigator.serviceWorker.register('/service-worker.js')

B. serviceWorker.register('/service-worker.js')

C. navigator.registerServiceWorker('/service-worker.js')

D. register.serviceWorker('/service-worker.js')

Solution

1. Step 1: Recall the correct API

   The standard API to register a service worker is navigator.serviceWorker.register().

2. Step 2: Check method and object names

   Only navigator.serviceWorker.register('/service-worker.js') uses the correct object (navigator.serviceWorker) and method (register).

3. Final Answer:

   navigator.serviceWorker.register('/service-worker.js') -> Option A

4. Quick Check:

   Use navigator.serviceWorker.register() [OK]

Hint: Use navigator.serviceWorker.register() to register [OK]

Common Mistakes:

• Using wrong method names like registerServiceWorker
• Calling register on wrong objects
• Missing navigator or serviceWorker in the call

3. What will happen if you try to register a service worker in a browser that does not support it, using this code?

if ('serviceWorker' in navigator) {
  navigator.serviceWorker.register('/sw.js')
    .then(() => console.log('Registered'))
    .catch(err => console.error('Failed', err));
} else {
  console.log('No support');
}

medium

A. Registers the service worker anyway

B. Throws an error because serviceWorker is undefined

C. Logs 'No support' and does not attempt registration

D. Logs 'Registered' even if unsupported

Solution

1. Step 1: Check the feature detection condition

   The code checks if 'serviceWorker' exists in navigator before registering.

2. Step 2: Understand behavior if unsupported

   If unsupported, the else block runs, logging 'No support' and skipping registration.

3. Final Answer:

   Logs 'No support' and does not attempt registration -> Option C

4. Quick Check:

   Feature check prevents errors = logs 'No support' [OK]

Hint: Check 'serviceWorker' in navigator before registering [OK]

Common Mistakes:

• Assuming registration runs without support
• Expecting errors instead of safe fallback
• Confusing logs from then/catch with else block

4. Identify the error in this service worker registration code snippet:

if (navigator.serviceWorker) {
  navigator.serviceWorker.register('/sw.js')
    .then(() => console.log('Registered'))
    .catch(err => console.error('Failed', err));
}

medium

A. The catch block is incorrectly placed

B. register() method is missing parentheses

C. The path '/sw.js' must be absolute URL

D. Should check 'serviceWorker' in navigator, not just navigator.serviceWorker

Solution

1. Step 1: Analyze the feature detection condition

   The code checks if navigator.serviceWorker exists directly, which can cause errors if undefined.

2. Step 2: Correct way to check support

   The proper check is 'serviceWorker' in navigator to safely detect support.

3. Final Answer:

   Should check 'serviceWorker' in navigator, not just navigator.serviceWorker -> Option D

4. Quick Check:

   Use 'serviceWorker' in navigator for support check [OK]

Hint: Use 'serviceWorker' in navigator, not navigator.serviceWorker alone [OK]

Common Mistakes:

• Checking navigator.serviceWorker directly without 'in'
• Misplacing catch block
• Thinking path must be full URL

5. You want your Svelte app to update the cached files when a new service worker version is available. Which approach correctly handles this scenario?

hard

A. Reload the page immediately after registering the service worker

B. Listen for 'updatefound' event on registration and call skipWaiting() in the new worker

C. Unregister the old service worker manually before registering a new one

D. Do nothing; service workers update automatically without extra code

Solution

1. Step 1: Understand service worker update process

   When a new service worker is found, the 'updatefound' event fires on the registration.

2. Step 2: Use skipWaiting() to activate new worker immediately

   Calling skipWaiting() on the new worker lets it take control without waiting for old pages to close.

3. Step 3: Evaluate other options

   Reloading immediately or unregistering manually is not recommended; automatic updates require event handling.

4. Final Answer:

   Listen for 'updatefound' event on registration and call skipWaiting() in the new worker -> Option B

5. Quick Check:

   Use 'updatefound' + skipWaiting() to update cache [OK]

Hint: Use 'updatefound' event and skipWaiting() to update cache [OK]

Common Mistakes:

• Ignoring updatefound event
• Reloading page too early
• Unregistering service workers unnecessarily
• Assuming automatic update without code