You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for creating this very useful wrapper around puppeteer, Sindre!
Currently, it launches a Chrome instance for every capture via puppeteer.launch(). Would it make sense, if we added an option to let it connect to a running Chrome instance via puppeteer.connect()? I could take a look at implementing this, if there are no obvious (or not so obvious) arguments against it. 😄
The text was updated successfully, but these errors were encountered:
I decided to use the puppeteer library directly, because for my use-case this library was just a small wrapper around it anyways.
I had to deal with zombie processes as well (in a Docker/K8s environment) and the solution was to use tini as my Docker entrypoint which takes care of correctly reaping sub-process zombies.
Thanks for creating this very useful wrapper around puppeteer, Sindre!
Currently, it launches a Chrome instance for every capture via
puppeteer.launch()
. Would it make sense, if we added an option to let it connect to a running Chrome instance via puppeteer.connect()? I could take a look at implementing this, if there are no obvious (or not so obvious) arguments against it. 😄The text was updated successfully, but these errors were encountered: