How to use emulateVisionDeficiency method in Puppeteer

You can try wrapping everything in a try catch block, otherwise try unwrapping the promise with then().

(async() => {
  const browser = await puppeteer.launch();
  try {
    const page = await browser.newPage();
    await page.goto(url,{timeout: 0, waitUntil: 'networkidle0'});

    const [el]= await page.$x('//*[@id="left"]/div/div[4]/div[3]/div[2]/a/h3/span[1]');
    // console.log(el)
    const txt = await el.getProperty('textContent');
    const rawTxt = await txt.jsonValue(); 

    console.log({rawTxt}); 

  } catch (err) {
    console.error(err.message);
  } finally {
    await browser.close();
  }
})();

sudo apt-get update
sudo apt-get install -y libgbm-dev

Above command fixed my problem. While doing some research on this issue I also found some other useful links which might help someone.

Answer which helped me
Official Puppeteer Github Guide for different Platforms
Medium Tutorial

Map the array to a new array, and call .replace (or, more appropriately, .replaceAll) on every item.

const input = ['asd dsa', 'asd', 'dsa asd', 'abc'];
const result = input.map(
  str => str.replaceAll('asd', 'abc')
);
console.log(result);

There is an option to save user data using the userDataDir option when launching puppeteer. This stores the session and other things related to launching chrome.

puppeteer.launch({
  userDataDir: "./user_data"
});

It doesn't go into great detail but here's a link to the docs for it: https://pptr.dev/#?product=Puppeteer&version=v1.6.1&show=api-puppeteerlaunchoptions

Update for puppeteer 12, adapted from the current documentation:

page.on('console', async (msg) => {
  const msgArgs = msg.args();
  for (let i = 0; i < msgArgs.length; ++i) {
    console.log(await msgArgs[i].jsonValue());
  }
});

await page.evaluate(() => console.log('hello', 5));
await page.evaluate(() => console.log({ foo: 'bar' }));
await page.evaluate(() => console.log([1, 2, 3, 4, 5]));

Shows the following results:

hello  
5  
{ foo: 'bar' }  
[ 1, 2, 3, 4, 5 ]  

Use the browser.version() function to find out during runtime which version is used.

If you have the page object you can use it like this:

const version = await page.browser().version();

To find out which Chromium version is bundled with the puppeteer version without starting, you should check out the release notes, there is always a section about the Chromium version which is used.

Example (taken from release notes from v1.14.0):

Big Changes

• Chromium 75.0.3738.0 (r641577)

You could wait for some reaction to your click (some page change, or HTTP request made), for example:

• wait for certain element state change https://playwright.dev/docs/api/class-locator#locator-wait-for
• wait for a new element to appear on the page (like a dialog open) https://playwright.dev/docs/api/class-page#page-wait-for-selector
• wait until a request fired https://playwright.dev/docs/api/class-page#page-wait-for-request
• wait until a response received https://playwright.dev/docs/api/class-page#page-wait-for-response
• or wait for an event https://playwright.dev/docs/api/class-page#page-wait-for-event

I have installed puppeteer with the global flag, as root. Then, I started a project as user and got the same problem as your.

Running npm install puppeteer --save in the project and as a user triggered the download of Chromium, and solved this error.

No idea why the global install of pupeeter doesn't trigger the same dependencies.

I didn't realise sending a different error code (aborted) to request.abort lets you access the previous requests. With that I was able to access the text from the original response:

const page = await browser.newPage();
await page.setCacheEnabled(false);
await page.setRequestInterception(true);

const requests = [];
let redirectBlocked = false;

page.on('request', async request => {
    let isNavRequest = request.isNavigationRequest() && request.frame() === page.mainFrame();
    if (!isNavRequest) {
        request.continue();
        return;
    }

    requests.push(request);
    if (requests.length == 1) {
        request.continue();
        return;
    }

    // *snip* more here to detect legitimate redirects...

    redirectBlocked = true;
    request.abort('aborted');

    let originalResponse = await requests[0].response();
    console.log(await originalResponse.text());
});

const response = await page.goto(pageUrl, { waitUntil: 'domcontentloaded' });

if (!redirectBlocked) console.log(await response.text());