تصحيح أخطاء مكوّنات الإضافات

Debugging is the process of finding and fixing errors in your code. For browser extensions, it's crucial to understand how to debug different parts, like background scripts, popups, and content scripts.

Since extensions run in unique environments, the standard web debugging techniques need a slight adjustment. We'll explore how to use Chrome and Edge Developer Tools effectively.

To debug your extension, you'll primarily use the browser's Developer Tools (DevTools). The way you open them depends on which part of your extension you want to inspect.

• Go to chrome://extensions (or edge://extensions).
• Ensure "Developer mode" is enabled.
• Find your extension and click "Inspect views" for background scripts or specific popups.

Background service workers are event-driven scripts that run in the background. They don't have a visible UI, so their DevTools instance is separate.

• On the chrome://extensions page, under your extension, look for the "Inspect views" link, specifically for "service worker" or "background page."
• Clicking this link opens a dedicated DevTools window where you can see console logs, set breakpoints, and inspect variables for your background script.

Let's see a simple background script in action and how to debug it. This script just logs a message when the extension starts up.

After loading this extension, open its background service worker DevTools from chrome://extensions. You'll see "Background script loaded!" and other messages in the console.

Popups and options pages are essentially regular HTML pages with their own JavaScript and CSS. This means you debug them just like any other webpage.

• For a popup: Right-click anywhere on the popup when it's open and select "Inspect" or "Inspect Element."
• For an options page: Open the options page (usually from the extension management page or a direct link) and then right-click and "Inspect."

This opens a standard DevTools window for that specific UI component.

Here's the JavaScript for a basic popup. When you open the popup, this script runs and logs a message. You can inspect this popup's elements and console output directly.

To debug: Click your extension icon to open the popup, then right-click on the popup and choose "Inspect". Check the Console and Elements tabs.

Content scripts run in the context of a web page. This means they can interact with the page's DOM, but also that their DevTools are linked to the page itself.

• Open the web page where your content script is injected.
• Open the page's DevTools (usually F12 or right-click -> "Inspect").
• In the "Sources" tab, you'll often find your content script under a special chrome-extension:// or moz-extension:// URL.

Be aware that content scripts run in an isolated world, meaning they don't directly share global variables with the page's own JavaScript.

This content script changes the background color of the body and logs a message when injected into a web page. Load this as part of an extension configured to run on a specific site (e.g., *://*/*).

To debug: Navigate to a web page where your script is injected, open the page's DevTools, and check the Console. You can also find the script in the Sources tab.

Beyond just seeing errors, DevTools offer powerful features:

• Breakpoints: Pause execution at specific lines of code to inspect variables and step through your program. Click on the line number in the "Sources" tab to set one.
• Console API: Use console.log(), console.warn(), console.error() for quick output. Also, console.dir() for object inspection.
• Network Tab: Monitor all network requests made by your extension or the page it interacts with.
• Elements Tab: Inspect and modify the HTML and CSS of your popup, options page, or the web page (for content scripts).

Here are a few more tips for effective debugging:

• Source Maps: If you're using a build tool (like Webpack or Rollup), ensure source maps are generated for easier debugging of original source code.
• debugger; statement: Add debugger; directly in your JavaScript code to programmatically trigger a breakpoint when DevTools are open.
• Preserve Log: In the DevTools console settings, enable "Preserve log" to prevent the console from clearing on navigation or service worker restarts.
• Conditional Breakpoints: Right-click a breakpoint to add conditions, so it only pauses when a specific expression is true.

You've learned how to access DevTools for different parts of your extension. Let's test your understanding.

Great job! You've learned the essentials of debugging browser extensions.

• Background service workers are debugged via their dedicated "Inspect views" link on chrome://extensions.
• Popups and options pages are debugged like regular web pages: right-click and "Inspect."
• Content scripts are debugged by opening DevTools for the web page they are injected into.
• Utilize breakpoints, console logging, and other DevTools features to efficiently find and fix issues in your extension.

Mastering these techniques is key to building robust and error-free extensions!