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

@commercetools/nimbus-tokens

v2.9.1

Published

This package is the single source of truth for our design tokens.

Downloads

16,455

Readme

Design System Tokens Package

This package is the single source of truth for our design tokens.

Defining Tokens

All tokens are defined in src/tokens/base.json. All changes to the design tokens should occur in this file.

Token Format

Tokens in src/tokens/base.json are defined using a modified version of the W3C Design Tokens Community Group Token Definition Standard.

The version we use is somewhat modified to be more compatible with the Tokens Studio for Figma plugin. We specifically use a subset of unofficial tokens-studio-specific types. This enables for better token definitions in figma.

When adding tokens, define them using the DTCG spec, then upload them into the Tokens Studio plugin in Figma to make sure that they are defined as expeced in the figma file.

This process will be documented better as we start contributing changes to tokens.

Building Tokens

Once tokens have been added to src/tokens/base.json in the correct format and successfully updated in Figma, it is necessary to update them for all supported platforms: Typescript, CSS, and Chakra-specific (internal).

To update all platforms, run the following script from this directory:

pnpm build

This will update all tokens in src/generated.

Token Build Process

Tokens are transformed from the tokens stored in src/tokens/base.json using style-dictionary.

Style dictionary is configured in src/style-dictionary.config.js. Update this config file in order to change the formatting of any tokens in src/generated/*. See comments in that file for more information.

This process will also be better documented as we start distributing the tokens package for use in the design system.