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

@florid-kit/tokens

v0.1.17

Published

Tokens This project takes input from the export-tokens package in the form of the tokens.json file and creates CSS and SCSS variables out of it.

Readme

Tokens This project takes input from the export-tokens package in the form of the tokens.json file and creates CSS and SCSS variables out of it.

It uses Style Dictionnary for converting json to CSS, and SCSS, so export could be done to any number of platform.

Out of the doc: Style Dictionary is a build system that allows you to define styles once, in a way for any platform or language to consume. Updating tokens Currently the source of truth for tokens is located in Figma, so you have to export variables from Figma and replace the ./tokens.json file with the output, and the build the tokens with pnpm nx build @bloom-kit/tokens. It will output new css and scss files for each brand.

How it works Take a look at the ./src/index.mjs file, which is roughly preparing the data to pass it onto ./src/token-builder.mjs which abstracts style dictionary.

It's also here that the layers (primitives, semantic, components), as well as themes for each brands are configured. The components package, appart from switching theme in the storybook code, should be completely theme/brand agnostic.