npmpackage.info

Gathering detailed insights and metrics for @puppeteer/browsers

Other packages similar to @puppeteer/browsers

@hint/connector-puppeteer

2.5.25

hint connector for browsers supported by Puppeteer

@replayio/puppeteer

0.2.12

Configuration utilities for using the Replay browsers with puppeteer

puppeteer-extra-plugin-minmax

1.1.2

Minimize/maximize puppeteer browsers in real time!

puppeteer-ie

0.5.8

Headless **Internet Explorer** NodeJS API inspired by [Puppeteer](https://pptr.dev/).

Gathering detailed insights and metrics for @puppeteer/browsers

@puppeteer/browsers - 2.10.5 | npmpackage.info

@puppeteer/browsers

JavaScript API for Chrome and Firefox

2.10.5

91,174

Apache-2.0

TypeScript

528.05 kB

8.5

Installations

npm install @puppeteer/browsers

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS, ESM

Min. Node Version

>=18

Node Version

22.15.0

NPM Version

10.9.2 Pull Requests

Open

12

Total

6,668

Closed

1,288

Merged

5,368

Issues

Open

256

Total

7,184

Closed

6,928

Releases

546

puppeteer-core: v24.13.0

puppeteer-core-v24.13.0

Updated on Jul 15, 2025

puppeteer: v24.13.0

puppeteer-v24.13.0

Updated on Jul 15, 2025

puppeteer-core: v24.12.1

puppeteer-core-v24.12.1

Updated on Jul 09, 2025

puppeteer: v24.12.1

puppeteer-v24.12.1

Updated on Jul 09, 2025

puppeteer-core: v24.12.0

puppeteer-core-v24.12.0

Updated on Jul 07, 2025

puppeteer: v24.12.0

puppeteer-v24.12.0

Updated on Jul 07, 2025

View All 546 releases

Languages

TypeScript

JavaScript

HTML

CSS

Dockerfile

Shell

TypeScript (93.15%)

JavaScript (5.38%)

HTML (1.15%)

CSS (0.23%)

Dockerfile (0.07%)

Shell (0.02%)

Developer

puppeteer

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

Apache-2.0 License

91,174 Stars

5,645 Commits

9,234 Forks

1,186 Watchers

14 Branches

516 Contributors

Updated on Jul 15, 2025

Maintainers

View All 516 Contributors

Package Meta Information

Latest Version

2.10.5

Package Id

@puppeteer/browsers@2.10.5

Unpacked Size

528.05 kB

Size

78.18 kB

File Count

168

NPM Version

10.9.2

Node Version

22.15.0

Published on

May 20, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

debug extract-zip progress proxy-agent tar-fs yargs semver

Dev Dependencies

@types/debug @types/progress @types/tar-fs @types/yargs @types/ws

@puppeteer/browsers

Manage and launch browsers/drivers from a CLI or programmatically.

System requirements

A compatible Node version (see engines in package.json).
For Firefox downloads:
- Linux builds: xz and bzip2 utilities are required to unpack .tar.gz and .tar.bz2 archives.
- MacOS builds: hdiutil is required to unpack .dmg archives.

CLI

Use npx to run the CLI:

1# This will install and run the @puppeteer/browsers package.
2# If it is already installed in the current directory, the installed
3# version will be used.
4npx @puppeteer/browsers --help

Built-in per-command help will provide all documentation you need to use the CLI.

1npx @puppeteer/browsers --help # help for all commands
2npx @puppeteer/browsers install --help # help for the install command
3npx @puppeteer/browsers launch --help # help for the launch command
4npx @puppeteer/browsers clear --help # help for the clear command
5npx @puppeteer/browsers list --help # help for the list command

You can specify the version of the @puppeteer/browsers when using npx:

1# Always install and use the latest version from the registry.
2npx @puppeteer/browsers@latest --help
3# Always use a specifc version.
4npx @puppeteer/browsers@2.4.1 --help
5# Always install the latest version and automatically confirm the installation.
6npx --yes @puppeteer/browsers@latest --help

To clear all installed browsers, use the clear command:

1npx @puppeteer/browsers clear

To list all installed browsers, use the list command:

1npx @puppeteer/browsers list

Some example to give an idea of what the CLI looks like (use the --help command for more examples):

1# Download the latest available Chrome for Testing binary corresponding to the Stable channel.
2npx @puppeteer/browsers install chrome@stable
3
4# Download a specific Chrome for Testing version.
5npx @puppeteer/browsers install chrome@116.0.5793.0
6
7# Download the latest Chrome for Testing version for the given milestone.
8npx @puppeteer/browsers install chrome@117
9
10# Download the latest available ChromeDriver version corresponding to the Canary channel.
11npx @puppeteer/browsers install chromedriver@canary
12
13# Download a specific ChromeDriver version.
14npx @puppeteer/browsers install chromedriver@116.0.5793.0
15
16# On Ubuntu/Debian and only for Chrome, install the browser and required system dependencies.
17# If the browser version has already been installed, the command
18# will still attempt to install system dependencies.
19# Requires root privileges.
20npx puppeteer browsers install chrome --install-deps

Known limitations

Launching the system browsers is only possible for Chrome/Chromium.

API

The programmatic API allows installing and launching browsers from your code. See the test folder for examples on how to use the install, canInstall, launch, computeExecutablePath, computeSystemExecutablePath and other methods.

No vulnerabilities found.

10

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

10

Dependency-Update-Tool

Determines if the project uses a dependency update tool.

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

10

License

Determines if the project has defined a license.

10

CI-Tests

Determines if the project runs tests before pull requests are merged.

10

Contributors

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

9

Security-Policy

Determines if the project has published a security policy.

9

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

8

SAST

Determines if the project uses static code analysis.

8

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

5

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

Score

8.5

/10

Last Scanned on 2025-07-15T17:33:01Z

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More