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.
Description
I don't have enough experience in contributing and pull-requests, so I would be thankful for help.
It adds possibility to build Safari Web Extension that works similar to Chrome extension #1139
Tested with Safari Technology Preview (Safari 16.0) on Mac OS 12.4.
Builded with Xcode 14 beta 3
Safari 16 and Xcode 14 allow us to write extension with a Web Inspector tab feature.
Added shell-safari folder based on shell-chrome folder, just replaced chrome.* with browser.* in some code lines.
Added shell-safari/app folder with Xcode Safari Web Extension Folder.
Added some scripts to package.json for building the extension app
How to build extension
Builded extension app: packages/shell-safari/app/extension/VueDevTools.app
P.S. To see extension from Safari preferences you should activate Develop/Allow Unsigned Extensions. To avoid this, the extension must be signed with Apple Developer Account.
Additional context
I guess, it should use same code base for Chrome and Safari (with chrome.* and browser.* difference), but I think it should be done by main developers of this repository.
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).