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

@ibis-design/css

v0.6.0

Published

Design tokens, CSS variables, and Tailwind preset for the IBIS design system.

Readme

@ibis-design/css

Design tokens as CSS custom properties, optional base CSS, and a Tailwind v4–compatible preset for the IBIS design system. Framework-agnostic; usable from any stack.

Installation

npm install @ibis-design/css

Usage

Brands / style sets

The package ships two style sets. The default entry is ibis; use explicit paths for alchemy:

| Import | Description | |--------|-------------| | @ibis-design/css or @ibis-design/css/ibis-design.css | IBIS design tokens (default) | | @ibis-design/css/alchemy-design.css | Alchemy design tokens | | @ibis-design/css/ibis-design.scss / alchemy-design.scss | SCSS variables for each brand |

Tailwind presets — Use the preset that matches the token CSS you load:

| Import | Description | |--------|-------------| | @ibis-design/css/tailwind.preset or @ibis-design/css/preset | IBIS preset (default) | | @ibis-design/css/ibis/tailwind.preset | IBIS preset (explicit) | | @ibis-design/css/alchemy/tailwind.preset | Alchemy preset |

CSS variables

Import the generated tokens in your CSS (or entry point) so that :root is populated with design tokens:

@import "@ibis-design/css";
/* or */
@import "@ibis-design/css/ibis-design.css";

All tokens are exposed as custom properties, for example:

  • --color-primary-500, --color-success-text, …
  • --spacing-1, --spacing-4, …
  • --font-sans, --font-size-base, …
  • --radius-sm, --radius-lg, …

Use them in your own CSS:

.card {
  background: var(--color-primary-50);
  padding: var(--spacing-4);
  border-radius: var(--radius-md);
  font-family: var(--font-sans);
}

Tailwind preset

Use the preset so Tailwind utilities (e.g. bg-primary-500, p-4, rounded-md) map to the same token values. Load the preset that matches the token CSS you use.

Ibis:

/** @type {import('tailwindcss').Config} */
module.exports = {
  presets: [require("@ibis-design/css/tailwind.preset")],
  content: ["./src/**/*.{html,js,ts,jsx,tsx,svelte,vue}"],
};

Alchemy:

presets: [require("@ibis-design/css/alchemy/tailwind.preset")],

Ensure the matching token CSS is loaded in your app (e.g. @import "@ibis-design/css/ibis-design.css" for ibis or @import "@ibis-design/css/alchemy-design.css" for alchemy) so that the var(--...) references resolve.

Tailwind v4 may use a different config or CSS-based theme; the preset shape is compatible with Tailwind v3. For v4, use the same preset via @config if supported, or import the tokens CSS and extend your theme with the same variable names.

Build

From the package directory (or from the repo root with npm run build:css):

npm run build

This runs Style Dictionary for each token set in src/tokens/ (e.g. ibis.json, alchemy.json) and writes per brand under dist/<brand>/:

  • dist/<brand>/<brand>-design.css:root block with all CSS custom properties
  • dist/<brand>/<brand>-design.scss — SCSS variables
  • dist/<brand>/tailwind.preset.js — Tailwind theme extend object that references those variables

Do not edit the files in dist/; they are generated. To change tokens, edit the JSON files in src/tokens/ and run npm run build again.

Token source

Tokens are defined in DTCG format in src/tokens/ (e.g. ibis.json, alchemy.json). The build is driven by src/scripts/build.ts and src/config/style-dictionary.config.ts. Style Dictionary reads the token JSON and emits CSS, SCSS, and the Tailwind preset. Other packages (e.g. Svelte, React Native) can consume the generated CSS or preset for consistent values.

Fonts

The tokens reference font families (e.g. Inter, Metrisch, Beyond Infinity). This package does not bundle or load font files. To get the intended typography, load the fonts in your app (e.g. via Google Fonts, a CDN, or self-hosted assets) and ensure the font names match the token values.