Open andywer opened 6 years ago
Issue: How to know when the script(s) in the headless browser are finished?
Potential solution: Script exits explicitly. Could add a window.exit(statusCode)
method or add a process
object with a process.exit(statusCode)
method.
Run any code in a headless chrome instance. Useful for running tests in a browser (Karma sucks!), snapshotting and more.
Entry point may be a JS or HTML file. Console output will be piped through, unhandled errors will be piped to stderr. The DOM, the rendered page, network requests or coverage may be piped into an output file.
Sample usage
Integrations
Optional integration to use a locally present webpack or parcel bundler and its config might be cool.