why `await`?

Cool project, but I am confused that why you use await in your example:

const { Cluster } = require('puppeteer-cluster');

(async () => {
  const cluster = await Cluster.launch({
    concurrency: Cluster.CONCURRENCY_CONTEXT,
    maxConcurrency: 2,
  });
  
  // Is `await` necessary?
  await cluster.task(async ({ page, data: url }) => {
    await page.goto(url);
    const screen = await page.screenshot();
    // Store screenshot, do something else
  });

  await cluster.queue('http://www.google.com/');
  await cluster.queue('http://www.wikipedia.org/');
  // many more pages

  await cluster.idle();
  await cluster.close();
})();

when you define a task or try to add some queues, why await? I try to remove them and is ok to do that.

[thomasdondorf]

I removed the awaits from all cluster.queue examples and added this hint to the docs:

“Be aware that this function only returns a Promise for backward compatibility reasons. This function does not run asynchronously and will immediately return.”

I guess that should clear any confusion in the future.

[SidKwok]

Option 2 seems nice.