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

@devslab/dds-tokens

v0.13.0

Published

DDS (DevsLab Design System) design tokens — one JSON source, built for CSS, Tailwind, TypeScript/RN and Ionic

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jlc488jlc488

Keywords

design-tokensdesign-systemcss-variablestailwinddevslab

Readme

@devslab/dds-tokens

🌐 한국어

DDS design tokens, built from the single source at the repo root (tokens/*.json, W3C Design Tokens format) into every consumption shape (spec §2). pnpm build produces:

| Artifact | Import | Consumer | | --- | --- | --- | | dist/tokens.css | @devslab/dds-tokens/tokens.css | Every web surface. --dds-* custom properties — light on :root, dark on [data-theme="dark"] | | dist/tailwind/theme.css | @devslab/dds-tokens/tailwind/theme.css | Tailwind v4 (@theme) | | dist/tailwind/preset.js / .cjs | @devslab/dds-tokens/tailwind/preset | Tailwind v3 (presets: [...]) | | dist/tokens.ts (+ tokens.js / tokens.d.ts) | @devslab/dds-tokens | RN and any runtime code — raw numbers (px on web, pt on RN) | | dist/ionic.css | @devslab/dds-tokens/ionic.css | Ionic apps — --ion-* mapped onto --dds-*: brand color (primary + -rgb/-shade/-tint/-contrast), the three status colors with their -contrast, page background/text/border, font, and app chrome (item, toolbar, tab-bar, card) |

Usage notes

  • Load order. tokens.css first; theme.css / ionic.css reference its variables. Tailwind color utilities resolve through var(--dds-*), so they follow the theme at runtime.
  • Dark mode. Set data-theme="dark" on <html> (or any subtree — data-theme="light" pins a subtree back, so panels can be fixed to either theme). No media query is emitted; auto-follow is the consumer's call, same as devslab.kr's toggle.
  • The raw palette is not in the CSS. Components may only use semantic tokens (spec §3.1); what the CSS doesn't ship can't be hardcoded against. Palette values are available from tokens.ts for mapping-definition code.
  • Tailwind naming. Color names keep the semantic path: bg-bg-brand, text-text-primary, border-border-default. Flattening ("brand") would collide — color.bg.brand and color.text.brand are different values. Spacing is not overridden: Tailwind's default quarter-rem grid already equals the DDS 4px scale (p-1=4px … p-16=64px; DDS space.2 = p-0.5).

Scripts

  • pnpm build — Style Dictionary v4 resolves tokens/*.json; explicit formatters emit the artifacts (an unknown $type fails the build).
  • pnpm check — token JSON validation (leaf shape, reference resolution, light/dark parity, value shapes) + tsc --strict on the generated TS.

The repo-level pnpm verify additionally runs scripts/check-docs-sync.mjs, which fails CI when docs/design-system*.md or preview/index.html drift from the token values.