Kumar McMillan

@apoorvasingh17 I don't think this can be fixed in the web-ext codebase if I'm reading https://github.com/mozilla/web-ext/issues/970#issuecomment-307893927 correctly

The `--scan-file` option has landed in the linter (https://github.com/mozilla/addons-linter/pull/1100) so this should be doable now.

Hi, thanks for filing the issue. Since we already have an `--ignore-files` option I think the best way forward is to finish implementing [config file support](https://github.com/mozilla/web-ext/issues/176) so that you could...

I agree, sorry about the delay. The config file approach is actually in progress right now. The latest patch is close to landing (see https://github.com/mozilla/web-ext/pull/1080) but there are still a...

@stokito sorry for that. Config files are [documented here](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Getting_started_with_web-ext#Setting_option_defaults_in_a_configuration_file) but they are a generic solution for setting defaults on any option so maybe it wasn't obvious to look there. What...

Yeah, that would be nice to choose a sane default. BTW, there is a shortcut for this: `web-ext run --firefox=firefoxdeveloperedition` and you can also set $FIREFOX in the environment.

oops, the aliases weren't documented. I fixed that in https://developer.mozilla.org/en-US/Add-ons/WebExtensions/web-ext_command_reference?document_saved=true#--firefox

Looks like Windows never got a developer edition alias

@eight04 Hmm, that sounds like a regression caused by https://github.com/mozilla-jetpack/node-fx-runner/pull/30 -- could you file a bug [here](https://github.com/mozilla-jetpack/node-fx-runner/issues) with some details? Also, are you sue you aren't running a 32-bit version...

> Right now, I'm using a custom script Why do you need a script for this? Is it helpful because it pre-populates the extension ID? I'd be curious to look...