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

@gsa-tts/graymatter-style-tokens

v0.3.17

Published

## Package Responsibilities

Readme

@gsa-tts/graymatter-style-tokens

Package Responsibilities

The GrayMatter Style Tokens package (@gsa-tts/graymatter-style-tokens) is responsible for defining and managing foundational design tokens. These are named entities that store visual design attributes such as colors, typography, spacing, and more.

Primary Responsibilities:

  • Define and maintain design tokens (colors, typography, spacing, etc.)
  • Generate platform-specific token formats
  • Provide a single source of truth for design values
  • Ensure design consistency across applications
  • Bridge the gap between design tools (like Figma) and code

Package Boundaries:

  • SHOULD contain design token definitions
  • SHOULD contain token transformation and build logic
  • SHOULD export tokens in various formats (CSS, JS, JSON)
  • SHOULD NOT contain UI components or application logic
  • SHOULD NOT contain styling implementation (CSS/SCSS)
  • SHOULD NOT depend on UI components or application packages

Token Categories

The style tokens package includes the following categories of tokens:

  • Colors: Brand colors, UI colors, semantic colors
  • Typography: Font families, font sizes, font weights, line heights
  • Spacing: Margin and padding values
  • Breakpoints: Screen size breakpoints for responsive design
  • Borders: Border widths, radii, and styles
  • Shadows: Box shadows for different elevation levels
  • Z-indices: Z-index values for layering elements

Development

Adding or Modifying Tokens

  1. Edit the token source files in the src directory
  2. Run pnpm build to generate the token files
  3. Commit the changes

Building

pnpm build

This will:

  1. Compile the TypeScript configuration
  2. Run Style Dictionary to transform the tokens
  3. Generate the output files in various formats