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

aihand

v0.4.2

Published

The hand of AI — drive the live UI (and any website), from one CLI

Readme

aihand

The hand of AI. Your agent can read files but can't see the running page, guesses at the UI instead of looking at it.

Add one plugin. Drive the user's already-open tab over HTTP.

aihand runtime   screen | click | fill | wait | check   YOUR app — the already-open tab, via --port=
aihand probe     open <url> | …                         NOT your app: Playwright, fresh empty session

Every command and flag: aihand runtime --help.

Why it's faster than Playwright

After a Playwright click the model still has to think and re-read the page to see what changed — an extra round, about 5–10s. aihand click returns the delta (view: chat → im, modal opened), so it does not need another watch. On a click that is ~30–50× (~180ms vs 5–10s).

| | aihand | Playwright MCP | |---|---|---| | a click | ~180ms, 1 turn | click + think/re-read, extra 5–10s (~30–50×) |

Install

npm i -D aihand
// vite.config.ts
import { aihand } from 'aihand/vite'
export default defineConfig({ plugins: [aihand()] })

// webpack.config.js
const { aihand } = require('aihand/webpack')
module.exports = { plugins: [aihand()] }

// rspack.config.ts
import { aihand } from 'aihand/rspack'
export default { plugins: [aihand()] }

// next.config.mjs  — Next has no plugins[]; wrap is the slot (same as withSentryConfig)
// Next >= 15.3, webpack + turbopack. Already have a config? aihand(nextConfig)
import { aihand } from 'aihand/next'
export default aihand()

Default ports: Vite 5173, webpack/rspack 8080, Next 3000 — aihand runtime --port=8080 (or 3000).

On dev, the plugin writes <!-- AIHAND:START --> into AGENTS.md / CLAUDE.md so the agent reaches for aihand runtime screen instead of guessing from source.

Stores (Zustand / Redux / MobX) and knobs are discovered automatically. No config file, nothing to hang on window. If a store cannot be recognized, /screen still lists DOM knobs and /click still works.

License

MIT