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

pi-echo-bundle

v0.1.0

Published

Installs and registers all thirteen echo extensions (and the pi-echo-themes theme pack) in one shot — each remains independently installable on its own too

Downloads

134

Readme

pi-echo-bundle

Installs and registers all thirteen echo extensions in one shot: pi install npm:pi-echo-bundle. Each of the other thirteen packages remains independently installable on its own — this is purely additive, nothing about them changed to make this exist.

Design note

Depends on all thirteen packages as real npm dependencies (so one npm install resolves the whole set — the same mechanism that resolves pi-echo-core for any single one of them today), then imports each package's default export and calls it with the same pi instance. This relies only on ordinary Node ancestor node_modules resolution, not any Pi-specific glob support.

Verified before building, not assumed: checked Pi's own source (resolveExtensionEntries in core/package-manager.js) for whether a package manifest could instead just point at its dependencies' folders via "extensions" glob patterns. It can't — manifest extension paths resolve via plain path.resolve(), not globs (despite the docs' prose implying otherwise for this resource type), and Pi's own auto-discovery explicitly skips node_modules. Importing each package's factory function directly, rather than trying to get Pi to discover them, is what actually works.

The real trade-off, stated plainly: Pi's loader treats whatever file it's given as one Extension — loading thirteen packages this way means Pi sees a single "pi-echo-bundle" extension, not thirteen independently identifiable ones. Each factory call is individually wrapped (try/caught and logged by name) so one package failing to register doesn't take the rest down and the failure is still identifiable by name — but any future per-extension enable/disable UI in Pi would still show one entry, not thirteen. Installing the packages individually doesn't have that limitation.

Usage

pi install npm:pi-echo-bundle        # global
pi install npm:pi-echo-bundle -l     # project-local

Want only some of the thirteen? Install those specific packages instead (pi install npm:pi-echo-permissions, etc.) — this package is for "give me everything," not a replacement for picking individually.