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

@agentshouse/app-bridge

v0.1.0-alpha.1

Published

Renderer-side client of the agents.house App bridge: navigation, ceremonies and status, with an in-page test host.

Readme

@agentshouse/app-bridge

The renderer-side client of the agents.house App bridge. An App served by House receives one message port before its own scripts run; this package is that port's one listener. It carries three families:

  • Navigation - the part of the shell's URL below the App's path, with its query and fragment. The shell delivers it when the App starts and whenever the User navigates; the App asks the shell to push or replace it.
  • Ceremony - the App asks the shell to leave for one of House's own purpose-bound authenticated pages. The shell navigates only to a same-origin absolute path, carries its current address as the return target, and the page returns there when it completes. An App names an address House gave it in a reading and composes none.
  • Status - sync state, credential state, release availability and observed failure.

The package carries no credential handling and no Runtime family. It surfaces the dedicated Runtime port the worker transfers over the bridge as a plain message port, which the App hands to the MD Runtime client entry.

Use

import { connectHouseBridge } from '@agentshouse/app-bridge';
import { connectMdRuntime } from '@agentshouse/mdruntime/client';

const bridge = connectHouseBridge();
const md = connectMdRuntime(await bridge.runtime);

bridge.onAddress((address) => render(address));
bridge.onStatus((status) => showSync(status.sync));

open('/rooms/atlas');
function open(address) {
  bridge.push(address);
}

async function manageSecurity(securityPath) {
  try {
    await bridge.ceremony(securityPath);
  } catch (refusal) {
    report(refusal);
  }
}

bridge.runtime resolves with a structural HouseMessagePort. A consumer whose Runtime client entry asks for the DOM MessagePort type passes it through directly at run time and casts at the type level.

Test without a House

import { connectHouseBridge } from '@agentshouse/app-bridge';
import { createHouseBridgeTestHost } from '@agentshouse/app-bridge/test-host';

const host = createHouseBridgeTestHost({ address: '/rooms/atlas' });
const bridge = connectHouseBridge(host.port);

bridge.push('/rooms/atlas/members');
host.open('/rooms/atlas');

The host plays the shell and the worker: it delivers the address the App starts at, records every push and replace and answers each with the address the shell would then show, records an admitted ceremony, refuses one that is not a same-origin absolute path, publishes a status, and attaches a Runtime port.