Issue8141/support safari extensions #8175
Merged
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.
↪️ Pull Request
Adapt parcel js runtime to also support safari extensions.
Fixes #8141
💻 Examples
Any webextension build with parcel that uses getBundleUrl/getBaseUrl/getOrigin should now function.
🚨 Test instructions
This can only be tested by building a webextension and running it on safari. Note that to do this, you need to package the webextension as an OSX application using xcode.
In your extension, add an asset (let's say test.png). Then add code as follows to your content script:
this should add the test image to the document body when your extension is applied (i.e. the import resolves to a
safari-web-extension://
url at runtime).