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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@voys/design-tokens

v0.4.1

Published

The pipeline runs when all-tokens.json changes. Main is an unprotected branch. That is why we can use git push in the pipeline on main. A new tag (version) will be created with a patch. This will then be published to npm.

Readme

Design Tokens

Warning!

The pipeline runs when all-tokens.json changes. Main is an unprotected branch. That is why we can use git push in the pipeline on main. A new tag (version) will be created with a patch. This will then be published to npm.

Development

  1. If you don't have Node.js and npm installed, you can install them by following the instructions on the Node.js website.

macOS

For macOS, you can use Homebrew (if installed):

brew install node

Windows

For Windows, you can use the Node.js installer from the Node.js website.

Linux

For Linux, you can use the package manager of your distribution. For example, on Ubuntu:

sudo apt update
sudo apt install nodejs

0.1 Install dependencies

npm install

Developing the product

  1. First got to the folder of the project and run npm link
cd design-tokens
npm link
  1. Then go to project you want to test it in, e.g. conversations and "install" the package like so:
cd conversations
npm link @voys/design-tokens
  1. Go to the file you want to import the package and add the following
import { dark, light } from '@voys/design-tokens';

Publish a new version

Make sure you are logged in, use the spindle user within KeyHub to authenticate:

npm login

Bump the version accordingly and publish it to the NPM registry, make sure to git push the new version as well:

npm version <major | minor | patch>
npm publish
git push

Install the new version within the consuming project:

npm i -D @voys/design-tokens@latest

Run locally

After installing npm, generate the tokens files by:

npm run create-tokens