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

@dapplelight/signet-tokens

v0.4.1

Published

Signet design tokens. One theme file per design system; all themes satisfy CONTRACT.md.

Readme

@dapplelight/signet-tokens

Themes for Signet as plain CSS variables: colour, radius, type, shadow and motion. A theme is one CSS file that defines the variables in the theme contract. Docs: https://signet.dapplelight.in/

Themes

| File | Look | |---|---| | editorial.css | warm paper, ink text, green accent | | cinematic.css | cool neutrals, violet accent | | finance.css | editorial plus money and spend-category slots |

Each has light and dark (the .dark class). Every text pair meets WCAG AA, and a test checks it.

Use

@import "tailwindcss";
@import "@dapplelight/signet-tokens/editorial.css";
@import "@dapplelight/signet-tokens/base.css";

base.css adds the body defaults, focus outline, the overlay animations (tw-animate-css) and a reduced-motion rule.

React Native and Expo

@dapplelight/signet-tokens/native is the same themes as plain JS (hex or rgba() strings, numbers for radius, spacing and font size), with no React or React Native import. nativeTheme takes what useColorScheme() returns:

import { useColorScheme, View, Text } from "react-native"
import { nativeTheme } from "@dapplelight/signet-tokens/native"

export function Card() {
  const t = nativeTheme("editorial", useColorScheme()) // "light" | "dark" | null | "unspecified"
  return (
    <View style={{ backgroundColor: t.colors.card, borderRadius: t.radius.lg, padding: t.spacing * 4 }}>
      <Text style={{ color: t.colors.cardForeground, fontSize: t.fontSize.base }}>Hello</Text>
    </View>
  )
}

Colour names are the contract's, in camelCase (--color-card-foreground is cardForeground). NATIVE_THEMES holds every theme and mode at once, and THEME_NAMES lists them, for a theme picker. There is deliberately no useNativeTheme hook: it would pull react-native into this package. Wrap the call above in your own if you want one.

Make your own theme

From one brand colour:

import { buildTheme, toCss, toDesignTokens, toFigmaVariables } from "@dapplelight/signet-tokens/theme"

const theme = buildTheme({ brand: "#e11d48", base: "cinematic" }) // mode: "light" | "dark" | "both"
toCss(theme)            // a theme file: imports the base, overrides its colours in light and dark
theme.adjustments       // tokens moved to reach WCAG 4.5:1 (text) or 3:1 (focus, charts)
toDesignTokens(theme)   // W3C Design Tokens JSON; fromDesignTokens(json) reads it back
toFigmaVariables(theme) // body for Figma's POST /v1/files/:key/variables

Or signet theme "#e11d48" --base cinematic > src/brand.css, and import that file in place of the base theme. Every text token is checked against every surface it sits on, so a pale brand comes back darker in light mode, with the change listed.

By hand: copy a theme file, change the values, and keep every variable the contract lists. @dapplelight/signet-ui reads only these variables, so the components follow.

Density

data-density="compact" (or comfortable, spacious) on any element tightens or loosens the spacing of everything inside it. --density-button: 0.8 (and input, card, badge, ... see CONTRACT.md) on :root does it for one component everywhere. Nothing set means the theme's normal spacing, unchanged.

License

MIT