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

@appdirect/ad-design-tokens

v0.0.10

Published

AppDirect design token source and distribution artifacts.

Readme

@appdirect/ad-design-tokens

AppDirect design tokens for frontend applications.

Install

npm install @appdirect/ad-design-tokens

Available Exports

  • Resolved semantic tokens:
    • @appdirect/ad-design-tokens/semantic/light
    • @appdirect/ad-design-tokens/semantic/dark
  • Resolved component tokens:
    • @appdirect/ad-design-tokens/components/light
    • @appdirect/ad-design-tokens/components/dark
  • Resolved token outputs (per layer):
    • @appdirect/ad-design-tokens/resolved/core.json
    • @appdirect/ad-design-tokens/resolved/open-color.json
    • @appdirect/ad-design-tokens/resolved/derived.json
    • @appdirect/ad-design-tokens/resolved/semantic-light.json
    • @appdirect/ad-design-tokens/resolved/semantic-dark.json
    • @appdirect/ad-design-tokens/resolved/components-light.json
    • @appdirect/ad-design-tokens/resolved/components-dark.json
  • Figma / Tokens Studio (DTCG JSON with {ref} aliases intact):
    • @appdirect/ad-design-tokens/figma/open-color.json
    • @appdirect/ad-design-tokens/figma/core.json
    • @appdirect/ad-design-tokens/figma/derived.json
    • @appdirect/ad-design-tokens/figma/semantic.light.json
    • @appdirect/ad-design-tokens/figma/semantic.dark.json
    • @appdirect/ad-design-tokens/figma/components.light.json
    • @appdirect/ad-design-tokens/figma/components.dark.json
    • @appdirect/ad-design-tokens/figma/$themes.json (Tokens Studio theme manifest)
  • CSS variables:
    • @appdirect/ad-design-tokens/css/foundations.css (semantic tokens only — base for framework adapters)
    • @appdirect/ad-design-tokens/css/mantine.css (Mantine adapter — component selectors referencing --ad-* vars)
    • @appdirect/ad-design-tokens/css/tokens.css (foundations + component tokens — full monolith for vanilla consumers)
    • @appdirect/ad-design-tokens/css/open-color.css (--ad-open-color-* palette)
  • Design docs adapter:
    • @appdirect/ad-design-tokens/design-spec.yaml (resolved YAML payload for syncing DESIGN.md front matter in ad-design-system)
  • JS entrypoint:
    • @appdirect/ad-design-tokens (full resolved bundle)

Usage

Figma via Tokens Studio

Point Tokens Studio at dist/figma/ in the published package. The $themes.json manifest groups the layer files into two themes (Light, Dark) so Tokens Studio creates the following Figma variable collections on import:

| Collection | Modes | |---|---| | Tokens / Open-Color | Value | | Tokens / Core | Value | | Tokens / Derived | Value | | Tokens / Semantic | Light, Dark | | Tokens / Semantic Brand | Value | | Tokens / Components | Light, Dark |

Interactive states (hover, active, focus, disabled) are intentionally excluded from the Figma export — they are code-side concerns. Figma binds the default/resting state only.

Resolved JSON imports

import semanticLight from '@appdirect/ad-design-tokens/semantic/light' with { type: 'json' };
import componentsDark from '@appdirect/ad-design-tokens/components/dark' with { type: 'json' };
import resolvedCore from '@appdirect/ad-design-tokens/resolved/core.json' with { type: 'json' };

CSS variables — vanilla consumers

import '@appdirect/ad-design-tokens/css/tokens.css';

CSS variables — palette only

import '@appdirect/ad-design-tokens/css/open-color.css';

CSS variables — Mantine adapter

Import after @mantine/core/styles.css so the adapter's higher-specificity selectors win:

import '@mantine/core/styles.css';
import '@appdirect/ad-design-tokens/css/foundations.css';
import '@appdirect/ad-design-tokens/css/mantine.css';
.button {
  background: var(--ad-color-brand-primary);
  color: var(--ad-color-brand-on-primary);
}

JS entrypoint

import tokens from '@appdirect/ad-design-tokens';

console.log(tokens.semantic.light.color.bg.default.$value);