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

@subimpact/e

v0.100.3

Published

Minimal terminal coding harness. Fork of earendil-works/pi (MIT) with the MCP, codemode, and tool-search built-ins removed; compatibility with the classical pi extension/package ecosystem.

Readme

e

e is a minimal terminal coding harness, forked from earendil-works/pi (MIT). It is not affiliated with the upstream project.

e keeps the original pi promise, as code: one model, one loop, four tools (read, write, edit, bash). The mcp, codemode, and tool-search built-in extensions are removed, not disabled: there is no setting that brings them back. See the root README for the full fork story and the compatibility scope.

Getting started

Install the command-line interface with npm:

npm install -g --ignore-scripts @subimpact/e

This requires Node.js 22.19 or newer. e does not require dependency lifecycle scripts for a normal npm installation.

Start e in the directory where you want it to work:

cd /path/to/project
e

For a built-in AI provider, run /login inside e to connect a subscription or API key. Then give e a task.

To reuse an existing pi installation's config, point E_CODING_AGENT_DIR (or the legacy PI_CODING_AGENT_DIR) at ~/.pi/agent.

Classical pi packages, extensions, skills, prompt templates, and themes install with e install <package> exactly as before. Packages that require the 0.99 built-in MCP, codemode, or tool-search APIs do not work in e, by design. Extensions that use hidden or deferred tools, tool loadout hooks, or mid-conversation tool changes still install, with a warning: e ignores those features. Why.

The package is one self-contained bundle with two runtime dependencies (jiti, photon-node). import from @subimpact/e loads that same bundle; no TypeScript declarations are published.

See the documentation for full setup and usage instructions.

Development

npm install --ignore-scripts  # Install all dependencies without running lifecycle scripts
npm run build         # Refresh model data, then build all packages
npm run build:offline # Rebuild using existing model data without network access
npm run check         # Lint, format, and type check
./test.sh             # Run tests (skips LLM-dependent tests without API keys)
./pi-test.sh          # Run e from sources (can be run from any directory)

License

MIT. See ../../LICENSE.