Skip to content

Conversation

terjanq
Copy link
Contributor

@terjanq terjanq commented Jun 6, 2023

Since puppeteer 19.0.0. the browser is loaded from ~/.cache/. Maybe not the cleanest fix but it works.

puppeteer/puppeteer#9533

Node.js v18.16.0
/home/user/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:300
                    throw new Error(Could not find Chrome (ver. ${this.puppeteer.browserRevision}). This can occur if either\n +
                          ^

Error: Could not find Chrome (ver. 113.0.5672.63). This can occur if either
 1. you did not perform an installation before running the script (e.g. npm install) or
 2. your cache path is incorrectly configured (which is: /home/user/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
    at ChromeLauncher.resolveExecutablePath (/home/user/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:300:27)
    at ChromeLauncher.executablePath (/home/user/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:181:25)
    at ChromeLauncher.computeLaunchArguments (/home/user/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:97:37)
    at async ChromeLauncher.launch (/home/user/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:83:28)
    at async /home/user/bot.js:121:19

Node.js v18.16.0

terjanq added 3 commits June 6, 2023 19:01
Since puppeteer 1.19 the browser is loaded from `~/.cache/`. Maybe not the cleanest fix but it works.

puppeteer/puppeteer#9533
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant