백그라운드 서비스 워커

Welcome to the core of your Manifest V3 extension: Background Service Workers! Think of them as the silent brain of your extension.

They're responsible for listening to browser events, managing persistent logic, and ensuring your extension runs efficiently without constantly consuming resources.

In Manifest V2, extensions often used 'persistent background pages' that ran constantly. Manifest V3 introduced service workers as a more modern, energy-efficient alternative.

• Event-Driven: They only wake up when an event occurs.
• Temporary: They go idle and terminate when not needed.
• Energy-Saving: This 'sleep-wake' cycle saves battery and memory.

To use a service worker, you must declare it in your manifest.json file. This tells the browser which JavaScript file acts as your background script.

It's specified under the 'background' key, pointing to your service worker script.

Unlike a traditional always-on program, a service worker has a dynamic lifecycle:

• It activates when an event it's listening for occurs.
• It runs its associated tasks.
• After a period of inactivity (usually a few seconds), it goes idle and eventually terminates.

It will reactivate the next time an event triggers it.

Service workers primarily function by listening for browser events using the chrome API. When an event fires, your worker code springs into action!

Common events include:

• chrome.runtime.onInstalled: When the extension is installed or updated.
• chrome.action.onClicked: When the extension's toolbar icon is clicked.

Let's write a simple service worker that logs a message when your extension is first installed or updated. This is a great place for one-time setup tasks.

Create a file named service-worker.js:

Another common event is when the user clicks your extension's icon in the browser toolbar. You can make your service worker respond to this interaction, for example, by opening a new tab.

To see your console.log messages and debug your service worker, you'll use the browser's Developer Tools.

In Chrome/Edge, go to chrome://extensions, enable 'Developer mode', find your extension, and click the 'service worker' link to open its dedicated DevTools window.

What is a key characteristic of Manifest V3 background service workers compared to Manifest V2 background pages?

Great job! You've learned about the fundamental role of Background Service Workers in Manifest V3 extensions:

• They are the event-driven 'brains' of your extension.
• They are declared in manifest.json.
• They have a temporary lifecycle, waking for events and then terminating.
• You use event listeners (e.g., chrome.runtime.onInstalled, chrome.action.onClicked) to make them react to browser events.

Next, we'll dive into how permissions control what your extension can do!