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

@waynestate/wayne-ui-tokens

v2.0.1

Published

Wayne State University design tokens. Brand color, type, spacing and motion, with WCAG contrast requirements declared alongside the values.

Readme

@waynestate/wayne-ui-tokens

Wayne State University's brand color, type, spacing and motion, as design tokens rather than hex values copied between projects.

This is part of Wayne UI, the design system for Wayne State C&IT and DSOE internal applications. If you are building for the public web, you want waynestate/base-site, not this.

Contrast is declared on the tokens, not hoped for

Colors are the Wayne State Identity Style Guide's, but each token that participates in a text or UI contrast requirement carries the requirement inline, under $extensions['wsu.contrast']: which token it is measured against, and the ratio it has to clear. For example, the default body text token declares a minimum of 7:1 against the default surface, AAA rather than merely AA, because body copy is what most of a page is.

That declaration is not decoration. The package's test suite reads every one of them, computes the real WCAG contrast ratio between the two tokens as built, and fails if any pairing misses its own stated minimum. A color change that quietly drops a pairing below what it promises does not ship; it fails pnpm --filter @waynestate/wayne-ui-tokens test. Copying a hex value out of a screenshot gives you none of that. This package gives you a value that has already been checked against the thing it sits next to, and stays checked every time either one changes.

The measured pairings ship too, so a consuming application can run the same check against its own combinations rather than trusting that a value looking right is a value that is right. contrastRatio() from the ./contrast export is the exact function the build itself uses, so an application computes contrast the same way rather than reimplementing WCAG's luminance maths slightly wrong.

Install

pnpm add @waynestate/wayne-ui-tokens

Use

The tokens come out in whatever format your build wants:

import tokens from '@waynestate/wayne-ui-tokens'
// { "green-400": "#0c5449", "gold-400": "#ffcc33", ... }
@import "@waynestate/wayne-ui-tokens/css";
/* --wsu-green-400: #0c5449; ... */
@import "@waynestate/wayne-ui-tokens/scss";
// $wsu-green-400: #0c5449;

The ./json export is the same tokens plus the measured contrastPairs, for anything that wants to inspect or re-verify the contrast data directly rather than trust the CSS or JS output. The ./contrast export is the WCAG contrast functions themselves, parseHex, luminance and contrastRatio, with no dependency on the rest of the package.

Most applications will not reach for this package directly. @waynestate/wayne-ui-css depends on it and re-exports the tokens as the CSS custom properties every Wayne UI component reads. Reach for this package on its own when you need the raw values, the contrast data, or the maths, in something other than CSS.

Documentation

Full token reference, including every ramp and every declared contrast pairing: https://wayneui.apps.wayne.edu/docs/