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

@feugene/granum

v3.13.0

Published

Build pipeline for granular UI packages: components, styles, design tokens and themes flow from provider manifests to the application bundle through one resolution. Framework-agnostic, zero dependencies.

Readme

@feugene/granum

Build pipeline for granular UI packages: a provider manifest, one resolution per application and three channels out of it — JS (a virtual entry driven by the selection), CSS (five cascade layers) and themes with their tokens.

Since 1.0 the contract is frozen: the provider contract, the manifest format, the entry points, the shape of GranumConfig, the layer names, the virtual module ids, the CLI commands with their exit codes and the error classes change only with a major release — see §18 of the specification. The engine's vocabulary fingerprint is deliberately not part of that promise: it changes whenever the rule set does, and re-extracting a package's classes is a normal path, not a breakage.

| Entry | Environment | Purpose | |---|---|---| | @feugene/granum | browser + node | resolver and contract re-exports | | @feugene/granum/contract | browser + node | provider contract: types and define* helpers | | @feugene/granum/engine | browser + node | the GranumEngine contract and helpers (extractClasses, parseDialect, vocabularyFingerprint); no engine implementation lives here — the application picks one, e.g. @feugene/granum-engine-wind | | @feugene/granum/build | node | Vite plugin for a provider's build | | @feugene/granum/vite | node | Vite plugin for an application | | @feugene/granum/node | node | manifests, CSS emission, diagnostics as functions | | @feugene/granum/runtime | browser | theme controller | | @feugene/granum/codegen | node | provider registry generation | | @feugene/granum/client | — (types only) | ambient declarations for the virtual modules; reference them with /// <reference types="@feugene/granum/client" /> |

vite is an optional peer dependency: only ./build and ./vite need it.

Specification: docs/spec.md.