feat!: Add support for "main world" content scripts #284
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This closes #282.
Now, when a content script is built, it will use different virtual entrypoints depending on the
world
option. If it'sundefined
or"ISOLATED"
, it will continue working as-is. If it's"MAIN"
, then a separate entrypoint is imported that doesn't load thewebextension-polyfill
, since main world content scripts run in a sandboxed environment without access to the extension APIs.BREAKING CHANGE: In order to isolate the
webextension-polyfill
from being imported automatically fromwxt/client
when importingdefineContentScript
,defineContentScript
anddefineBackgroundScript
have been moved fromwxt/client
towxt/sandbox
.