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

@amitkaps/pagez

v0.3.0

Published

pagez — Markdown, as pages.

Readme

pagez

pagez — Markdown, as pages.

A folder holds pages written in Markz, each .md at its folder's path, and what they use: a style.css, a frame.html, images and fonts. Pagez compiles each page, writes its head from its frontmatter, checks that every file and page it links is there, and Vite bundles them with hashed names. One page is the smallest site.

site/
├── index.md      the page at /
├── about.md      the page at about/
├── style.css     their design, in place of Pagez's theme
├── frame.html    the document around them, optional
├── img/
└── fonts/

A folder below uses the nearest style.css and frame.html above it, or its own.

pagez build site     # writes site/dist/
pagez dev site       # serves it while it's written
pagez preview site   # serves what was built
pagez preview site --port 4173   # on that port, or fails if it's taken
pagez check site     # lists what to fix in every page, and writes nothing
pagez rules folder-page   # prints a rule, an error or a warning
pagez help build     # prints what a command does

Usage states each command once: build, dev, preview, check, rules and help.

A folder with its own Vite config adds the plugin instead:

import pagez from "@amitkaps/pagez/vite";

export default { plugins: [pagez()] };

Usage says how to build with it, and pages has the rules a page and a site follow. 0.1 builds one page without elements or ${…}. Elements, ${…} and many pages are built since, and what's left comes next, in the plan.

Install

pnpm add -D @amitkaps/pagez vite-plus

It needs Node 26 or newer, the Node it's built and tested on.

Read the docs for its design, plan and lessons. It follows craftz's rules for how it builds, checks and releases.