Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

suggestion: cache downloaded chromium zip in user's cache directory

See original GitHub issue

(surprised I couldn’t find an existing issue regarding this)

Puppeteer currently caches the extracted downloaded chromium folder at <project>/node_modules/puppeteer/.local-chromium.

Would be great if the zip file itself could be cached as well in the local user’s cache directory (per revision). Could use https://www.npmjs.com/package/cachedir to do that.

Having it in the user’s cache will ensure different projects can reuse already-downloaded revisions and avoid the speed hit for cold installs.

Issue Analytics

State:
Created 3 years ago
Reactions:14
Comments:5 (3 by maintainers)

Top GitHub Comments

3reactions

mathiasbynenscommented, Aug 17, 2020

@jsdevel This was implemented in #6014. It’ll be in the next Puppeteer release! Closing this issue.

2reactions

mathiasbynenscommented, Jul 14, 2020

There are a few existing issues about this such as #679. I agree we should do this. We could perhaps install the browser binaries globally, in a ~/.puppeteer directory (configurable through an environment variable), with a unique path per exact revision.