Abre pronto
Building Chrome Extensions & Automations
Build a Chrome extension, from the manifest and content scripts to popup and options pages, with AI help.
5 capítulos · 22 lecciones
Recibe un correo cuando abra este curso
Lo que verás
Los capítulos
El plan del curso completo. Las lecciones se abren cuando abra el curso.
- 01How Chrome extensions are structured4 lecciones
- 02The manifest file and permissions4 lecciones
- 03Content scripts and changing web pages5 lecciones
- 04Building popup and options pages4 lecciones
- 05Using AI to build and debug extensions5 lecciones
Autoevaluación
¿Cuánto sabes ya?
5 preguntas rápidas. Elige una respuesta para ver por qué es correcta o no. No se guarda nada.
Pregunta 1 de 5
What replaced background pages in Manifest V3 for running background scripts?
Pregunta 2 de 5
A user installs an extension that saves their custom settings. They log into Chrome on a new laptop. What happens to those settings if the extension uses chrome.storage.sync?
Pregunta 3 de 5
What does the 'permissions' field in manifest.json do?
Pregunta 4 de 5
What does the 'activeTab' permission grant a Chrome extension?
Pregunta 5 de 5
Which file tells Chrome which components an extension has, what permissions they need, and where each one runs?
Términos clave
Palabras que verás en este curso
- Manifest V3
- The current version of Chrome's extension platform, which replaces background pages with service workers and limits remotely hosted code.
- Content script
- JavaScript an extension injects into matching web pages so it can read and change their content.
- Isolated world
- The separate JavaScript environment a content script runs in: it shares the page's DOM but not the page's own variables or functions.
- Service worker
- An extension's event-driven background script, which Chrome starts when an event needs handling and stops when it is idle.
- Host permissions
- The list of sites an extension asks to access, declared in the manifest and shown to users before they grant it.
- Match patterns
- URL patterns, such as https://example.com/*, that tell Chrome which pages a content script or permission applies to.
- Message passing
- How an extension's separate parts, such as content scripts and the service worker, send data to each other through Chrome's messaging APIs.
Ayúdanos a elegir
¿Qué curso debería abrir después?
Elige el que harías primero. Tu voto nos ayuda a decidir qué terminar después.