Skip to content
Permalink
Browse files

docs(readme): clarify SPA and SSR (#3363)

  • Loading branch information...
sonyarianto authored and aslushnikov committed Oct 9, 2018
1 parent 6ac66c3 commit 0bb462c8f59071dd9dd6f5a854a3497f2f5497a8
Showing with 2 additions and 2 deletions.
  1. +2 −2 README.md
@@ -16,7 +16,7 @@
Most things that you can do manually in the browser can be done using Puppeteer! Here are a few examples to get you started:

* Generate screenshots and PDFs of pages.
* Crawl a SPA and generate pre-rendered content (i.e. "SSR").
* Crawl a SPA (Single-Page Application) and generate pre-rendered content (i.e. "SSR" (Server-Side Rendering)).
* Automate form submission, UI testing, keyboard input, etc.
* Create an up-to-date, automated testing environment. Run your tests directly in the latest version of Chrome using the latest JavaScript and browser features.
* Capture a [timeline trace](https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference) of your site to help diagnose performance issues.
@@ -50,7 +50,7 @@ npm i puppeteer-core
# or "yarn add puppeteer-core"
```

`puppeteer-core` is intended to be a lightweight version of puppeteer for launching an existing browser installation or for connecting to a remote one.
`puppeteer-core` is intended to be a lightweight version of Puppeteer for launching an existing browser installation or for connecting to a remote one.

See [puppeteer vs puppeteer-core](https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#puppeteer-vs-puppeteer-core).

0 comments on commit 0bb462c

Please sign in to comment.
You can’t perform that action at this time.