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

appwire

v0.1.0

Published

Live app REPL for Node.js — run code inside your running app

Readme

Appwire

Live REPL for Node.js — evaluate code inside your running process without restarting.

appwire(ipc:main.ts) > $users = await $app.get(UserService).findAll()
[{ id: 1, email: '[email protected]' }, ...]  18ms

appwire(ipc:main.ts) > $users[0].email
'[email protected]'  0ms

appwire(ipc:main.ts) > .timeit 20 await $app.get(PrismaService).user.count()
42
  runs: 20  avg: 4ms  min: 3ms  max: 8ms

appwire(ipc:main.ts) > .doc $app.get(AuthService)
  AuthService
  Methods:
    login(dto)
    logout(userId)
    validateToken(token)
  Properties:
    jwtService
    usersService

Install

npm install -g appwire

Usage

cd your-project
appwire                          # entry auto-detected from package.json
appwire --entry src/main.ts      # explicit entry
appwire --entry apps/backend/    # directory — entry detected inside

Persist the entry with .appwirerc in your project root:

{ "entry": "src/main.ts" }

Framework Adapters

Optional. Wire your DI container into $app.

NestJS — no import needed. The bootstrap intercepts NestFactory.create and wires $app to the DI container automatically.

Plain Node

import { startAppwireAgent } from 'appwire'

startAppwireAgent({ context: { db, config, redis } })

REPL Commands

| Command | Description | | -------------------- | -------------------------------------------------------- | | .timeit [N] <expr> | Time expression. N runs shows avg/min/max. | | .doc <expr> | Inspect constructor name, methods, and properties. | | .services | List DI services / context keys. | | .vars | List session variables assigned with $name = expr. | | .reload | Restart the app and reconnect. | | .editor | Multi-line mode — Ctrl+D to run, Ctrl+C to cancel. | | .history | Show last 20 entries. | | .exit | Quit. |

Eval Context

| Variable | Description | | --------- | -------------------------------------------------------- | | $app | DI container (NestJS) or context object (plain Node) | | $env | process.env | | $fetch | Global fetch (Node.js 18+) | | $reload | Evict a module from require.cache and re-require it | | require | CJS require resolved from the app's working directory |

$-prefixed variables assigned during a session persist across evals and tab-complete automatically. Use .vars to list them.

MCP server

appwire-mcp exposes Appwire as an MCP server so Claude Code, Cursor, Zed, and Cline can evaluate code in your running app.

appwire-mcp
APPWIRE_ENTRY=src/main.ts appwire-mcp

Tools: evaluate, list_services, ping.

How it works

appwire
  └── reads package.json → detects entry → spawns app
        └── app starts with --require bootstrap.cjs
              ├── VM context: $app, $env, $fetch, $reload, require
              ├── console.* intercepted → streamed to REPL
              └── IPC channel open → waiting for eval requests

appwire REPL
  └── readline → sends { id, code, timeout }
        └── bootstrap evaluates in VM context
              └── returns { id, type, value, duration }

Bootstrap is a self-contained CJS bundle — no external deps, safe to --require into any Node process.

Security

  • APPWIRE=1 gates the IPC channel. appwire sets it on spawn; your normal process never has it.
  • IPC channel is process-local — only the parent appwire process can send messages.

License

MIT