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

@tdacorp/signal-tokens

v0.1.1

Published

SIGNAL's design tokens as a versioned npm package: load it and stock shadcn components inherit SIGNAL automatically, no fork required.

Downloads

14

Readme

@tdacorp/signal-tokens

SIGNAL's design tokens (graphite ramp, electric-lime accent, both acts) plus the shadcn-over-SIGNAL alias bridge, as a versioned npm package. Load it and stock shadcn components inherit SIGNAL automatically, no fork required.

SIGNAL itself is defined in brand/architecture/brand-architecture.md in the TDACorp workspace. This package implements it; it does not own or redefine it.

Install

npm i @tdacorp/signal-tokens

Use

Import the barrel after your Tailwind entry, in your app's global CSS:

@import "tailwindcss";
@import "@tdacorp/signal-tokens/signal.css";

That one import chains through three layers:

| Layer | Import | Holds | |---|---|---| | Barrel (default) | @tdacorp/signal-tokens/signal.css | core + acts + shadcn, everything below | | Core | @tdacorp/signal-tokens/core.css | the raw ramp: colour, radius, motion, type faces | | Acts | @tdacorp/signal-tokens/acts.css | the --sig-* semantic layer, both acts | | shadcn bridge | @tdacorp/signal-tokens/shadcn.css | shadcn's variable names aliased onto --sig-* | | Compat (optional) | @tdacorp/signal-tokens/compat-unprefixed.css | bare --bg/--surface/… names, for a SIGNAL-native consumer; mutually exclusive with the shadcn bridge, not additive to it |

Once loaded, any stock shadcn component — installed with a plain shadcn add card, unforked — renders SIGNAL-styled, because it's already written against the variable names the shadcn bridge redefines (bg-card, text-muted-foreground, border-border, …).

Supply the two font variables yourself, via next/font or equivalent — this package wires the fallback stack but does not load the fonts:

// next/font/google, variable names matter: the tokens reference these exactly
const plexSans = IBM_Plex_Sans({ variable: "--font-plex-sans", ... });
const plexMono = IBM_Plex_Mono({ variable: "--font-plex-mono", ... });

Acts

Dark is the unconditional default. Invert any subtree, or the whole document, with:

<html data-act="light">

What this package deliberately does not do

  • Does not ship components. Signal's shadcn registry does that separately — see the signal repo for @signal/button, @signal/input, @signal/select, and the shared control-size map, the handful of genuine deltas tokens can't express.
  • Does not redefine --primary as the lime. It resolves to a neutral raised surface; the accent is reachable through an explicit accent variant on the components that define one. SIGNAL's own rule is that the accent is used surgically, never as a field.
  • Does not invent values. Every token here traces to products/tdacorp-site/src/app/globals.css, SIGNAL's canonical source, or is logged as a documented per-repo delta. Nothing is fabricated.

Versioning

Published versions are immutable once released. A token value changing is a version bump, picked up by any consumer on their own schedule — not a silent change to an already-built application.

License

Internal to TDACorp.