chromium-edge-launcher
npmv2.0.1TypeScriptLaunch latest Edge with the Devtools Protocol port open
Adopt with care
chromium-edge-launcher is usable, with caveats.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 151 days ago. 2 releases in the last 2 years.
- BWeight: grade B, Good.
Pulls in 10 transitive packages, about 2.8 MB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- 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 chromium-edge-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 chromium-edge-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 chromium-edge-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 Edge is found at that port,
// * if `false` (default), chromium-edge-launcher will launch a new Edge with that port.
// * if `true`, throw an error
// This option is useful when you wish to explicitly connect to a running Edge, such as on a mobile device via adb
// Default: false
portStrictMode: boolean;
// (optional) Additional flags to pass to Edge, for example: ['--headless', '--disable-gpu']
// See: https://github.com/cezaraugusto/chromium-edge-launcher/blob/main/docs/edge-flags-for-tools.mdDependencies
Declared by chromium-edge-launcher v2.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (7)
Used by
Popular packages that depend on chromium-edge-launcher.
Relationship graph
Dependencies (left) and dependents (right) of chromium-edge-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
Launch latest Chrome with the Devtools Protocol port open
The time-based use-recency-unaware cousin of [`lru-cache`](http://npm.im/lru-cache)
Debugger frontend for React Native based on Chrome DevTools
High performance middleware framework
Serve static files
invariant
Release history
2 releases in the last two years, typically about 88 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.0.1latest | 5 months ago | 133 KB | Apache-2.0 |
| 2.0.0 | 5 months ago | 259 KB | Apache-2.0 |
| 0.3.0 | 2 years ago | 108 KB | Apache-2.0 |
| 0.2.0 | 2 years ago | 103 KB | Apache-2.0 |
| 1.0.0 | 5 years ago | 103 KB | Apache-2.0 |
| 0.1.0 | 5 years ago | 105 KB | Apache-2.0 |
| 0.0.0 | 5 years ago | 105 KB | Apache-2.0 |
Overview
chromium-edge-launcher is an npm package that launch latest Edge with the Devtools Protocol port open. It has 1 known dependents in the graph. The latest version is 2.0.1, released under the Apache-2.0 license.
Who should use it
Teams working in the npm ecosystem who need launch latest Edge 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 chromium-edge-launcher?
chromium-edge-launcher is usable, with caveats.
How do I install chromium-edge-launcher?
Run `npm install chromium-edge-launcher` to add chromium-edge-launcher to your npm project.
How many dependencies does chromium-edge-launcher have?
chromium-edge-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 chromium-edge-launcher released under?
chromium-edge-launcher is distributed under the Apache-2.0 license. Its dependency tree also includes: Apache-2.0, MIT.
How popular is chromium-edge-launcher?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on chromium-edge-launcher.
Is chromium-edge-launcher still maintained?
The most recent release of chromium-edge-launcher (v2.0.1) was published 5 months ago.
Does chromium-edge-launcher run install scripts?
No. chromium-edge-launcher does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.