New issue
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
feat(docs): mention puppeteer@chrome tagged releases #3528
Conversation
README.md
Outdated
npm i puppeteer-core | ||
# or "yarn add puppeteer-core" | ||
npm i puppeteer-core@chrome-71 | ||
# or "yarn add puppeteer-core@chrome-71" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd keep this as, otherwise it is confusing: reader at this point has no idea what's chrome-71
and why they should install this version of pptr-core.
README.md
Outdated
@@ -312,6 +313,11 @@ This is not an artificial constraint: A lot of work on Puppeteer is actually tak | |||
|
|||
However, oftentimes it is desirable to use Puppeteer with the official Google Chrome rather than Chromium. For this to work, you should pick the version of Puppeteer that uses the Chromium version close enough to Chrome. | |||
|
|||
Since Chrome 70, the latest supported version Puppeteer is tagged on npm. To install Puppeteer for use with Chrome 71: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the latest supported version Puppeteer is tagged on npm
I am not sure, but is some word missing here?
close |
@JoelEinbinder updated this - ptal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
We should also add a note about them to the [For Project Maintainers] section of CONTRIBUTING.md, but I am not sure what the process actually is.