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

@daikin-oss/dds-tokens

v1.1.0

Published

Design token definitions for DDS

Downloads

2,697

Readme

dds-tokens

This package provides design tokens for the Daikin Design System (DDS) in multiple formats:

  • JS/TypeScript: ESM and CommonJS modules with TypeScript declarations
  • CSS: CSS custom properties (CSS variables)
  • SCSS: Sass mixins for flexible integration
  • Tailwind CSS v4: Theme files for Tailwind CSS integration
  • JSON: Token metadata for tooling and integrations

Available themes:

  • Brands: Daikin and AAF
  • Color schemes: Light and Dark mode for each brand

For the complete list of output files, check the build folder after installation.

Usage

Install package:

npm install @daikin-oss/dds-tokens

Import CSS

import "@daikin-oss/dds-tokens/css/daikin/Dark/variables.css";

or

@import url("@daikin-oss/dds-tokens/css/daikin/Dark/variables.css");

This imports all design tokens as CSS custom properties under the :root selector.

Import SCSS mixins

SCSS mixins require the SCSS compiler, but they provide flexibility in terms of where CSS variables are deployed.

Import all themes:

@use "pkg:@daikin-oss/dds-tokens/scss/mixins" as dds-tokens;

:root {
  @include dds-tokens.daikin-Light-variables;
}

:root[data-theme="aaf"] {
  @include dds-tokens.aaf-Light-variables;
}

@media (prefers-color-scheme: dark) {
  :root {
    @include dds-tokens.daikin-Dark-variables;
  }

  :root[data-theme="aaf"] {
    @include dds-tokens.aaf-Dark-variables;
  }
}

Import individual themes:

@use "pkg:@daikin-oss/dds-tokens/scss/daikin/Light/mixins" as daikin-Light;
@use "pkg:@daikin-oss/dds-tokens/scss/daikin/Dark/mixins" as daikin-Dark;

:root {
  @include daikin-Light.variables;
}

:root.dark {
  @include daikin-Dark.variables;
}

Tailwind CSS v4 Integration

This package provides Tailwind CSS v4 theme files that map DDS tokens to Tailwind CSS variables.

Common theme file (theme-agnostic)

The tailwind4.css file provides a theme-agnostic mapping that works with any DDS theme:

@import "@daikin-oss/dds-tokens/tailwind4.css";

This file uses @theme inline and references DDS CSS variables without fallback values. You must load a DDS theme CSS file separately to provide the actual token values.

Example:

@import "@daikin-oss/dds-tokens/css/daikin/Light/variables.css";
@import "@daikin-oss/dds-tokens/tailwind4.css";

Theme-specific files

You can also use theme-specific Tailwind CSS files that include fallback values:

@import "@daikin-oss/dds-tokens/css/daikin/Light/tailwind4.css";

Available files:

  • css/daikin/Light/tailwind4.css
  • css/daikin/Dark/tailwind4.css
  • css/aaf/Light/tailwind4.css
  • css/aaf/Dark/tailwind4.css

These files use @theme (not inline) with fallback values, allowing them to work standalone without requiring a separate DDS theme CSS file.

Variable mapping

DDS tokens are mapped to Tailwind CSS variables based on their token type:

  • color--color-dds-*
  • spacing--spacing-dds-*
  • borderRadius--radius-dds-*
  • borderWidth--border-width-dds-*
  • fontSize--font-size-dds-*
  • fontWeight--font-weight-dds-*
  • fontFamily--font-family-dds-*
  • lineHeight--line-height-dds-*

Example output:

/* Common file (build/tailwind4.css) */
@theme inline {
  --color-dds-color-blue-10: var(--dds-color-blue-10);
  --spacing-dds-space-100: var(--dds-space-100);
  /* ... */
}

/* Theme-specific file (build/css/daikin/Light/tailwind4.css) */
@theme {
  --color-dds-color-blue-10: var(--dds-color-blue-10, #ddf3fc);
  --spacing-dds-space-100: var(--dds-space-100, 4px);
  /* ... */
}

Import JS variables

// ESM
import { colorBlue10 } from "@daikin-oss/dds-tokens/js/daikin/Light/variables.js";

// CommonJS
const {
  colorBlue10,
} = require("@daikin-oss/dds-tokens/js/daikin/Light/variables.js");

Use JSON files

JSON files under json/ provide token metadata including types and values. These are primarily for internal use and tooling integrations.

Available files:

  • json/daikin/Light/tokens.json
  • json/daikin/Dark/tokens.json
  • json/aaf/Light/tokens.json
  • json/aaf/Dark/tokens.json

File structure: { "<token name>": ["<token value>", "<style-dictionary token type>", "<tokens-studio token type>" | null] }

Example:

{
  "color-blue-10": ["#ddf3fc", "color", null],
  "space-100": ["4px", "dimension", "spacing"]
}

Additionally, the source theme JSON files (located in themes/) are published in the same path within the package for advanced use cases.