github/puppeteer
0
0
Fork 0
mirror of https://github.com/puppeteer/puppeteer synced 2024-06-14 14:02:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(api.md): fix typo (#3848)

Browse Source
This commit is contained in:
Dan Dascalescu 2019-01-26 21:37:02 -08:00 committed by Andrey Lushnikov
parent 62da2366c6
commit 7446550fdb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/api.md
View File

@ -348,7 +348,7 @@ To sum up, the only differences between `puppeteer-core` and `puppeteer` are:
In most cases, you'll be fine using the `puppeteer` package. In most cases, you'll be fine using the `puppeteer` package.
However, you should use `puppeteer-core` if: However, you should use `puppeteer-core` if:
- you're building another end-user product or library atop of DevTools protocol. For example, one might build PDF generator using `puppeteer-core` and write a custom `install.js` script that downloads [`headless_shell`](https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md) instead of Chromium to save disk space. - you're building another end-user product or library atop of DevTools protocol. For example, one might build a PDF generator using `puppeteer-core` and write a custom `install.js` script that downloads [`headless_shell`](https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md) instead of Chromium to save disk space.
- you're bundling Puppeteer to use in Chrome Extension / browser with the DevTools protocol where downloading an additional Chromium binary is unnecessary. - you're bundling Puppeteer to use in Chrome Extension / browser with the DevTools protocol where downloading an additional Chromium binary is unnecessary.
When using `puppeteer-core`, remember to change the *include* line: When using `puppeteer-core`, remember to change the *include* line: