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

@aeye/context

v0.3.9

Published

Pull @aeye's agent context into your repo — flatten every installed @aeye/* package's aeye-*.md into one folder (with a generated index) to point a coding agent at.

Readme

@aeye/context

Pull @aeye's agent context — the flat agent-reference docs — into your repo with one command.

Each @aeye/* package ships LLM/agent docs as flat markdown: an aeye-<pkg>.md reference (some packages add topic sub-docs like aeye-core-tools.md), cross-linked as flat siblings (./aeye-core-types.md). Those files ship inside each installed package (node_modules/@aeye/core/aeye-core.md, …). This CLI copies every installed package's doc into one flat folder and generates an aeye.md index, so the links actually resolve — on GitHub, in your editor, and when you point a coding agent at them.

Usage

npx @aeye/context             # → ./docs
npx @aeye/context .aeye       # → any target directory

Run it from your project root (wherever node_modules/ lives). Re-run after adding or upgrading @aeye/* packages to resync. To wire it into your project:

// package.json
"scripts": { "context:sync": "aeye-context" }

What it does

  1. Scans node_modules/@aeye/* (and pnpm's virtual store) for aeye-*.md files and copies each, flat, into the target folder. Deduped by filename; direct dependencies win.
  2. Writes a generated aeye.md index — a table linking to every synced doc, labelled by each file's title. (Unlike some monorepos, @aeye has no hand-written root router, so the index is generated from whatever is installed — it never lists docs you don't have.)

Only files are written — nothing is deleted from the target.

Options

| Arg | Meaning | | --- | --- | | [target-dir] | Where to write the flat docs + index. Default: docs. | | --help | Show usage. |