launch() options get nuked

ebidel commented 7 years ago

If the user launches with:

const browser = await puppeteer.launch({
    slowMo: 250, // slow down by 250ms
    headless: false,
    ignoreHTTPSErrors: true,
    dumpio: true,
});

We kill all these options adding --no-sandbox. Instead, the options should be captured, parsed, and reset.

sahanDissanayake commented 6 years ago

@ebidel How many concurrent request can we handle ? Is there a nice way to do this ?

I'm thinking of using EC2 Micro server to have this service.

ebidel commented 6 years ago

How many can what handle? Wouldn't it depend on your platform / environment?

On Sun, Jul 8, 2018, 7:58 PM Sahan Dissa notifications@github.com wrote:

@ebidel https://github.com/ebidel How many concurrent request can we handle ? Is there a nice way to do this ?

I'm thinking of using EC2 Micro server to have this service.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ebidel/try-puppeteer/issues/1#issuecomment-403368232, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOigLayjlt6S5vS0yXrFmD4YWDjoDZwks5uEvEQgaJpZM4PU5VC .

ebidel / try-puppeteer

launch() options get nuked #1