Vue-devtools: Support for Safari Browser

[rafmjr]

What problem does this feature solve?

When developing vue applications on remote servers is not always possible to connect with the ngrok tunnel as proposed on the README for the standalone electron app. It is also very inconvenient having to install ngrok and the electron shell just to be able to debug the application.

I believe extensions provide a better user experience as they are directly integrated in the web browser and do not require configuration on the projects or developers machines.

What does the proposed API look like?

Unfortunately I don't have experience developing safari extensions but I'm willing to spend time helping on the development of this feature and learning how to do it if the idea is supported.

[zoltan-magyar]

Safari 14 supports a new range of JavaScript APIs, along with a new Web Extension app extension type for Safari. This is supposed to make porting existing Chrome and Firefox extensions much easier. It also offers some conversion tools.

The biggest drawback that as they remained App Extensions, they are distributed through the AppStore in the same way previous ones, but with support for JS APIs that are used by Firefox and Chrome extensions.

[mesqueeb]

Suggestion: Create a link to easily add funding to this issue on Issue Hunt.

Once a link is generated for Issue Hunt and people start adding some funding, I'm sure some developer will pick it up in no time!!

[rafmjr]

@mesqueeb I forked this repo, created an issue and added some funding.

https://issuehunt.io/r/rafmjr/vue-devtools/issues/1

[tjkohli]

Just doubled the existing fund. Let's make this happen— it would be instrumental to my development workflow!

[mesqueeb]

I'm not sure any one can claim the funds if it's funded on a fork.
Technically I think the PR closing the issue should then be a PR towards that fork?

There's already over 100 USD on that forked git issue, so would be sad to see it go to vain.

I hope someone of the official Dev team can look into this git issue situation.

[rafmjr]

@mesqueeb I was planning of doing just that. If somebody submits a PR to close the issue, I would then submit a PR to this repository and close the one on the fork once it has been merged here.

However, I do admit it is a little bit awkward and if a maintainer of this repository would create an issue in Issue Hunt, I would close it in favor of that one. I'm open to suggestions for a better solution.