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

@stonecrop/themes

v0.42.0

Published

Design tokens and the default theme for Stonecrop

Readme

Themes

The Stonecrop token floor: one stylesheet defining every --sc-* CSS variable the component packages consume.

This is not a theme system with themes to pick between. There is a single sheet, and hosts restyle by overriding the variables in their own CSS.

Usage

import '@stonecrop/themes/default.css'

Nuxt hosts get it automatically — @stonecrop/nuxt loads it into nuxt.options.css, so there is nothing to import and no option to set.

Restyling

Override any --sc-* name in your own stylesheet. The floor wraps its declarations in the stonecrop.tokens cascade layer, and an unlayered declaration always beats a layered one regardless of specificity or source order — so a plain :root block wins, and it does not matter which stylesheet loads first.

:root {
	--sc-primary-color: #6d28d9;
	--sc-font-family: 'IBM Plex Sans', sans-serif;
}

Keep overrides on :root. Scoping them to a container (.my-app { --sc-primary-color: … }) works for elements inside that container but changes how the variable resolves elsewhere, because an ancestor declaration beats :root by inheritance proximity.

Derived tokens follow their inputs: overriding --sc-brand-success moves --sc-badge-success-bg, which is a color-mix() of it.

What the sheet contains

  • The --sc-* variables, declared on :root.
  • A font-inheritance reset, so form controls and code elements inherit the document font instead of their browser defaults.
  • The document font rule, applied to body from --sc-font-family. It pairs with the reset above — without it, the reset would strip the controls' sensible defaults and leave them inheriting the browser's serif.
  • A webfont @import for Arimo, the default --sc-font-family. It must stay the first rule in the file; CSS requires @import before all other rules.

Adding a token

A component may only read a --sc-* name this sheet defines. A var() on an undefined name is invalid at computed-value time — it does not throw, it computes to unset and renders wrong silently.

aform, atable and desktop each carry a tests/token-floor.spec.ts that fails if they consume a name the floor does not define, so adding the var() without adding the declaration is caught in CI.

Do not add a var() fallback (var(--sc-x, #fff)) as a substitute. A fallback only renders when the floor is absent, which never happens in a working host, so a wrong value there stays invisible indefinitely — that is how several tokens drifted from the floor before being removed.