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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@haiilo/catalyst-tokens

v10.26.1

Published

Design tokens for Catalyst Design System

Downloads

2,930

Readme

Catalyst: Tokens

Tokens: build & test

This project contains all design tokens for the Catalyst design system.

Tokens are being transformed using Amazon Style Dictionary.

Style Dictionary is a build system that allows you to define styles once, in a way for any platform or language to consume. A single place to create and edit your styles, and a single command exports these rules to all the places you need them - iOS, Android, CSS, JS, HTML, sketch files, style documentation, or anything you can think of. It is available as a CLI through npm, but can also be used like any normal node module if you want to extend its functionality.

Getting started

Install @haiilo/catalyst-tokens in your Node.js powered apps with the npm package:

npm install @haiilo/catalyst-tokens

Contributing

If you want to add or update tokens in this repository, please make sure to adhere to the design token structure outlined at Design token structure.

Package management

This project is using npm as a package manager. This is especially important if you want to add new dependencies to a project and fail to provide an updated package-lock.json. This will cause the CI build to fail. If dependencies in the package lock do not match those in package.json, npm will exit with an error in the CI build, instead of updating the package lock.

Build

Run npm run build to build the project. The build artifacts will be stored in the dist directory. Artifacts will automatically be generated on the basis of the output configuration defined in config.js.

Publishing

The library can be published by running npm publish. However, the preferred way to publish a new version of the library is via the CI setup. A new version of the library will automatically be published to npm when pushing a new tag on the main branch. To simplyfy this process, you can use the following npm commands:

  • npm run release:major releases a new major version
  • npm run release:minor releases a new minor version
  • npm run release:patch releases a new patch version

These commands will automatically increase the version number in the package.json and package-lock.json, commit the changed files, create a corresponding git tag and push everything to the remote branch. This will then automatically publish a new library version.

License

The license is available within the main repository in the LICENSE file.