[WIP] Command line interface

[vweevers]

Finally had some time for this. Done so far:

Launching

• --browser name[@version]
• --proxy URI
• --no-proxy or better --no-proxies-on (Firefox only option. What's the use?)
• --detached
• --headless
• Additional arguments, in the following format (i.e. everything after -- is passed to the browser):

browser-launcher2 -b chrome@45 http://google.com -- --remote-debugging-port=9222

Things to solve in programmatic API / lib

• Don't do configFile || defaultConfigFile everywhere, add functional equivalent to config module
• Use cache for listing browsers. How caching and profiles are handled is likely to change but for now it should be consistent and always use the cache (also because that's what you'd expect when passing a --config option to the CLI).
• Support custom profile directory (useful if you want it to persist and install extensions for example)
• Overriding default arguments (an additional argument like the above should replace an argument that browser-launcher2 adds, if any)
• Add http:// to URLs if protocol is missing

Other

• Without any args, list browsers
• Shorthands
• --help
• --version
• --update
• --config file
• Readme documentation

[vweevers]

Formatted --help a bit (screenshot of term with monokai scheme):

[vweevers]

@gregpabian Safe to remove this entire block right? It makes no sense to create a directory on read, fs.exists is deprecated, and mkdir isn't even necessary (because both configModule.write and createProfiles already do this themselves). And the third argument to the callback (configDir) is never used, nor documented.

[Reinmar]

Hi, we finally know that unfortunately we'll not be able to maintain browser-launcher2 anymore. More details in: #57. There may be new active forks available, so you can port your PR to one of them.