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.
Firefox Puppeteer not importing
See original GitHub issueSteps to reproduce
Tell us about your environment:
- Puppeteer version: 2.1.1
- Platform / OS version: MacOS Catalina 10.15.3
- URLs (if applicable):
- Node.js version: 12.6.0
What steps will reproduce the problem?
Please include code that reproduces the issue.
- import * as puppeteerFirefox from ‘puppeteer-firefox’
What is the expected result?
The import should pull in puppeteer-firefox as import puppeteer from 'puppeteer' pulls puppeteer
What happens instead?
Could not find a declaration file for module ‘puppeteer-firefox’. ‘/Users/<path>/node_modules/puppeteer-firefox/index.js’ implicitly has an ‘any’ type.
Try npm install @types/puppeteer-firefox if it exists or add a new declaration (.d.ts) file containing declare module 'puppeteer-firefox';
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ah, I think the ‘Could not find browser message’ might be a confusing.
If you want puppeteer to download Firefox as part of installation you should run something like
PUPPETEER_PRODUCT=firefox yarn add puppeteer@next.Firefox support is experimental so you will encounter timeouts for features that aren’t supported yet.
If you could share more information about your test suite (link to project?), including debug logs for a Chrome run (e.g.
DEBUG=puppeteer:* yarn:test unit) that can help prioritize feature work in Firefox’s remote protocol implementation.