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

@prss/premium-themes

v1.0.4

Published

Paid PRSS themes, published as a single package served over CDN.

Readme

PRSS premium themes

Paid PRSS themes. This repo is private; only the compiled output is published, as @prss/premium-themes.

The published layout matches the free themes, so the API points a theme at .../@prss/premium-themes@<version>/build/<theme> and PRSS resolves manifest.json, index.html, theme.css, client.js and the template bundles beneath it.

Why the split

Themes have to be fetched from a CDN without authentication, so the compiled bundle is necessarily public — that is true today and does not change here. What stays private is the source, which is why these themes live apart from prss-io/themes rather than in it.

Premium themes are deliberately not forkable: PRSS's theme creator builds its base-theme list from public repos and filters out anything premium.

Shared components

packages/_shared mirrors the layer in prss-io/themes. It is a copy on purpose: this repo stays self-contained, and @prss/themes publishes build output only. Port changes across by hand when the public layer moves.

Each theme aliases @/components/ui, @/hooks and @/lib into it and compiles that source with its own Tailwind config, so shared components pick up the theme's design tokens.

npm install
npm run build      # build every theme and assemble build/
npm run verify     # check the published layout is complete