后台服务工作线程
学习后台服务工作线程如何在扩展中管理事件、持久化逻辑与生命周期
后台服务工作线程 是 CoddyKit 上的免费 Browser Extensions Development (Chrome & Edge) 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Browser Extensions Development (Chrome & Edge) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Browser Extensions Development (Chrome & Edge) 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Extension's Brain: Service Workers
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.
MV3: Why Service Workers?
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.
Declaring Your Service Worker
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.
{
"manifest_version": 3,
"name": "My Service Worker Extension",
"version": "1.0",
"background": {
"service_worker": "service-worker.js"
},
"action": {
"default_popup": "popup.html"
}
}Service Worker Lifecycle
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.
Listening for Events
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.
Event: On Extension Installed
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:
// service-worker.js
chrome.runtime.onInstalled.addListener(() => {
console.log('CoddyKit Extension installed or updated!');
// You could set default preferences here
chrome.storage.sync.set({ 'theme': 'light' });
});Event: On Extension Icon Click
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.
// service-worker.js
chrome.action.onClicked.addListener((tab) => {
console.log('Extension icon clicked! Current tab ID:', tab.id);
// Open a new tab to a specific URL
chrome.tabs.create({ url: 'https://www.google.com/search?q=CoddyKit' });
});Debugging Your Service Worker
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.
Quick Check: Service Worker Role
What is a key characteristic of Manifest V3 background service workers compared to Manifest V2 background pages?
Recap: Background Service Workers
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!
常见问题解答
「后台服务工作线程」课时是免费的吗？
是的 — 「后台服务工作线程」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Browser Extensions Development (Chrome & Edge) 课程的其余内容，请升级到 CoddyKit PRO。 Browser Extensions Development (Chrome & Edge) 课程共包含 4 节课。
「后台服务工作线程」这节课中我会学到什么？
学习后台服务工作线程如何在扩展中管理事件、持久化逻辑与生命周期 你通过在浏览器中直接运行的动手代码来练习 Browser Extensions Development (Chrome & Edge)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Browser Extensions Development (Chrome & Edge) 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Browser Extensions Development (Chrome & Edge) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。
「后台服务工作线程」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Browser Extensions Development (Chrome & Edge) 课中编写并运行代码吗？
能。每节 Browser Extensions Development (Chrome & Edge) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。