question-mark
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.

ERROR Run npm install to download the correct Chromium revision (1056772)

See original GitHub issue

Bug description

Steps to reproduce the problem:

  1. 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:closed
  • Created a year ago
  • Reactions:2
  • Comments:25

github_iconTop GitHub Comments

4reactions
otrajmancommented, Nov 12, 2022

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:

@gRoussac https://github.com/gRoussac I changed the puppeteerrc.cjs and still no luck any chance you’ll look at my repo and tell me what I’m missing? it’s a very small project and that puppeteer error is very frustrating repo: https://github.com/AdirBuskila/star-info

— Reply to this email directly, view it on GitHub https://github.com/puppeteer/puppeteer/issues/9192#issuecomment-1311910060, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA7OLDEJ6EZKZ3TMSZYUCTWHZW4RANCNFSM6AAAAAARSLH57Y . You are receiving this because you are subscribed to this thread.Message ID: @.***>

4reactions
kfitzgeraldcommented, Nov 1, 2022

Running into this as well, I suspect it has to do with the breaking change

use ~/.cache/puppeteer for browser downloads (https://github.com/puppeteer/puppeteer/pull/9095)

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

node.js - Puppeteer Error: Chromium revision is not downloaded
I only managed to fix the issue by manually installing Chromium after much searching and trying most of the suggestions:
Read more >
chromium-revision - npm
Chromium binaries for Node.js projects with the ability to specify revision number. Latest version: 1.0.0, last published: 3 years ago.
Read more >
A critical error: Chromium revision is not downloaded.
A critical error: Chromium revision is not downloaded. ... Run "npm install" or "yarn install" at Launcher.launch ...
Read more >
Chromium revision is not downloaded. Run "npm install" or ...
Error : Chromium revision is not downloaded. Run "npm install" or "yarn install" at Launcher.launch ...
Read more >
Error: Chromium revision is not downloaded. Run "npm install ...
Recently I have needed to solve a problem that involves generating a PDF file based on database conte...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found