npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

chrome-driver-installer

v1.0.0

Published

CLI tool to download and install Chrome Driver and Chrome for Testing versions

Readme

Chrome Driver Installer

An interactive CLI (Command Line Interface) tool to easily download and install Chrome Driver and Chrome for Testing versions.

🚀 Features

  • ✅ Lists all Chrome for Testing versions (Stable, Beta, Dev, Canary)
  • ✅ Interactive version selection
  • ✅ Supports Chrome, ChromeDriver, and Chrome Headless Shell
  • ✅ Automatic platform detection (macOS, Linux, Windows)
  • ✅ ARM64 and x64 architecture support
  • ✅ Download progress bar
  • ✅ Automatic installation to system path (/usr/local/bin or system directory)

📦 Installation

Global Installation

npm install -g chrome-driver-installer

Local Installation (Development)

# Clone the project
git clone <repository-url>
cd chrome-driver-installer

# Install dependencies
npm install

# Create global link
npm link

🎯 Usage

Interactive Mode

The easiest way to use the tool is in interactive mode:

cft-install install

This command will present you with the following options:

  1. Channel selection (Stable, Beta, Dev, Canary, or a specific version)
  2. Binary type selection (Chrome, ChromeDriver, Chrome Headless Shell)
  3. Automatic download and installation

Command Line Options

To install a specific version directly:

# Install the stable version of Chrome
cft-install install --type chrome --version 141.0.7390.65

# Install ChromeDriver
cft-install install --type chromedriver

# Install Chrome Headless Shell
cft-install install --type chrome-headless-shell

List Versions

To see current channel versions:

cft-install list

📋 Commands

install

Downloads and installs a Chrome for Testing version.

Options:

  • -t, --type <type>: Binary type (chrome, chromedriver, chrome-headless-shell) - Default: chrome
  • -v, --version <version>: Version number to install

Examples:

# Interactive mode
cft-install install

# Install a specific version of Chrome
cft-install install -t chrome -v 141.0.7390.65

# Install ChromeDriver
cft-install install -t chromedriver

# Install Headless shell
cft-install install -t chrome-headless-shell

list

Lists available channel versions.

cft-install list

🔧 Requirements

  • Node.js >= 14.0.0
  • npm

💻 Supported Platforms

  • macOS: Intel (x64) and Apple Silicon (arm64)
  • Linux: 64-bit (x64)
  • Windows: 32-bit and 64-bit

⚠️ Permissions

On Linux and macOS, write permission to /usr/local/bin is required. If you get a permission error:

sudo cft-install install

On Windows, installation is done to C:\Program Files\Chrome for Testing directory.

📁 Installation Paths

  • Linux/macOS: /usr/local/bin/chrome, /usr/local/bin/chromedriver
  • Windows: C:\Program Files\Chrome for Testing\chrome.exe, C:\Program Files\Chrome for Testing\chromedriver.exe

🛠️ Development

Project Structure

chrome-driver-installer/
├── bin/
│   └── cli.js           # Main CLI interface
├── src/
│   ├── api.js           # Chrome for Testing API operations
│   └── installer.js     # Download and installation operations
├── package.json
└── README.md

Dependencies

  • axios: HTTP requests
  • chalk: Colored terminal output
  • cli-progress: Progress bar
  • commander: CLI framework
  • inquirer: Interactive prompts
  • ora: Spinner animations
  • extract-zip: ZIP extraction

🐛 Troubleshooting

"Permission denied" error

sudo cft-install install

"Platform not supported" error

Make sure your platform is supported by Chrome for Testing. Supported platforms:

  • macOS (Intel and Apple Silicon)
  • Linux 64-bit
  • Windows 32-bit and 64-bit

Download error

Check your internet connection and make sure the Google Chrome for Testing site is accessible.

📚 API Resources

This tool uses the official Chrome for Testing API:

  • Latest versions: https://googlechromelabs.github.io/chrome-for-testing/last-known-good-versions-with-downloads.json
  • All versions: https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json

📝 License

MIT

🤝 Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

📧 Contact

For questions or suggestions, feel free to open an issue.