Open
Description
Is this a feature request or a bug?
feature
What is the current behavior?
A command like this ends in an error:
web-ext --verbose run \
-t chromium \
--chromium-binary /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
-t chromium \
--chromium-binary /Applications/Brave\ Browser.app/Contents/MacOS/Brave\ Browser
...
TypeError [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string. Received type object
at validateString (internal/validators.js:125:11)
at normalizeSpawnArguments (child_process.js:399:3)
at Launcher.spawn (child_process.js:532:38)
at Launcher.<anonymous> (/Users/kumar/dev/web-ext/node_modules/chrome-launcher/src/chrome-launcher.ts:242:27)
at Generator.next (<anonymous>)
at fulfilled (/Users/kumar/dev/web-ext/node_modules/chrome-launcher/dist/chrome-launcher.js:9:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
[program.js][error] Error code: ERR_INVALID_ARG_TYPE
What is the expected or desired behavior?
This command should launch both Chrome and Brave and support auto-reloading in both.
Version information (for bug reports)
- Firefox version: n/a
- Your OS and version: n/a
- Paste the output of these commands:
node --version && npm --version && web-ext --version
v10.15.3
6.11.3
master-e315c932777b09ed992003f384ec90abe649a0d6 (near the 3.2.0 release)
The log has this in it:
[extension-runners/chromium.js][debug] Starting Chromium instance...
[extension-runners/chromium.js][debug] (chromiumBinary: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome,/Applications/Brave Browser.app/Contents/MacOS/Brave Browser)
...so maybe the launching part won't be too hard.
Also see #1269 for running multiple versions of Firefox.