Luca Greco

> > ``` > > if we should consider adding the bundled file in our npm package or not (eslint doesn't seem to be included its webpack bundle neither to...

@dependabot rebase

@creesch I've reproduced this issue and I did a brief debug session on it locally, but with a slightly different STR composed by the following steps: 1. open reddit in...

Besides Rob question (which we are still interested in), we agreed that we would be willing to extend the --firefox-prefix option to support this use case (at the moment we...

@willdurand this looks like a duplicate of #142, which has been fixed long time ago in #676. The check is being done using the `update-notifier` dependency (used in [`checkForUpdates` defined...

The fact that addons-linter is using eslint internally for some (not all) of the addons-linter rules is an internal implementation detail of the addons-linter and I would really prefer to...

In the meantime, the short term workarounds could be: - using the addons-linter bin script, to use the options that addons-linter may be already providing - or using `web-ext lint...

One other possible approach to get the port we choose internally may be to use web-ext as a nodejs library and programmatically retrieve the port through that, using web-ext as...

In #2477 we introduced support for handling a similar issue in flatpak packaged Firefox, by running it through flatpak run along with the --filesystem option passed, in theory something similar...

@moroshko not yet, but it is definitely a good idea. It is definitely possible to introduce this feature by using the `"flow-annotation-check"` npm dependency to discover if a file has...