chrome-launcher
npmv1.2.1TypeScriptLaunch latest Chrome with the Devtools Protocol port open
Safe to adopt
Yes — chrome-launcher scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 349 days ago. 2 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 349 days ago. 2 releases in the last 2 years.
- BWeight: grade B, Good.
Pulls in 10 transitive packages, about 2.8 MB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 4 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
Apache-2.0 — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding chrome-launcher to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Licenses in the dependency tree
Every license you inherit by installing chrome-launcher, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=12.13.0
- Module format
- ESM only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the chrome-launcher README.
{
// (optional) remote debugging port number to use. If provided port is already busy, launch() will reject
// Default: an available port is autoselected
port: number;
// (optional) When `port` is specified *and* no Chrome is found at that port,
// * if `false` (default), chrome-launcher will launch a new Chrome with that port.
// * if `true`, throw an error
// This option is useful when you wish to explicitly connect to a running Chrome, such as on a mobile device via adb
// Default: false
portStrictMode: boolean;
// (optional) Additional flags to pass to Chrome, for example: ['--headless', '--disable-gpu']
// See: https://github.com/GoogleChrome/chrome-launcher/blob/main/docs/chrome-flags-for-tools.mdDependencies
Declared by chrome-launcher v1.2.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (7)
Used by
Popular packages that depend on chrome-launcher.
Relationship graph
Dependencies (left) and dependents (right) of chrome-launcher.
Frequently installed together
Experimental debugger shell for React Native for use with @react-native/debugger-frontend
An HTTP/1.1 client, written from scratch for Node.js
Open stuff like URLs, files, executables. Cross-platform.
flow typed nullthrows
Lightweight debugging utility for Node.js and the browser
The time-based use-recency-unaware cousin of [`lru-cache`](http://npm.im/lru-cache)
Debugger frontend for React Native based on Chrome DevTools
Launch latest Edge with the Devtools Protocol port open
High performance middleware framework
Serve static files
invariant
Release history
2 releases in the last two years, typically about 92 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.2.1latest | 11 months ago | 134 KB | Apache-2.0 |
| 1.2.0 | 1 year ago | 133 KB | Apache-2.0 |
| 1.1.2 | 2 years ago | 129 KB | Apache-2.0 |
| 1.1.1 | 2 years ago | 129 KB | Apache-2.0 |
| 1.1.0 | 2 years ago | 129 KB | Apache-2.0 |
| 1.0.0 | 3 years ago | 124 KB | Apache-2.0 |
| 0.15.2 | 3 years ago | 125 KB | Apache-2.0 |
| 0.15.1 | 4 years ago | 180 KB | Apache-2.0 |
| 0.15.0 | 4 years ago | 111 KB | Apache-2.0 |
| 0.14.2 | 4 years ago | 109 KB | Apache-2.0 |
| 0.14.1 | 4 years ago | 109 KB | Apache-2.0 |
| 0.14.0 | 5 years ago | 106 KB | Apache-2.0 |
| 0.13.4 | 6 years ago | 142 KB | Apache-2.0 |
| 0.13.3 | 6 years ago | 161 KB | Apache-2.0 |
| 0.13.2 | 6 years ago | 159 KB | Apache-2.0 |
Overview
chrome-launcher is an npm package that launch latest Chrome with the Devtools Protocol port open. It has 1 known dependents in the graph. The latest version is 1.2.1, released under the Apache-2.0 license.
Who should use it
Teams working in the npm ecosystem who need launch latest Chrome with the Devtools Protocol port open and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (Apache-2.0).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use chrome-launcher?
Yes — chrome-launcher scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 349 days ago. 2 releases in the last 2 years.
How do I install chrome-launcher?
Run `npm install chrome-launcher` to add chrome-launcher to your npm project.
How many dependencies does chrome-launcher have?
chrome-launcher declares 11 direct dependencies and pulls in 10 packages in total once its runtime tree is resolved totalling about 2.8 MB on disk.
What license is chrome-launcher released under?
chrome-launcher is distributed under the Apache-2.0 license. Its dependency tree also includes: Apache-2.0, MIT.
How popular is chrome-launcher?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on chrome-launcher.
Is chrome-launcher still maintained?
The most recent release of chrome-launcher (v1.2.1) was published 11 months ago.
Does chrome-launcher run install scripts?
No. chrome-launcher does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.