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/press

v3.20260927.0

Published

A local-first printing press for a personal newspaper: the frame of the morning that binds a paper's sections — each printed by one engine (the news brief, the desk, the letter, the digest, the sports page, the wrap, the shelf, the ledger) from its own so

Readme

@eto-press/press

The printing press, not the paper.

The thin binding that makes a directory into a paper. It reads sources.toml (the editorial line) and eto.toml (the nameplate and plumbing), keeps its journal in db/, prints to archive/ and site/, and reaches outside that directory only to read the news through the front door and — if configured — to send the mail and write the backups. The press never owns a paper; it visits one.

Since generation 2 the press is the frame of the morning: preflight (the mastheads, migrations, model pins through the inference boundary), the engine registry (eto, desk, letter, digest, sports, wrap, shelf, ledger), the joint where an engine prints one section's whole edition in one call, and the tail: the archive write, the published-edition store, the report. Since generation 3 a paper is sections — [[section]] blocks in eto.toml, each naming an engine and a source file, printed in order and bound into one morning; a paper that declares none is one section on [engine] use from sources.toml, as before. The other verbs — render, email, correct, export, backup — are here too; the eto command in @eto-press/cli is the way to call them. The engine interface is public at @eto-press/press/engine.

In a paper

npm install @eto-press/press @eto-press/cli
npx eto doctor
npx eto print

@eto-press/press exports the public API (nightly, Inference, Ollama, the masthead schema, config); the verbs are subpath exports (@eto-press/press/main, /render-site, /send-edition, …), and the default theme is reachable as @eto-press/press/brief.css for skins written against generation 2.

License: AGPL-3.0-only.