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

@wdio/native-cdp-bridge

v1.0.0

Published

Shared single- and multi-target CDP bridge for WebdriverIO native-app services

Readme

@wdio/native-cdp-bridge

Shared Chrome DevTools Protocol (CDP) bridge for WebdriverIO native-app services. Provides the low-level pieces every CDP-attach service needs, so each service composes rather than re-implements:

  • Connection — a single CDP WebSocket connection to one target (request/response correlation, timeouts, observation-only — never issues Page.navigate).
  • DevTool — HTTP target discovery (/json, /json/version) with port-wait/retry.
  • CdpBridge — single-target client: discover → pick a target (selectTarget, default first) → connect. Supports an origin/headers option for endpoints that enforce a WebSocket Origin check (e.g. React Native's Fusebox inspector-proxy).
  • MultiTargetCdpBridge — multi-target client: one Connection per target, with switchTarget/listWindows/refresh/sendTo, backed by a TargetRegistry. Target classification is injected (classifyTarget) so renderer-specific schemes stay in the consuming service.

Consumers:

  • @wdio/electrobun-serviceMultiTargetCdpBridge (CEF on macOS / native WebView2 on Windows, one target per window; supplies the target classifier).
  • @wdio/react-native-serviceCdpBridge (single Hermes target via Metro's inspector-proxy; supplies a Hermes selectTarget + origin).
  • @wdio/electron-service — migrating to CdpBridge (single-target).

Not a public/user-facing package — it's internal infrastructure for the service family.