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

@depthly/tokens

v0.1.0

Published

Depthly design tokens — DTCG sources, generated CSS variables, and base themes.

Vulnerabilities

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

Links

Git

Maintainers

stritarstritar

Keywords

design-tokensdtcgthemethemingcss-variablesdata-landscapedepthly

Readme

@depthly/tokens

The single source of styling truth for Depthly. Edit the DTCG JSON sources; everything else is generated. See the token-and-theming skill for the rules.

Layout

src/            DTCG token sources (edit these)
  core.*.json   tier 1 — primitives (color, scale, type, motion, 3D: light/camera/surface/grid)
  sem.json      tier 2 — semantic (the default = midnight; branding starts here)
  component.json tier 3 — per-visual tokens
themes/         user/AI-facing theme files (validated by `pnpm validate:theme`)
  midnight.theme.json   default dark base (identity — :root is already midnight)
  daylight.theme.json   light base (overrides; accent-derived tokens cascade automatically)
theme.schema.json       the contract a theme file must satisfy
scripts/        the build (DTCG -> CSS/TS/JSON, and themes -> scoped CSS)
generated/      build output (gitignored; published via package "files")

Build

pnpm --filter @depthly/tokens build

Produces:

  • generated/depthly.css — the :root cascade. References resolve to var() chains, so overriding a sem var re-skins everything downstream.
  • generated/tokens.json — fully-resolved literals ({ "--depthly-*": "value" }) for AI/tooling.
  • generated/tokens.js + .d.ts — export { cssVars, resolved } for TS consumers (the engine reads 3D params like --depthly-core-light-key-intensity from here / from computed styles).
  • generated/themes/<name>.css — [data-depthly-theme="<name>"] { … } per theme.

The build runs a WCAG contrast gate on foreground/background and terrain low/high; it exits non-zero if a default pair is illegible.

Using it

@import "@depthly/tokens/css";              /* :root defaults (midnight) */
@import "@depthly/tokens/themes/daylight.css"; /* opt-in light theme */
<div data-depthly-theme="daylight"> … visuals re-skin … </div>

Build-tool decision (interim)

We ship a small zero-dependency DTCG compiler (scripts/build-tokens.mjs) instead of wiring Style Dictionary 4 right now, so the token pipeline runs on plain node and is verifiable before pnpm install — matching tooling/scripts/. The DTCG sources are tool-agnostic, so migrating to Style Dictionary 4 later is a drop-in swap of the build script with no change to sources, themes, or output contract. CLAUDE.md still names Style Dictionary 4 as the eventual tool; this README is the documented interim decision.