puppeteer/website/versioned_docs/version-22.6.5/guides/installation.md

# Installation

To use Puppeteer in your project, run:

```bash npm2yarn
npm i puppeteer
```

When you install Puppeteer, it automatically downloads a recent version of
[Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing/) (~170MB macOS, ~282MB Linux, ~280MB Windows) and a `chrome-headless-shell` binary (starting with Puppeteer v21.6.0) that is [guaranteed to
work](https://pptr.dev/faq#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy)
with Puppeteer. The browser is downloaded to the `$HOME/.cache/puppeteer` folder
by default (starting with Puppeteer v19.0.0). See [configuration](https://pptr.dev/api/puppeteer.configuration) for configuration options and environmental variables to control the download behavior.

For every release since v1.7.0 we publish two packages:

- [`puppeteer`](https://www.npmjs.com/package/puppeteer)
- [`puppeteer-core`](https://www.npmjs.com/package/puppeteer-core)

`puppeteer` is a _product_ for browser automation. When installed, it downloads
a version of Chrome, which it then drives using `puppeteer-core`. Being an
end-user product, `puppeteer` automates several workflows using reasonable
defaults [that can be customized](https://pptr.dev/guides/configuration).

`puppeteer-core` is a _library_ to help drive anything that supports DevTools
protocol. Being a library, `puppeteer-core` is fully driven through its
programmatic interface implying no defaults are assumed and `puppeteer-core`
will not download Chrome when installed.

You should use `puppeteer-core` if you are
[connecting to a remote browser](https://pptr.dev/api/puppeteer.puppeteer.connect)
or [managing browsers yourself](https://pptr.dev/browsers-api/).
If you are managing browsers yourself, you will need to call
[`puppeteer.launch`](https://pptr.dev/api/puppeteer.puppeteernode.launch) with
an explicit
[`executablePath`](https://pptr.dev/api/puppeteer.launchoptions)
(or [`channel`](https://pptr.dev/api/puppeteer.launchoptions) if it's
installed in a standard location).

When using `puppeteer-core`, remember to change the import:

```ts
import puppeteer from 'puppeteer-core';
```
chore: release main (#12252) Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> 2024-04-11 16:51:07 +00:00			`# Installation`

			`To use Puppeteer in your project, run:`

chore: release main (#12274) :robot: I have created a release beep boop --- <details><summary>browsers: 2.2.2</summary> ## [2.2.2](https://github.com/puppeteer/puppeteer/compare/browsers-v2.2.1...browsers-v2.2.2) (2024-04-15) ### Bug Fixes * remove NetworkServiceInProcess2 set by default ([#12261](https://github.com/puppeteer/puppeteer/issues/12261)) ([ff4f70f](https://github.com/puppeteer/puppeteer/commit/ff4f70f4ae7ca8deb0becbec2e49b35322dba336)), closes [#12257](https://github.com/puppeteer/puppeteer/issues/12257) </details> <details><summary>puppeteer: 22.6.5</summary> ## [22.6.5](https://github.com/puppeteer/puppeteer/compare/puppeteer-v22.6.4...puppeteer-v22.6.5) (2024-04-15) ### Miscellaneous Chores * puppeteer: Synchronize puppeteer versions ### Dependencies * The following workspace dependencies were updated * dependencies * puppeteer-core bumped from 22.6.4 to 22.6.5 * @puppeteer/browsers bumped from 2.2.1 to 2.2.2 </details> <details><summary>puppeteer-core: 22.6.5</summary> ## [22.6.5](https://github.com/puppeteer/puppeteer/compare/puppeteer-core-v22.6.4...puppeteer-core-v22.6.5) (2024-04-15) ### Bug Fixes * remove NetworkServiceInProcess2 set by default ([#12261](https://github.com/puppeteer/puppeteer/issues/12261)) ([ff4f70f](https://github.com/puppeteer/puppeteer/commit/ff4f70f4ae7ca8deb0becbec2e49b35322dba336)), closes [#12257](https://github.com/puppeteer/puppeteer/issues/12257) * use setImmediate to reduce flakiness when processing events ([#12264](https://github.com/puppeteer/puppeteer/issues/12264)) ([73403b3](https://github.com/puppeteer/puppeteer/commit/73403b323ec0dd8a08c164cb2c07751451215788)) ### Dependencies * The following workspace dependencies were updated * dependencies * @puppeteer/browsers bumped from 2.2.1 to 2.2.2 </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> 2024-04-15 07:06:55 +00:00			```bash npm2yarn
chore: release main (#12252) Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> 2024-04-11 16:51:07 +00:00			`npm i puppeteer`
			```

			`When you install Puppeteer, it automatically downloads a recent version of`
			[Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing/) (~170MB macOS, ~282MB Linux, ~280MB Windows) and a `chrome-headless-shell` binary (starting with Puppeteer v21.6.0) that is [guaranteed to
			`work](https://pptr.dev/faq#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy)`
			with Puppeteer. The browser is downloaded to the `$HOME/.cache/puppeteer` folder
			`by default (starting with Puppeteer v19.0.0). See [configuration](https://pptr.dev/api/puppeteer.configuration) for configuration options and environmental variables to control the download behavior.`

			`For every release since v1.7.0 we publish two packages:`

			- [`puppeteer`](https://www.npmjs.com/package/puppeteer)
			- [`puppeteer-core`](https://www.npmjs.com/package/puppeteer-core)

			`puppeteer` is a _product_ for browser automation. When installed, it downloads
			a version of Chrome, which it then drives using `puppeteer-core`. Being an
			end-user product, `puppeteer` automates several workflows using reasonable
			`defaults [that can be customized](https://pptr.dev/guides/configuration).`

			`puppeteer-core` is a _library_ to help drive anything that supports DevTools
			protocol. Being a library, `puppeteer-core` is fully driven through its
			programmatic interface implying no defaults are assumed and `puppeteer-core`
			`will not download Chrome when installed.`

			You should use `puppeteer-core` if you are
			`[connecting to a remote browser](https://pptr.dev/api/puppeteer.puppeteer.connect)`
			`or [managing browsers yourself](https://pptr.dev/browsers-api/).`
			`If you are managing browsers yourself, you will need to call`
			[`puppeteer.launch`](https://pptr.dev/api/puppeteer.puppeteernode.launch) with
			`an explicit`
			[`executablePath`](https://pptr.dev/api/puppeteer.launchoptions)
			(or [`channel`](https://pptr.dev/api/puppeteer.launchoptions) if it's
			`installed in a standard location).`

			When using `puppeteer-core`, remember to change the import:

			```ts
			`import puppeteer from 'puppeteer-core';`
			```