docs: small misc. updates (#9978)

Co-authored-by: Alex Rudenko <OrKoN@users.noreply.github.com>
This commit is contained in:
Nikolay Vitkov 2023-04-05 18:06:33 +02:00 committed by GitHub
parent fa93e4ebdf
commit c03f5922f8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 19 additions and 23 deletions

View File

@ -29,7 +29,7 @@ Here are a few examples to get you started:
- Capture a - Capture a
[timeline trace](https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference) [timeline trace](https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference)
of your site to help diagnose performance issues. of your site to help diagnose performance issues.
- Test Chrome Extensions. - [Test Chrome Extensions](https://pptr.dev/guides/chrome-extensions).
## Getting Started ## Getting Started
@ -39,8 +39,10 @@ To use Puppeteer in your project, run:
```bash ```bash
npm i puppeteer npm i puppeteer
# or `yarn add puppeteer` # or using yarn
# or `pnpm i puppeteer` yarn add puppeteer
# or using pnpm
pnpm i puppeteer
``` ```
When you install Puppeteer, it automatically downloads a recent version of When you install Puppeteer, it automatically downloads a recent version of

View File

@ -98,13 +98,15 @@ rely on complex conditions (such as names of distinct files) that cannot be
captured by the build system. To clean artifacts, you can run captured by the build system. To clean artifacts, you can run
```sh ```sh
npm run clean # or npm run clean --workspace <package> npm run clean
# or specify the package
npm run clean --workspace <package>
``` ```
## Comprehensive testing ## Comprehensive testing
Outside of `npm test`, there are several other Outside of `npm test`, there are several other
[`npm` scripts](https://docs.npmjs.com/cli/v8/using-npm/scripts) that are [`npm` scripts](https://docs.npmjs.com/cli/using-npm/scripts) that are
usually check through CI: usually check through CI:
- `test-install` - Tests whether `puppeteer` and `puppeteer-core` install - `test-install` - Tests whether `puppeteer` and `puppeteer-core` install

View File

@ -97,17 +97,6 @@ taking place in the Chromium repository. Heres a typical story:
- Once the upstream fix is landed, we roll updated Chromium into Puppeteer: - Once the upstream fix is landed, we roll updated Chromium into Puppeteer:
https://github.com/puppeteer/puppeteer/pull/2769 https://github.com/puppeteer/puppeteer/pull/2769
However, oftentimes it is desirable to use Puppeteer with the official Google
Chrome rather than Chromium. For this to work, you should install a
`puppeteer-core` version that corresponds to the Chrome version.
For example, in order to drive Chrome 71 with puppeteer-core, use `chrome-71`
npm tag:
```bash
npm install puppeteer-core@chrome-71
```
## Q: Which Chromium version does Puppeteer use? ## Q: Which Chromium version does Puppeteer use?
Find the version using one of the following ways: Find the version using one of the following ways:
@ -135,7 +124,6 @@ To fetch Firefox Nightly as part of Puppeteer installation:
```bash ```bash
PUPPETEER_PRODUCT=firefox npm i puppeteer PUPPETEER_PRODUCT=firefox npm i puppeteer
# or "yarn add puppeteer"
``` ```
#### Q: Whats considered a “Navigation”? #### Q: Whats considered a “Navigation”?

View File

@ -29,7 +29,7 @@ Here are a few examples to get you started:
- Capture a - Capture a
[timeline trace](https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference) [timeline trace](https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference)
of your site to help diagnose performance issues. of your site to help diagnose performance issues.
- Test Chrome Extensions. - [Test Chrome Extensions](https://pptr.dev/guides/chrome-extensions).
## Getting Started ## Getting Started
@ -39,8 +39,10 @@ To use Puppeteer in your project, run:
```bash ```bash
npm i puppeteer npm i puppeteer
# or `yarn add puppeteer` # or using yarn
# or `pnpm i puppeteer` yarn add puppeteer
# or using pnpm
pnpm i puppeteer
``` ```
When you install Puppeteer, it automatically downloads a recent version of When you install Puppeteer, it automatically downloads a recent version of

View File

@ -26,7 +26,7 @@
] ]
}, },
"build:packages": { "build:packages": {
"command": "npm pack --workspace puppeteer --workspace puppeteer-core --workspace @puppeteer/browsers", "command": "npm pack --quiet --workspace puppeteer --workspace puppeteer-core --workspace @puppeteer/browsers",
"dependencies": [ "dependencies": [
"../../packages/puppeteer:build", "../../packages/puppeteer:build",
"../../packages/puppeteer-core:build", "../../packages/puppeteer-core:build",

View File

@ -98,13 +98,15 @@ rely on complex conditions (such as names of distinct files) that cannot be
captured by the build system. To clean artifacts, you can run captured by the build system. To clean artifacts, you can run
```sh ```sh
npm run clean # or npm run clean --workspace <package> npm run clean
# or specify the package
npm run clean --workspace <package>
``` ```
## Comprehensive testing ## Comprehensive testing
Outside of `npm test`, there are several other Outside of `npm test`, there are several other
[`npm` scripts](https://docs.npmjs.com/cli/v8/using-npm/scripts) that are [`npm` scripts](https://docs.npmjs.com/cli/using-npm/scripts) that are
usually check through CI: usually check through CI:
- `test-install` - Tests whether `puppeteer` and `puppeteer-core` install - `test-install` - Tests whether `puppeteer` and `puppeteer-core` install