feat!: use ~/.cache/puppeteer for browser downloads

[jrandolf]

This PR moves browser downloads into ~/.cache/puppeteer to make use of global caching. This allows for better, cross-project installation of browsers and simplifies the location of browsers.

Previously, Puppeteer download Chromium to .local_chromium wherever your puppeteer-core was installed.

Now, Puppeteer will download Chromium into $PUPPETEER_CACHE_DIR/chrome (where PUPPETEER_CACHE_DIR defaults to ~/.cache/puppeteer).

Synonymous statements can be said for Firefox.

[xcbaojian]

After this upgrade, Ubuntu shows some errors when running. This seems to be a problem with the chrome path. The error that is eventually reported after relying on the installation is difficult to solve. Note that this is the case with Ubuntu.

[00:16:30] /root/workspace/pupperteer_WcJ8/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:299
[00:16:30]             reject(new Error([
[00:16:30]                    ^
[00:16:30] 
[00:16:30] Error: Failed to launch the browser process!
[00:16:30] /root/.cache/puppeteer/chrome/linux-1056772/chrome-linux/chrome: /lib/x86_64-linux-gnu/libdbus-1.so.3: no version information available (required by /root/.cache/puppeteer/chrome/linux-1056772/chrome-linux/chrome)
[00:16:30] /root/.cache/puppeteer/chrome/linux-1056772/chrome-linux/chrome: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /root/.cache/puppeteer/chrome/linux-1056772/chrome-linux/chrome)
[00:16:30] /root/.cache/puppeteer/chrome/linux-1056772/chrome-linux/chrome: symbol lookup error: /root/.cache/puppeteer/chrome/linux-1056772/chrome-linux/chrome: undefined symbol: gbm_bo_get_modifier
[00:16:30] 
[00:16:30] 
[00:16:30] TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
[00:16:30] 
[00:16:30]     at onClose (/root/workspace/pupperteer_WcJ8/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:299:20)

const puppeteer = require('puppeteer');
const moment = require('moment');
console.log(moment().format("YYYY-MM-DD HH:mm:ss"));  

(async () => {
  // const browser = await puppeteer.launch({ args: ['--no-sandbox', '--disable-setuid-sandbox'] })

const pathToExtension = '/root/.cache/puppeteer/chrome/linux-1056772/chrome-linux/chrome';
const browser = await puppeteer.launch({
   headless: true,
   timeout: 0, 
   devtools: true, 
   executablePath: pathToExtension,
   args:['--disable-infobars','--no-sandbox','--disable-setuid-sandbox']
   });
  const page = await browser.newPage();
  await page.goto('https://www.google.com');
  await page.screenshot({path: 'example110401.png'});

  await browser.close();
})();

This PR moves browser downloads into ~/.cache/puppeteer to make use of global caching. This allows for better, cross-project installation of browsers and simplifies the location of browsers.

Previously, Puppeteer download Chromium to .local_chromium wherever your puppeteer-core was installed.

Now, Puppeteer will download Chromium into $PUPPETEER_CACHE_DIR/chrome (where PUPPETEER_CACHE_DIR defaults to ~/.cache/puppeteer).

Synonymous statements can be said for Firefox.

This PR moves browser downloads into ~/.cache/puppeteer to make use of global caching. This allows for better, cross-project installation of browsers and simplifies the location of browsers.

Previously, Puppeteer download Chromium to .local_chromium wherever your puppeteer-core was installed.

Now, Puppeteer will download Chromium into $PUPPETEER_CACHE_DIR/chrome (where PUPPETEER_CACHE_DIR defaults to ~/.cache/puppeteer).

Synonymous statements can be said for Firefox.

[WilliamDEdwards]

How do I restore the previous behaviour on new versions?

When Puppeteer is installed globally by root, this change causes Chrome to be inaccessible for regular users.