Error: Could not find expected browser (chrome) locally. Run `npm install` to download the correct Chromium revision (901912).
See original GitHub issueError: Could not find expected browser (chrome) locally. Run npm install
to download the correct Chromium revision (901912).
when build example and start, errors are occurred. ‘npm run dev’ is ok, but ‘npm run build’ and ‘npm run start’ has problem.
reproduce steps
- clone this project
- npm install
- cd example && npm install
after I encountered errors bellow `It looks like you’re trying to use TypeScript but do not have the required package(s) installed.
Please install @types/react by running:`
so i installed @types/react and upgrade next, react 4. npm install --save-dev @types/react && npm install next@latest && npm upgrade react@latest react-dom@latest
- npm build && npm start
- browser open and go to url http://localhost:3000/api/basic?myQueryParam=asdf
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Could not find expected browser chrome locally - Stack Overflow
8", It gives this error: Error: Could not find expected browser (chrome) locally. Run npm install to download the correct Chromium revision ( ......
Read more >Could not find expected browser (chrome) locally. Run npm ...
Run npm install to download the correct Chromium revision (938248). When using serverless-esbuild plugin with puppeteer.
Read more >Puppeteer.js Error: Could not find expected browser (chrome ...
Error : Could not find expected browser (chrome) locally. Run `npm install` to download the correct Chromium revision (1022525).
Read more >“Could not find expected browser (chrome) locally. Run `npm ...
Run `npm install` to download the correct Chromium revision (901912). Error: Could not find expected browser (chrome) locally. Run `npm install` to download...
Read more >Puppeteer - npm
A high-level API to control headless Chrome over the DevTools Protocol. ... and puppeteer-core will not download Chromium when installed.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Serving my Next.js app on DigitalOcean, I’m getting this error after updating to 4.2.2:
Hey folks @guhyeon @mvandergrift @kamenskiyyyy
https://github.com/neg4n/next-api-og-image/releases/tag/4.2.2 🚀
Thanks for your contributions, feel free to continue the topic if problem still persists 😄