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

@pagina/cli

v0.3.0

Published

Command line interface for pagina: `pagina dev`, `pagina build`, `pagina pack`, and `pagina unpack` over an article folder.

Downloads

400

Readme

@pagina/cli

The command line for pagina: point it at a folder of Markdown and get a static documentation site, or a live one with hot reload while you write.

npm install -g @pagina/cli
# or, without installing:
npx @pagina/cli build docs --out site
usage: pagina dev|build <folder> [--out dist] [--base /] [--port 4321] [--host <addr>] [--edit]
                                 [--no-strict] [--theme full|tokens|none] [--no-chrome]
                                 [--strict-assets] [--no-search]
                                 [--site-url https://example.com/path/]
                                 [--mirror-of https://primary.example/path/]
       pagina pack [folder] [-o article.pgz] [--base /] [--created <iso8601>]
       pagina unpack <article.pgz> [dir] [--force]

The four commands

  • dev — Vite over the folder, hot reload on every file it renders. --edit also serves the WYSIWYG editor at /__edit/, which makes the folder writable over HTTP, so it is opt-in per run.
  • build — the static site. Strict by default: a nav entry without a file, a dead link, a missing snippet, a broken anchor, or a figure that fails to pre-render fails the build with a diagnostic naming the page. --no-strict downgrades those to warnings.
  • pack — one portable .pgz. It builds a bundle rather than zipping a folder: resolves the snippets that live outside it, copies only the media a page actually references, carries the pre-rendered figures, and checksums every file.
  • unpack — verifies the whole bundle before writing a byte.

What gets installed with it

@pagina/core, @pagina/vite, and @pagina/shell-static come along as dependencies. The Kineglyph figure engine — @kineglyph/core, @kineglyph/export, @kineglyph/web — is declared as a peer so that a project which already pins a Kineglyph version keeps that one copy rather than getting a second nested underneath the CLI. npm installs peers for you; if you have disabled that, install the three alongside.

Licence

MIT — see LICENSE.