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

bela-design-tokens-system

v0.2.0

Published

## How to use this design system

Downloads

1,465

Readme

bela-design-system

A repository for the files that describe the Bela design system for all front end technologies

How to use this design system

This will be exported as an npm package, so these files should only be edited by someone resolving the Figma and Style Dictionary versions.

Why everything is prepended by --ds

ds is short for "design system". All the variables are prepended with this, in order to disambiguate between variables created by this system, and other downstream variables that may apply.

This system is designed to be in sync with the documentation in Figma

One of the big problems right now, though Figma is great for prototyping, it isn't at all good at exporting actual code.

Click here for the Figma documentation of this system. Everything there is reflected in this system, so these components are straightforward to implement.

Omg why are there so many variables??

Don't worry, you don't have to use them all. In fact, a front-end developer will mostly be using the top-level component variables (those in /tier-3-components/).

The reason all the others exist is levels of abstraction - defining the variables, assigning them roles, and then collecting them into components. This is not redundancy - this is how this system remains ready to be applied to other systems and contexts that may not yet exist, and changes or updates can propagate through this system seamlessly and with little friction.

If you find errors/things look wrong or weird

Please open an issue in this repo, with the name of the component that needs to be fixed/defined/investigated.

WARNING!!!! Mever ever add or remove anything from these files without also resolving the same in Figma. This design system only works if it's perfectly in sync with Figma, and there is currently no automated way to do that. Bringing these files out of sync with Figma renders this system useless.

If this ever needs to be installed locally

In order to start Style Dictionary locally, do the following:

  1. In the root directory, start npm: $ npm init
  2. Install Style Dictionary as a dev dependency, meaning it won't ship with the final product: $ npm install -D style-dictionary
  3. Install Sass as a regular dependency: $ npm install sass
  4. Install Storybook as a dev dependency: $ npm install -D storybook
  5. Install Style Dictionary globally so we can use it in the command line: $ npm install -g style-dictionary
  6. Delete the build file (we're going to build it again)
  7. Run $ style-dictionary build to build the system. Now build contains _variables.css with all the values defined in the json files.