Feature request: Option to disable --single-process browser flag

[madcow]

I'm having problems with the windows build hanging indefinitely and in non-headless mode I see chromium closing directly after launching. I believe I narrowed it down to the (officially unsupported) --single-process flag in /lib/browser.js on line 61. When I manually run my browser with this flag it causes the same instant shutdown, but everything works as expected without the flag.

Would it be possible to add an --browser-single-process boolean option to improve compatibility with different chromium versions/forks? Or is there a technical necessity for running chromium as a single process?

[madcow]

I've now confirmed that removing the --single-process line 61 in /lib/browser.js allows single-file-cli to run without problems. I'm using ungoogled-chromium as my browser binary.