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

@vesture/theme-retro

v0.1.3

Published

A warm, terracotta-and-serif retro theme implementing the @vesture/tokens contract.

Readme

@vesture/theme-retro

A warm, terracotta-and-serif theme implementing the @vesture/tokens contract. It exists to prove the theming system actually works for swapping brands — every @vesture/react component reads from vars.*, never fixed values, so this package needs nothing but token values to produce a completely different look.

Usage

import "@vesture/theme-retro/styles.css";
import { retroThemeClass } from "@vesture/theme-retro";

document.documentElement.classList.add(retroThemeClass);

Apply the class to document.documentElement (or another true ancestor of document.body), not an inner <div> — see the @vesture/react README for why this matters when components render through portals (Modal, Tooltip, Popover, DropdownMenu, Toast).

What's different from the default theme

  • Warm cream background and terracotta primary color instead of neutral black/white
  • Serif display font (Georgia) for headings
  • Larger border radius and heavier border widths for a chunkier look
  • A bouncier motion easing curve

Every other structural decision — spacing scale, font size scale, line heights — matches the default theme, since components rely on those values being consistent across themes for layout to hold.