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

@eto-press/engine-shelf

v3.20260927.0

Published

The shelf engine: the writers you follow, one line each. Every new post as a row — the title as the link, a one-line deck that says what it says, the writer's own door.

Downloads

399

Readme

@eto-press/engine-shelf

The writers you follow, one line each.

The blogs desk. The masthead's sources are writers; side names the shelf a writer sits on ("Tech", "Essays"). Every morning the engine reads each writer's feed through the front door and prints every new post as one row: the title as the link, a one-line deck that says what the post says, the writer's own door. Rows are grouped by shelf, in the masthead's order, newest first within a shelf.

The deck is the copy desk's line, not the author's, and it adds nothing. When the writer's feed carries its own summary, that summary is the deck and no model is asked anything. Only a post whose feed carried the full body, or nothing at all, gets a deck from the desk — the inference boundary's fifth question — and the desk's deck is refused if it runs past two sentences or contains a number, a name or a quoted phrase the post does not. A refused deck prints as no deck. Nothing is retold.

Declare it with engine = "shelf" in a [[section]] of eto.toml (or [engine] use = "shelf" for a whole paper). It needs the judge model for the deck question and never the compositor. A morning with no new posts is NoEdition: no file, no mail, the press rests.

License: AGPL-3.0-only.