We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm introducing Puppeteer for Mozilla's PDF.js project in mozilla/pdf.js#11807. While trying to figure out which version of Firefox was being downloaded, I noticed https://github.com/puppeteer/puppeteer/blame/master/install.js#L125-L151, but I think it can be simplified by simply quering the Firefox versions API instead. It can be found at https://product-details.mozilla.org/1.0/firefox_versions.json and provides you with a JSON response that is much easier to handle than the current solution where a regex is done over the response contents.
/cc @mjzffr since it was introduced in #5467
The text was updated successfully, but these errors were encountered:
chore: fetch Firefox from https://product-details.mozilla.org/1.0/fir…
862dc5c
…efox_versions.json fixes puppeteer#5742
chore: fetch Firefox from JSON source instead of RegExp (#5864)
b510c35
Fetch Firefox from https://product-details.mozilla.org/1.0/firefox_versions.json. Fixes #5742.
Thank you for improving this!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I'm introducing Puppeteer for Mozilla's PDF.js project in mozilla/pdf.js#11807. While trying to figure out which version of Firefox was being downloaded, I noticed https://github.com/puppeteer/puppeteer/blame/master/install.js#L125-L151, but I think it can be simplified by simply quering the Firefox versions API instead. It can be found at https://product-details.mozilla.org/1.0/firefox_versions.json and provides you with a JSON response that is much easier to handle than the current solution where a regex is done over the response contents.
/cc @mjzffr since it was introduced in #5467
The text was updated successfully, but these errors were encountered: