Browser Extensions Development (Chrome & Edge) · Pelajaran

Pekerja Layanan Latar Belakang

Pelajari cara pekerja layanan latar belakang mengelola peristiwa, logika yang persisten, dan siklus hidup dalam ekstensi Anda.

Pekerja Layanan Latar Belakang adalah pelajaran Browser Extensions Development (Chrome & Edge) gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Browser Extensions Development (Chrome & Edge), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Browser Extensions Development (Chrome & Edge) mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

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!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Pekerja Layanan Latar Belakang” gratis?

Ya — teks lengkap “Pekerja Layanan Latar Belakang” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Browser Extensions Development (Chrome & Edge), upgrade ke CoddyKit PRO. Kursus Browser Extensions Development (Chrome & Edge) mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Pekerja Layanan Latar Belakang”?

Pelajari cara pekerja layanan latar belakang mengelola peristiwa, logika yang persisten, dan siklus hidup dalam ekstensi Anda. Kamu berlatih Browser Extensions Development (Chrome & Edge) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Browser Extensions Development (Chrome & Edge)?

Tidak diperlukan pengalaman sebelumnya. Browser Extensions Development (Chrome & Edge) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Pekerja Layanan Latar Belakang” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Browser Extensions Development (Chrome & Edge) ini?

Ya. Setiap pelajaran Browser Extensions Development (Chrome & Edge) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

← Kembali ke Browser Extensions Development (Chrome & Edge)