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

@rubar/lavish-themes

v0.1.0

Published

Six self-contained HTML theme shells — latex, terminal, water, swiss, handwritten, zine. No JS, no build step.

Readme

Lavish Themes

Six self-contained HTML theme shells you can paste content into. No build step, no framework dependency at view time, no JavaScript. Open any file in a browser and it just renders.

All six themes rendering the same sample content

Built for use with lavish-axi and the lavish-publish-cf worker, but the themes themselves are framework-agnostic — a Claude Code agent, a static-site generator, or a human with a text editor can all use them the same way.

The themes

Tier 1 — vendored from upstream sources

CSS lives inline in each shell. No external CDN at view time. Refresh from upstream with python3 _vendor_tier1.py.

| Slug | Aesthetic | Best for | Vendored from | | --- | --- | --- | --- | | latex | Academic paper, Latin Modern | Briefs that should feel like research | latex.vercel.app + LM woff2 fonts base64-inlined | | terminal | Monospace terminal stationery | Postmortems, runbooks, RFCs | [email protected] | | water | Neutral classless, auto dark/light | General-purpose briefs | water.css@2 |

Tier 2 — hand-built

Authored in this repo. Only external dependency is Google Fonts.

| Slug | Aesthetic | Best for | | --- | --- | --- | | swiss | International typographic. Inter Tight, black/red/white grid, flush-left. | Decisive product/strategy briefs | | handwritten | Lined exercise book + Caveat + Permanent Marker. Warm paper. | Personal notes, casual writing | | zine | Yellow / black / magenta. Anton display. Clip-path angles, hard shadows. | Loud manifestos, launches |

Preview them

Open the gallery — every theme side-by-side, no server needed:

open _gallery.html      # macOS
xdg-open _gallery.html  # Linux

The gallery uses <iframe srcdoc> so each theme is inlined into one file. Works offline.

Use a theme

From a git checkout:

cp tier2/swiss.html my-brief.html
# edit my-brief.html, replace the sample body content with yours
open my-brief.html

Or via the CLI (works the same whether installed or npx'd):

lavish-themes copy swiss my-brief.html
open my-brief.html

That's the whole flow. Each shell carries identical sample content so you can compare them apples-to-apples; when you adapt one, keep its structural markup (e.g. latex uses <article> wrapping) and replace the prose.

Install

Via npm (fastest, also gives you the lavish-themes CLI):

npm install -g @rubar/lavish-themes
lavish-themes list
lavish-themes copy swiss my-brief.html

Or one-off via npx:

npx @rubar/lavish-themes copy swiss my-brief.html
npx @rubar/lavish-themes path latex          # absolute path to the theme HTML

Via git (for editing themes or rebuilding the gallery):

./scripts/install.sh

The script clones (or updates) this repo at ~/.lavish-themes, optionally symlinks it into ~/.claude/skills/lavish-themes for skill discovery, and prints the gallery path so you can preview.

Build / maintenance

python3 _vendor_tier1.py     # refresh tier-1 vendored CSS from upstream
python3 _build_gallery.py    # regenerate _gallery.html from tier1/ + tier2/

Python 3.8+. No third-party packages.

To add a theme: drop the HTML into tier1/ or tier2/, add a line to the THEMES = [...] list in _build_gallery.py, re-run the script.

Conventions

  • No JavaScript. Themes work with script-src 'none' CSPs (e.g. the strict CSP on the lavish-publish-cf worker).
  • Tier 1 vendoring inlines the entire upstream stylesheet (and base64-inlined fonts where applicable) so themes work offline and CDN-free.
  • Tier 2 only loads Google Fonts externally. Replace the <link rel="stylesheet"> with an inlined @font-face declaration if you need fully offline behaviour.
  • Every shell carries <meta name="lavish-design" content="off">. That tag tells lavish-axi not to inject its DaisyUI auto-styling on top — irrelevant if you're not using lavish-axi, harmless if you are.

Related projects

  • lavish-axi — the local editor / review surface. lavish-axi <file.html> opens a theme in a browser with feedback tooling around it.
  • lavish-publish-cf — self-hosted Cloudflare Worker that publishes themed HTML pages on your own domain. The /publish Claude skill there knows how to pick a theme from this library.

Licence

Source in this repo is MIT — see LICENSE.

Vendored upstream CSS in tier1/*.html is redistributed under the upstream authors' licences — see THIRD-PARTY-NOTICES.md.