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

@prvt/mini-app-sdk

v0.1.3

Published

Browser SDK for prvt room web apps.

Readme

@prvt/mini-app-sdk

Browser SDK for apps opened inside a prvt room. The host keeps the LiveKit connection and integration credentials; this package communicates with the host through the typed postMessage bridge.

For a no-build integration, load the stable deployment URL instead:

<script src="https://call.example.com/prvt-mini-app.js"></script>
<script>
  const app = Prvt.MiniApp.create({ hostOrigin: "https://call.example.com" });
  app.ready().then(() => app.request("queue.add", { trackId: "track_123" }));
</script>

The script exposes window.Prvt.MiniApp.create and is generated from the same source as this package.

import { createPrvtMiniApp } from "@prvt/mini-app-sdk";

const app = createPrvtMiniApp({ hostOrigin: "https://call.example.com" });
const context = await app.ready();

const result = await app.request("queue.add", { trackId: "track_123" });
app.close();

The hostOrigin should be the canonical prvt application origin. The context contains only display context and capabilities; it never contains a room code, participant token, or integration key. Actions are handled by the integration that opened the app and should be validated and idempotent on that backend.

For a reusable coding-agent brief, see AGENT_PROMPT.md. It describes the browser app lifecycle, the typed action bridge, security boundaries, and the corresponding integration handler.