1 reply

Plasmo adds <all_urls> content script automatically, triggering host permissions

Title. I have a

contents

contents

directory with some content scripts, however the generated

manifest.json

manifest.json

also adds an additional content script:

    { "matches": ["<all_urls>"], "js": ["configs.9ddedc67.js"], "css": [] },

    { "matches": ["<all_urls>"], "js": ["configs.9ddedc67.js"], "css": [] },

This is triggering some warnings in the Chrome Web Store, asking to use the

activeTabs

activeTabs

permission or to add the specific domains to the rule.

Is there any way to force plasmo not to use this generic match? This didn't happen in older versions of Plasmo, but I'm unable to pinpoint exactly when this started to happen

�PD

🧩 Plasmo Developers•3y ago•

1 reply

Kurolox

Plasmo adds <all_urls> content script automatically, triggering host permissions

Title. I have a

contents

contents

directory with some content scripts, however the generated

manifest.json

manifest.json

also adds an additional content script:

    { "matches": ["<all_urls>"], "js": ["configs.9ddedc67.js"], "css": [] },

    { "matches": ["<all_urls>"], "js": ["configs.9ddedc67.js"], "css": [] },

This is triggering some warnings in the Chrome Web Store, asking to use the

activeTabs

activeTabs

Plasmo adds <all_urls> content script automatically, triggering host permissions

Similar Threads

Plasmo adds <all_urls> content script automatically, triggering host permissions

Similar Threads

Similar Threads

Similar Threads