puppeteer/website/versioned_docs/version-18.1.0/api/puppeteer.puppeteernode.executablepath.md
release-please[bot] 3aee641c3d
chore(main): release 18.1.0 (#9042)
🤖 I have created a release *beep* *boop*
---


##
[18.1.0](https://github.com/puppeteer/puppeteer/compare/v18.0.5...v18.1.0)
(2022-10-05)


### Features

* **chromium:** roll to Chromium 107.0.5296.0 (r1045629)
([#9039](https://github.com/puppeteer/puppeteer/issues/9039))
([022fbde](022fbde85e))

---
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>
2022-10-05 08:27:19 +00:00

30 lines
702 B
Markdown

---
sidebar_label: PuppeteerNode.executablePath
---
# PuppeteerNode.executablePath() method
**Signature:**
```typescript
class PuppeteerNode {
executablePath(channel?: string): string;
}
```
## Parameters
| Parameter | Type | Description |
| --------- | ------ | ----------------- |
| channel | string | <i>(Optional)</i> |
**Returns:**
string
A path where Puppeteer expects to find the bundled browser. The browser binary might not be there if the download was skipped with the `PUPPETEER_SKIP_DOWNLOAD` environment variable.
## Remarks
**NOTE** `puppeteer.executablePath()` is affected by the `PUPPETEER_EXECUTABLE_PATH` and `PUPPETEER_CHROMIUM_REVISION` environment variables.