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

@aihu/runtime

v6.2.0

Published

Single File Component (.aihu) runtime — registers custom elements compiled by @aihu/compiler.

Readme

@aihu/runtime

Aihu — agentic discovery and interaction, for human purpose.

Single File Component (.aihu) runtime — registers custom elements compiled by @aihu/compiler.

@aihu/runtime owns component definition and lifecycle behavior. It consumes the published DOM, context, and primitives packages and exposes a narrow @aihu/runtime/app bridge for @aihu/app.

(Hand-written prose lives in this block. Replace this placeholder; everything below is auto-generated.)

Install

npm install @aihu/runtime
# or
bun add @aihu/runtime

Package version @aihu/[email protected].

Package facts

| | | |---|---| | Version | 6.1.1 | | Tier | A — Reactive runtime core — custom-element wiring for compiled SFCs | | Bundle size | 4.62 kB (gz) — limit 4750 B | | Published files | 3 entries | | License | MIT |

Package version @aihu/[email protected].

Exports

| Subpath | ESM | CJS | |---|---|---| | . | ./dist/index.js | — | | ./ssr | ./dist/ssr-string.js | — | | ./app | ./dist/app.js | — |

Package version @aihu/[email protected].

Dependencies

Dependencies:

  • @aihu/primitives — ^0.2.3

Peer dependencies:

  • @aihu/arbor — ^4.1.2
  • @aihu/signals — ^0.5.1
  • @aihu/context — ^0.2.0

Package version @aihu/[email protected].

See also

Package version @aihu/[email protected].

License

MIT — see LICENSE.

Package version @aihu/[email protected].

Release procedure

Merge the reviewed change to main, update the package version, and verify the default branch locally. Then create and push the exact annotated tag runtime-v<package.version> (for example, runtime-v6.1.1). The release workflow rejects tags that do not point at the current main commit, checks that npm returns E404 for the target version, and publishes the one verified tarball with npm provenance through GitHub OIDC. Do not publish from a local classic token or create a tag before the workflow's package and consumer checks pass.