You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If targeting a different browser, it can be useful to not include specific entrypoints.
JS
exportdefaultdefineContentScript({exclude: ["safari"],// Excludes content script from safari});
exportdefaultdefineBackground({include: ["firefox"],// Only includes a background script for Firefox});
// For unlisted files, we probably need to add a default export as well.exportdefaultdefineUnlistedScript({exclude: ["chrome","safari"],main(){// ...}});
HTML
<!doctype html><htmllang="en"><head><!-- Exclude this HTML page from Firefox and Safari --><metaname="manifest.exclude" content="['firefox', 'safari']" />
</head><body><!-- ... --></body></html>
CSS
Then for CSS... I don't know what to do. Ideally, you would use a content script and not have a CSS file directly, but that's not always best all the time.
Is your feature request related to a bug?
N/A
What are the alternatives?
Using transformManifest to remove the entrypoint and delete built files.
The text was updated successfully, but these errors were encountered:
Feature Request
If targeting a different browser, it can be useful to not include specific entrypoints.
JS
HTML
CSS
Then for CSS... I don't know what to do. Ideally, you would use a content script and not have a CSS file directly, but that's not always best all the time.
Is your feature request related to a bug?
N/A
What are the alternatives?
Using
transformManifest
to remove the entrypoint and delete built files.The text was updated successfully, but these errors were encountered: