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

@dg-superapp/bridge-adapter-example

v0.2.1

Published

Educational stub adapter showing how to implement BridgeAdapter. NOT FOR PRODUCTION.

Readme

@dg-superapp/bridge-adapter-example

EDUCATIONAL STUB — NOT FOR PRODUCTION USE.

This package is a minimal, in-memory reference implementation of the BridgeAdapter contract. It exists solely to show public consumers the shape of a working adapter. Every response is a hardcoded value from an in-memory state object. There is no real backend, no HTTP, no persistence, no retry, no observability, no telemetry.

What it does

Implements BridgeAdapter from @dg-superapp/bridge-core with two handler responses wired into callHandler():

  • userProfile — returns a static "Jane Example" profile
  • initializeMiniApp — returns { os: "example" }
  • everything else — returns a structured UNSUPPORTED failure

initialize() and dispose() are no-ops.

What it is for

  • Reading as a template for your own adapter
  • Running in unit tests where you need a valid BridgeAdapter with predictable responses
  • Demonstrating handler dispatch without pulling in WebView, flutter_inappwebview, or any other platform-specific plumbing

What it is NOT for

  • Production traffic
  • Real user data
  • Anything that needs network I/O, persistence, encryption, or retry

If you are looking for a real adapter to model after, see packages/adapter-dg for a full production implementation with WebView plumbing, error handling, timeout semantics, and response normalization.

Usage

import { createExampleAdapter } from "@dg-superapp/bridge-adapter-example";

const adapter = createExampleAdapter();
await adapter.initialize();

const result = await adapter.callHandler("userProfile", []);
console.log(result);
// { success: true, data: { userId: "USER_0001", ... }, message: "OK" }

How to turn this into a real adapter

  1. Copy src/ExampleAdapter.ts into your own package.
  2. Replace the SUPPORTED_HANDLERS set and the switch in callHandler() with calls into your real platform (native bridge, HTTP client, WebView message channel, etc).
  3. Change platformId and platformName to match your platform.
  4. Register your adapter's factory via registerAdapterImport() in a module side-effect so the SDK can lazy-load it when your platform is detected.

License

MIT — same as the parent monorepo.