hughsk / chrome-launch

Light cross-platform launcher for Google Chrome

chrome-launch

Light cross-platform launcher for Google Chrome.

Usage

process = spawn(url, [options])

Spawns a new Chrome instance in a separate process using child_process.spawn.

Options include:

• args: additional command-line arguments to pass to Chrome. See here for a full list.
• dir: user configuration directory to use. By default, one will be created and then removed when the process is killed.
• env: environment variables to use. Defaults to process.env.
• nuke: remove opts.dir when the process exits.

The following command-line options are passed to Chrome in addition to the ones you supply:

• --no-first-run
• --no-default-browser-check
• --disable-translate
• --disable-default-apps
• --disable-popup-blocking
• --disable-zero-browsers-open-for-tests
• --user-data-dir=${opts.dir}

License

MIT. See LICENSE.md for details.

chrome-launch's Issues

Multiple-browser wrapper module

Might be nice to have something simple that wraps up chrome-launch and firefox-launch into a single module for just spawning any browser, overlooking the differences in configuration etc.

I know current options include https://github.com/substack/browser-launcher (opens a bunch of different browsers by choice, though support on OSX is a bit spotty due to the use of the open command it could be improved) and https://github.com/domenic/opener (opens the default browser), so it might be that these already address the cases where you'd want to do this? :)

/cc @mattdesl

Keep .config/google-chrome/NativeMessagingHosts

chrome-launch can be really useful to develop web-extensions. However, if a web-extension use the Native Messaging API, it needs a file in a Native messaging host location. Would it be possible to pass such a file content as a parameter to chrome-launch so it gets copied in the new profile?

Long running process gets killed by this module

I have a long running process that watches files and runs scripts through smokestack, but the process gets killed soon after Chrome closes (https://github.com/hughsk/chrome-launch/blob/master/index.js#L50).

Would be nice for chrome-launch to not kill my node process. firefox-launch does not have this problem.

Possible to start chromium instead

Would it be possible to start chromium instead of chrome?

How to launch chrome with current browser session?

thank you