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 … Read more
I had the same issue, I tried everything which is listed from the Puppeteer guide, none of them worked for me. What works for me was to download chromium manually sudo apt-get install chromium-browser. And then, tell Puppeteer where chromium is located : const browser = await puppeteer.launch({ executablePath: ‘/usr/bin/chromium-browser’ }) Hope this will help … Read more
I’ve used page.keyboard.press(‘Enter’); usually 🙂 Works for me. Have a look at the documentation here. I think you should use .keyboard before .press for it to work properly.
I just did a test locally (you can see I did this on windows) and puppeteer happily opened my local html file using page.goto and a full file url, and saved it as a pdf: ‘use strict’; const puppeteer = require(‘puppeteer’); (async() => { const browser = await puppeteer.launch(); const page = await browser.newPage(); await … Read more
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
The GitHub issue about capturing console erorrs includes a great comment about listening to console and network events. For example, you can register for console output and network responses and failures like this: page .on(‘console’, message => console.log(`${message.type().substr(0, 3).toUpperCase()} ${message.text()}`)) .on(‘pageerror’, ({ message }) => console.log(message)) .on(‘response’, response => console.log(`${response.status()} ${response.url()}`)) .on(‘requestfailed’, request => console.log(`${request.failure().errorText} … Read more
I think you can use page.waitForSelector(selector[, options]) function for that purpose. const puppeteer = require(‘puppeteer’); puppeteer.launch().then(async browser => { const page = await browser.newPage(); page .waitForSelector(‘#myId’) .then(() => console.log(‘got it’)); browser.close(); }); To check the options avaible, please see the github link.
You can use timeout: 0 to disable timeout errors if you’re loading a heavy page. Use it in your page.goto like: await page.goto(‘url’+tableCell04Val, {waitUntil: ‘load’, timeout: 0}); You can see the PR made to Pupeteer here which added the change, along with documentation and the unit tests that implement it.
You can use page.waitForNavigation() to wait for the new page to load completely before generating a PDF: await page.goto(fullUrl, { waitUntil: ‘networkidle0’, }); await page.type(‘#username’, ‘scott’); await page.type(‘#password’, ‘tiger’); await page.click(‘#Login_Button’); await page.waitForNavigation({ waitUntil: ‘networkidle0’, }); await page.pdf({ path: outputFileName, displayHeaderFooter: true, headerTemplate: ”, footerTemplate: ”, printBackground: true, format: ‘A4’, }); If there is a … Read more
Just set value of input like this: await page.$eval(‘#email’, el => el.value=”test@example.com”); Here is an example of using it on Wikipedia: const puppeteer = require(‘puppeteer’); (async () => { const browser = await puppeteer.launch(); const page = await browser.newPage(); await page.goto(‘https://en.wikipedia.org’, {waitUntil: ‘networkidle2’}); await page.waitForSelector(‘input[name=search]’); // await page.type(‘input[name=search]’, ‘Adenosine triphosphate’); await page.$eval(‘input[name=search]’, el => el.value=”Adenosine … Read more