chromium-bidi
npmv17.0.2TypeScriptAn implementation of the WebDriver BiDi protocol for Chromium implemented as a JavaScript layer translating between BiDi and CDP, running inside a Chrome tab.
Safe to adopt
Yes — chromium-bidi scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 65 days ago. 50 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 65 days ago. 50 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 2 transitive packages, about 15 MB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 2 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 chromium-bidi 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.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Licenses in the dependency tree
Every license you inherit by installing chromium-bidi, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=20.19.0 <22.0.0 || >=22.12.0
- Module format
- ESM only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the chromium-bidi README.
CdpSendCommandCommand = {
method: "goog:cdp.sendCommand",
params: CdpSendCommandParameters,
}
CdpSendCommandParameters = {
method: text,
params: any,
session?: text,
}
CdpSendCommandResult = {
result: any,
session: text,Dependencies
Declared by chromium-bidi v17.0.2. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (2)
Peer (1)
Dev (27)
Used by
Popular packages that depend on chromium-bidi.
Relationship graph
Dependencies (left) and dependents (right) of chromium-bidi.
Frequently installed together
Reactive Extensions for modern JavaScript
TypeScript definitions for node
TypeScript definitions for ws
Polyfill for the URLPattern API
Download and launch browsers
Better typed `querySelector` and `querySelectorAll`.
This repository contains TypeScript types conforming to the [WebDriver BiDi](https://w3c.github.io/webdriver-bidi/) specification. It also supports WebDriver BiDi extension modules defined in other specifications:
The Chrome DevTools Protocol JSON
Release history
50 releases in the last two years, typically about 6 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 17.0.2latest | 2 months ago | 9.1 MB | Apache-2.0 |
| 17.0.1 | 2 months ago | 35 KB | Apache-2.0 |
| 16.0.1 | 4 months ago | 8.9 MB | Apache-2.0 |
| 15.0.0 | 7 months ago | 13 MB | Apache-2.0 |
| 14.0.0 | 7 months ago | 13 MB | Apache-2.0 |
| 13.1.1 | 7 months ago | 13 MB | Apache-2.0 |
| 13.1.0 | 7 months ago | 13 MB | Apache-2.0 |
| 13.0.1 | 7 months ago | 13 MB | Apache-2.0 |
| 13.0.0 | 7 months ago | 13 MB | Apache-2.0 |
| 12.1.0 | 7 months ago | 13 MB | Apache-2.0 |
| 12.0.1 | 8 months ago | 12 MB | Apache-2.0 |
| 12.0.0 | 9 months ago | 12 MB | Apache-2.0 |
| 11.0.1 | 9 months ago | 12 MB | Apache-2.0 |
| 11.0.0 | 10 months ago | 12 MB | Apache-2.0 |
| 10.6.1 | 10 months ago | 12 MB | Apache-2.0 |
Overview
chromium-bidi is an npm package that an implementation of the WebDriver BiDi protocol for Chromium implemented as a JavaScript layer translating between BiDi and CDP, running inside a Chrome tab. It has 1 known dependents in the graph. The latest version is 17.0.2, released under the Apache-2.0 license.
Who should use it
Teams working in the npm ecosystem who need an implementation of the WebDriver BiDi protocol for Chromium implemented as a JavaScript layer translating between BiDi and CDP, running inside a Chrome tab and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, 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
- Large dependency tree (30 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use chromium-bidi?
Yes — chromium-bidi scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 65 days ago. 50 releases in the last 2 years.
How do I install chromium-bidi?
Run `npm install chromium-bidi` to add chromium-bidi to your npm project.
How many dependencies does chromium-bidi have?
chromium-bidi declares 30 direct dependencies and pulls in 2 packages in total once its runtime tree is resolved totalling about 15 MB on disk.
What license is chromium-bidi released under?
chromium-bidi is distributed under the Apache-2.0 license.
How popular is chromium-bidi?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on chromium-bidi.
Is chromium-bidi still maintained?
The most recent release of chromium-bidi (v17.0.2) was published 2 months ago.
Does chromium-bidi run install scripts?
No. chromium-bidi does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.