Open Bizarrus opened 1 month ago
As it can be also spotted in one of the results of the search (https://github.com/search?q=repo%3Amozilla%2Fweb-ext%20opera&type=code), web-ext run
supports running an extension also on Opera through the --chromium-binary
(by passing the past to the Opera binary as mentioned in the description associated to that option:
https://github.com/mozilla/web-ext/blob/420aa78db72f6c8d10f7ae6cfa8a61be7cf43820/src/program.js#L614
Is there any particular reason why highlighting that through the package.json keywords would be perceived as an issue?
Well, it is advertised with keywords for search results. The package can therefore be found via NPM, although Opera is not supported.
Even if you specify the Opera (I tried it) executable, all attached parameters except the devtools do not work. The automatic start of extensions is not given here at any time, as is the case with Firefox, for example.
Search: https://github.com/search?q=repo%3Amozilla%2Fweb-ext%20opera&type=code Package: https://github.com/mozilla/web-ext/blob/420aa78db72f6c8d10f7ae6cfa8a61be7cf43820/package.json#L58
Why Opera here is listen? Opera never been used or declared on Docs.