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

@3kaiu/xbridge-js

v0.1.0

Published

Open-source, zero-business-coupling cross-platform bridge SDK for H5.

Readme

xbridge-js

Open-source, zero-business-coupling H5 bridge SDK. Implements a JSON-RPC 2.0 variant protocol with a universal StandardAdapter for any container that injects window.XBridge.postMessage, plus a sync bypass adapter for window.dsbridge.call.

Install

npm install @3kaiu/xbridge-js
# or
pnpm add @3kaiu/xbridge-js

Quick start

import { XBridge } from "@3kaiu/xbridge-js";

const bridge = new XBridge();

// Async RPC (Promise, JSON-RPC over the detected transport)
const info = await bridge.call("getDeviceInfo");

// Fire-and-forget (no id, no response expected)
await bridge.call("logEvent", { foo: 1 }, { noCallback: true });

// Sync bypass — only when a sync adapter (e.g. your existing native bridge) is present
const version = bridge.callSync("getAppVersion");

// Subscribe to host-pushed events
const off = bridge.onEvent("onNetworkChange", (params) => {
  console.log("network changed", params);
});
// later
off();

// Register a handler for Native → H5 calls
const unreg = bridge.registerHandler("getUserConfirmation", (params) => {
  return confirm(params?.message);
});
// later
unreg();

// Re-sniff if the container injects window.XBridge after SDK init
import { resetSniffCache } from "@3kaiu/xbridge-js";
resetSniffCache();
const bridge2 = new XBridge(); // picks up StandardAdapter now

Auto-sniff order

The constructor probes window once (cached) and picks the first available adapter:

  1. window.XBridge.postMessageStandardAdapter (async, bidirectional)
  2. window.dsbridge.callNativeSyncAdapter (sync only; call() warns)
  3. none → NoopAdapter (warns "no bridge environment")

Override explicitly when you need to force a transport, e.g. for tests:

import { XBridge, StandardAdapter } from "@3kaiu/xbridge-js";

const bridge = new XBridge({ adapter: new StandardAdapter() });

Adapters

| Adapter | Transport | Direction | | --- | --- | --- | | StandardAdapter | window.XBridge.postMessage(str) | async bidirectional via window.__XBridge__.resolve/reject + window.__XBridgeInbound__ + XBridgeEvent | | NativeSyncAdapter | window.dsbridge.call(method, args) | sync only (returns value directly) |

StandardAdapter installs global overrides that route host → H5 messages into the core. The overrides are re-installed lazily on each send() call, so they survive host bootstrap re-injection.

Protocol

// H5 → Host
{ "jsonrpc": "2.0", "id": "<uuid>", "method": "getDeviceInfo", "params": {} }

// Host → H5 (response)
{ "jsonrpc": "2.0", "id": "<uuid>", "result": "..." }
{ "jsonrpc": "2.0", "id": "<uuid>", "error": { "code": -32000, "message": "..." } }

// Host → H5 (event, no id)
{ "jsonrpc": "2.0", "method": "onNetworkChange", "params": {} }

XBRIDGE_PROTOCOL_VERSION is exported as "2.0".

Performance

  • Single installed message handler per adapter; inbound parsed once.
  • O(1) Map for pending-request correlation and event listeners.
  • JSON.stringify / JSON.parse only — no intermediate allocations.
  • generateId() uses native crypto.randomUUID when available (cached).
  • No runtime dependencies.

License

MIT