Chrome扩展Runtime error：需在清单文件中申请主机权限

Hey there! Let's work through this frustrating runtime error you're hitting. The message is pretty clear, but it's easy to mix up how permissions work in Chrome extensions—especially if you're using Manifest V3 (the current recommended version).

First up, a quick reality check: Chrome extensions require a manifest.json file as their core configuration, not a .js file like small.js. If you've been trying to define permissions in small.js, that's definitely why it's not working—all permission declarations need to live in manifest.json.

Step 1: Use the Correct Manifest Structure #

For Manifest V3 (the modern standard), you need two key sections in your manifest:

• The permissions array for API-specific permissions like webRequest
• A separate host_permissions array to specify which sites your extension can monitor with webRequest

Here's a complete, minimal example of what your manifest.json should look like:

{
  "manifest_version": 3,
  "name": "Your Minimal Debug Extension",
  "version": "1.0",
  "permissions": ["webRequest"],
  "host_permissions": ["<all_urls>"], // Monitor requests from every site
  "background": {
    "service_worker": "small.js" // Your logic goes here
  }
}

If you're still using Manifest V2 (though it's being phased out), host permissions go directly in the permissions array like this:

{
  "manifest_version": 2,
  "name": "Your Minimal Debug Extension",
  "version": "1.0",
  "permissions": ["webRequest", "<all_urls>"],
  "background": {
    "scripts": ["small.js"]
  }
}

Step 2: Double-Check Common Mistakes #

• Incorrect host permission format: Make sure you include the protocol (http:///https://) and proper wildcards. For example, "https://*.google.com/*" works, but "google.com" doesn't. Use <all_urls> if you need to monitor every site.
• Forgot to reload the extension: After editing manifest.json, go to chrome://extensions/, enable Developer Mode, and click the "Reload" button for your extension. Changes won't take effect until you do this!
• Mixing up V3 permission sections: Manifest V3 splits API permissions and host permissions into separate fields—putting host permissions in permissions instead of host_permissions will trigger the error you're seeing.

Step 3: Verify Your Listener Setup #

Make sure your small.js (background service worker/script) registers the listener correctly. For example, a basic log listener in Manifest V3 would look like:

chrome.webRequest.onBeforeRequest.addListener(
  (details) => {
    console.log("Request detected:", details.url);
  },
  { urls: ["<all_urls>"] }, // Match your host permissions here
  ["requestBody"] // Optional: Specify extra details you need
);

Note that the urls parameter in the listener should align with the host permissions you declared—it acts as an extra filter to narrow down which requests you monitor.

If you've tried all this and still run into issues, share your exact manifest.json (redact any sensitive info!) and I can help dig deeper.

内容的提问来源于stack exchange，提问作者razeal113