Thomas Dondorf

I agree that a `setOptions` for all widgets would be nice. But you can also do it without it. Just remove the widget from the screen and recreate it. **Example**...

I have not tried it myself, but if you are able to launch two puppeteer instances in parallel, there should be no problems using the library. What did you try...

No. I'm not using this library on AWS Lambda. In case you want to investigate: - Does spawning a normal puppeteer instance work (without this library)? - Does spawning two...

That commit/repo you are linking to does not change anything related to running on AWS, it just adds "per browser options". So, if you got it running on AWS with...

Nice, thank you for sharing your config.

You mean something like: `cluster.queueForWorker(0, data)`. This sounds like an interesting feature. But it's currently not supported.

Good idea.

This sound more like a bug with puppeteer as the library only gives these arguments to the puppeteer library. Have you checked if it works with only puppeteer? Closing this...

Okay, can you give a minimal example that I can use to reproduce the problem?

1+2 -> Yes, the idea is to support these use cases. 3 -> This can already be done right now. Just pass the extra information (job id) as data to...