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

orbit-ds-variables

v1.0.4

Published

A centralized repository of design tokens and variables for the Orbit Design System, including colors, typography, spacing, sizing, and other foundational design primitives used across products and platforms.

Readme

# Orbit DS Variables

Design tokens exported from Figma (`tokens.json`), built with Style Dictionary and @tokens-studio/sd-transforms into **SCSS variables**, **CSS custom properties**, and **Tailwind maps** for colors and platform tokens.

Semantic theme colors keep their links to primitives (e.g., `{Green.400}` → `$green-400` / `var(--green-400)`).

---

## 🚀 Quick Start (Installation)

Install the design tokens into your project using npm:

```bash
npm install orbit-ds-variables

(Note: Whenever the design team publishes a new update, run npm install orbit-ds-variables@latest to get the freshest colors and spacing).


🎨 Usage

1. SCSS (Recommended)

Thanks to the bundled theme files, you do not need to manually import primitive colors. Just import the specific theme you want, and all base colors will come with it automatically.

/* Import your chosen theme bundle */
@use 'orbit-ds-variables/dist/scss/themes/d-grey' as *;

.my-card {
  /* You can now use variables directly with the $ symbol */
  background-color: $background-background;
  color: $green-400;
}

⚠️ Important Note on Multiple Themes: Do not import the master dist/scss/index file. Because different themes use the exact same variable names (like $text-primary), importing them all at once will cause them to overwrite each other. Always import one theme at a time!

💡 Tip: How to get SCSS Autocomplete in VS Code

By default, VS Code does not suggest SCSS variables from node_modules. To fix this and get a dropdown list of all your $tokens while typing:

  1. Open the VS Code Extensions tab.
  2. Search for and install SCSS IntelliSense (by mrmlnc).
  3. Give it a second to load. The next time you type $ in your file, VS Code will scan the @use path and show you all available design system variables.

2. Standard CSS / HTML

If you are using plain HTML and CSS, use the pre-bundled CSS file that includes both your primitive colors and your theme colors.

Option A: Link directly in HTML

<link rel="stylesheet" href="./node_modules/orbit-ds-variables/dist/css/themes/d-grey/index.css">

Option B: Import into your main CSS file

@import 'orbit-ds-variables/dist/css/themes/d-grey/index.css';

.my-card {
  background-color: var(--background-background);
  color: var(--green-400);
}

3. Tailwind CSS

Tailwind v4 (@theme example):

@import "tailwindcss";
@import "../node_modules/orbit-ds-variables/dist/css/themes/d-grey/index.css";

Tailwind v3 (theme.extend):

import colors from 'orbit-ds-variables/dist/tailwind/themes/d-grey/colors.js';

export default {
  theme: {
    extend: { colors },
  },
};

(Make sure to also import the CSS variables file in your app so the var(--...) tokens resolve properly).


📱 Platform Tokens (Web, Desktop, iPad)

Platform tokens hold your spacing, radius, typography, and component sizes.

SCSS:

@use 'orbit-ds-variables/dist/scss/platforms/web/variables' as web;

.container {
  padding: web.$gap-m;
  border-radius: web.$radius-s;
}

Tailwind v3:

import webTheme from 'orbit-ds-variables/dist/tailwind/platforms/web/theme.js';

export default {
  theme: {
    extend: webTheme,
  },
};

⚙️ How It Works (For Contributors)

  • scripts/split-tokens.mjs — Splits tokens.json into tokens/*.json per Figma collection.
  • scripts/build-tokens.mjs — Runs Style Dictionary to generate all final SCSS, CSS, and Tailwind formats.

To rebuild locally:

git clone [https://github.com/divyanshutomar78/Orbit-DS-Variables.git](https://github.com/divyanshutomar78/Orbit-DS-Variables.git)
cd Orbit-DS-Variables
npm install
npm run build:tokens

GitHub Automation

When tokens.json is updated from Figma/Tokens Studio and pushed to the main branch, a GitHub Action automatically runs the build script and updates the dist/ folder. The package can then be updated and published to npm.