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

flourish-tokens

v1.0.19

Published

Tokens library for the Flourish design system.

Downloads

60

Readme

flourish-tokens

Design tokens package for the Flourish design system.

Installation

npm i flourish-tokens

Usage

CSS

To use css tokens globally, import the tokens stylesheets at the root level of your project. If you are using React, that means either at the index.js or App.js level like this:

import React from 'react'
import ReactDOM from 'react-dom/client'
import App from './App'
import 'flourish-tokens/tokens/css/_tokens.css'


ReactDOM.createRoot(document.getElementById('root')!).render(
  <React.StrictMode>
    <App />
  </React.StrictMode>,
)

You can then use the css variables defined in this package in your individual stylesheets like this:

body {
    background-color: var(--f-color-bg-dark);
}

SCSS

To use our scss tokens, import them inside your stylesheets like this:

@import 'flourish-tokens/tokens/scss/_tokens.scss';

You can then use our scss variables for our tokens like this:

body {
  background-color: $f-color-bg-dark;
}

We have big plans for our tokens library - including vending our tokens as javascript variables and more. Make sure you stay up to date with flourish-tokens for exciting new updates!

How our tokens work

High level Overview

We use Figma Tokens Studio to create our tokens. Figma Tokens Studio is a Figma plugin that allows you to define design tokens, it is a free alternative to the Figma Variables REST API, which we also explored. Tokens are defined in the plugin, used in our Figma design files, and then synced to our tokens package in code. This way, we maintain a single source of truth for our tokens, and changes in the tokens studio plugin will automatically reflect in Figma as well as in our code.

Steps:

  1. Define or change a token value in the Figma Tokens Studio plugin, this will update any place in our Figma where that particular token value is used.
  2. Commit this token change to our github repo.
  3. Pull any tokens changes to our local workspace, this will appear in the tokens.json file.
  4. Run npm run build, this does a couple of things - a. Use token-transformer to transform the tokens.json file into output.json, this is a different json structure needed for the next step. b. Use style dictionary to create a build, this transforms the output.json file into scss and css variables that show up in the tokens/scss/_tokens.scss and tokens/css/_tokens.css directories. We can now use this to publish these tokens as an npm package to be used in other projects. For now we are just using scss and css, but we have the option to output these tokens in any other format we would like, for instance - we could output these tokens into swift ios (.swift) or android (.xml) formats. All of this transformation configuration is configured inside of the config.json file. At the moment, we are only publishing our tokens as css in this npm package.