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/shell-static

v0.3.0

Published

The static HTML shell for a pagina site: page chrome, CSS tokens, theming, and the browser runtime that hydrates figures and search.

Readme

@pagina/shell-static

The static HTML shell for a pagina site: the page chrome, the CSS tokens, the syntax highlighting, and the small client runtime that hydrates figures and search.

It is one shell over the manifest @pagina/core produces, not the only possible one — that is the whole reason the two are separate packages. A Laravel Blade view or a React app can consume the same manifest and never install this.

npm install @pagina/shell-static
import { staticShell, createHighlightedMarkdown } from "@pagina/shell-static";
import { buildStatic } from "@pagina/vite";

await buildStatic({ folder: "docs", outDir: "site", shell: staticShell, md: await createHighlightedMarkdown() });

Subpath exports

| Specifier | What it is | | --- | --- | | @pagina/shell-static | staticShell, renderPageHtml, renderNotFoundHtml, createHighlightedMarkdown | | @pagina/shell-static/interactive | the client-side behaviour: search overlay, figure hydration, theme switching | | @pagina/shell-static/theming | the token vocabulary and the theme identities the docs site ships | | @pagina/shell-static/pagina.css | the full stylesheet | | @pagina/shell-static/pagina.tokens.css | just the --pg-* custom properties, for a host that brings its own layout | | @pagina/shell-static/pagina.reading.css | the prose styles on their own | | @pagina/shell-static/client/* | the un-bundled client sources, for a host that wants to bundle them itself |

The three-way CSS split is what --theme full|tokens|none on the CLI selects between. A host page that already has a design system takes tokens and keeps its own layout; a standalone site takes full.

Licence

MIT — see LICENSE.