ERROR Run npm install to download the correct Chromium revision (1056772)
See original GitHub issueBug description
Steps to reproduce the problem:
- Deploy instance on render.com cloud working fine on localhost
Getting ERROR Run npm install to download the correct Chromium revision (1056772)
Oct 30 09:25:19 PM ERROR Run npm install to download the correct Chromium revision (1056772).
Oct 30 09:25:19 PM
Oct 30 09:25:19 PM at ChromeLauncher.resolveExecutablePath (node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:120:27)
Oct 30 09:25:19 PM at ChromeLauncher.executablePath (node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:166:25)
Oct 30 09:25:19 PM at ChromeLauncher.launch (node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:70:37)
Oct 30 09:25:19 PM at async exports.convert_to_pdf (api/controllers/client.js:287:21)
Puppeteer version
19.2.0
Node.js version
10.15.0
npm version
8.19.2
What operating system are you seeing the problem on?
macOS
Configuration file
No response
Relevant log output
Oct 30 09:25:19 PM ERROR Run npm install to download the correct Chromium revision (1056772).
Oct 30 09:25:19 PM
Oct 30 09:25:19 PM at ChromeLauncher.resolveExecutablePath (node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:120:27)
Oct 30 09:25:19 PM at ChromeLauncher.executablePath (node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:166:25)
Oct 30 09:25:19 PM at ChromeLauncher.launch (node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:70:37)
Oct 30 09:25:19 PM at async exports.convert_to_pdf (api/controllers/client.js:287:21)
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:25
I believe the file needs to be “.puppeteerrc.cjs” with a leading dot.
I also found that when patching an image (which runs “npm ci” on GAE Flex), I needed to add this to package.json when puppeteer gets upgraded:
{ “scripts”: { “postinstall”: “node node_modules/puppeteer/install.js”, } }
On Fri, Nov 11, 2022, 11:20 Adir Buskila @.***> wrote:
Running into this as well, I suspect it has to do with the breaking change
In my case, dependencies are installed using a privileged system account and the app is run using a different unprivileged account. I suspect that since the cache path is now user-dependent, this is a new problem.
The unprivileged user in my case also has no home directory, so puppeteer 19.x is effectively broken for me.
While I appreciate the effort to reduce the filesystem bloat when using puppeteer across many apps, allowing puppeteer to install things outside the scope of node_modules appears to be a significant oversight.