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

@doan-labs/duo-sdk

v0.0.0

Published

Duo developer platform sdk; Bun-based preview tooling

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

thanhminhthanhminh

Keywords

Readme

SDK

Preview SDK at 0.0.0. legacy.ts remains the host-only API for baked apps. The sandbox API exports os from index.ts and the async useKV adapter from react.ts. The shell host is integrated under packages/shell/runtime/; verification scope and reproduction are documented in docs/platform/review.md.

The host must satisfy the full caret range of the exact SDK version recorded in the app release. While 0.x, every published SDK version is its own host contract and a host bump requires a shell release. Prereleases are accepted only in development. Protocol version and SDK version are separate checks.

Call await os.connect() before rendering, then os.ready() after the first frame. Storage is asynchronous and strings-only. Snapshot and watch revisions prevent hydration gaps. useKV keeps edits made during hydration, serializes writes, and exposes hydrating/ready/saving/error states. A timeout does not prove a write failed: the client retries a mutation once using the same request ID, then the app must read back before starting a new operation.

Migration convention: keep a schema key in app storage, migrate forward, tolerate unknown keys, and finish migration before calling ready. The host delivers migration context only to the designated owner.

os.view and os.onView expose actual display, placement, visibility, focus, size and hinge angle. Ownership stays with the first view across folding; os.onOwner reports handover if that view closes. Session storage is shared between an app's views and persistent storage is private to its app id.

Commands resolve after the owner callback acknowledges. Internally the ordered request acknowledges admission first, then a separate command-result event settles the SDK promise; this allows owner callbacks to await storage safely.

Camera/microphone declarations are rejected and frame policy always denies them. Other permission adapters remain, but external developer catalogs accept no device permissions at the MVP gate. This is not a claim of full browser or native support for the broader permission roadmap.