this vs. puppeteer - launch browser to automatically stop at breakpoints

[googlechrome]

this vs. puppeteer - launch browser to automatically stop at breakpoints

[ORESoftware]

Looks like using chrome-launcher, we can use:

this command line switch:
--auto-open-devtools-for-tabs

which I found here:
https://peter.sh/experiments/chromium-command-line-switches/

[ORESoftware]

Actually this didn't work as I hoped - I thought the browser would pause at the first debugger; statement, but it didn't.

[patrickhulce]

This is outside the scope of chrome launcher. To answer your question, this repository is purely for finding and launching an existing Chrome installation on your machine. Puppeteer is a high-level API for controlling Chrome using the DevTools protocol in addition to downloading a specific compatible Chromium version and launching it. Many of your use cases you seem interested in are more in the puppeteer or cri wheelhouse.

From our perspective, the flag is passed successfully and DevTools opens as promised, but execution is not paused until DevTools is attached. Getting the behavior you desire requires more fine grained control of the browser over the protocol with puppeteer or cri.

[ORESoftware]

+1 for usage of "wheelhouse" :)

[ORESoftware]

TBH I will probably go for puppeteer first because it seems "more official" unless you think CRI is a better bet

[patrickhulce]

Yep sounds like a good plan @ORESoftware puppeteer is a great project :)