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

@aegisrunner/next

v0.2.1

Published

Next.js config wrapper that attaches AegisRunner to your dev server — scan your localhost app with AI, no deploy.

Readme

@aegisrunner/next

Attach AegisRunner to your Next.js dev server. Wrap your next.config, run next dev, and an AI scan of your localhost app is one keypress away — no deploy, no staging URL, no second terminal.

Next has no clean "server listening" plugin hook, so this wraps your config: in the dev phase it opens a secure outbound-only tunnel to your dev port and — on a or on startup — crawls your running app, generates tests, and streams progress into your terminal.

Install

npm install -D @aegisrunner/next
// next.config.mjs
import withAegisRunner from '@aegisrunner/next'

/** @type {import('next').NextConfig} */
const nextConfig = { /* your config */ }

export default withAegisRunner(nextConfig, {
  scanOn: 'manual', // 'manual' (press a) | 'startup' (scan on boot)
})
export AEGIS_TOKEN=aegis_xxxxxxxx   # a project CI trigger token (Pro/Business)
npm run dev
  ▲ Next.js  —  Local: http://localhost:3000

  ◆ aegis   tunnel open → https://ab12cd.tunnel.aegisrunner.com
  ◆ aegis   press [a] + Enter to scan your local app

Options

| Option | Default | Description | |--------|---------|-------------| | token | process.env.AEGIS_TOKEN | CI trigger token (Pro/Business). | | scanOn | 'manual' | 'manual' — press a. 'startup' — scan once when the tunnel opens. | | port | -p / PORT / 3000 | Dev-server port. Set it explicitly if you run on a non-standard port and don't pass -p. | | host | '127.0.0.1' | Local host the tunnel forwards to. | | label | package name | Shown in every log line as ◆ aegis·<label> — disambiguates tunnels when several dev servers run at once (monorepos). | | api | public API | process.env.AEGIS_API override. |

The wrapper is a pure pass-through in every phase except dev — it never runs in next build or production. The tunnel, scan trigger and live-progress stream are reused from @aegisrunner/cli. Prefer no config change? aegis dev -- next dev is identical.

Docs

MIT © AegisRunner