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

@hpe-web/design-tokens

v2.0.0

Published

HPE Design System design tokens — CSS custom properties, DTCG 2025.10 source, locale overrides, and Style Dictionary transforms. Three-tier aliased architecture (primitive → semantic → component) preserved end-to-end as CSS var() chains.

Readme

@hpe-web/design-tokens

HPE Design System design tokens — CSS custom properties, DTCG source, locale overrides, and Style Dictionary transforms. Three-tier token architecture (primitive → semantic → component) preserved end-to-end as CSS var() chains.

What's new

2.0.0 — first release off the new Figma-REST pipeline

Token values now track current Figma directly (Supernova retired). Font sizes, line-heights, spacing, and non-heading vars from 1.3.1 are unchanged — but there are breaking changes, so review before upgrading:

  • ⚠️ Breaking — heading .default removed. All --hpe-web-heading-h{1..6}-default-* properties are gone; Figma split heading styles into light/medium. Migrate --hpe-web-heading-h2-default-font-size…-h2-light-font-size (or -medium-).
  • All component families now ship. card, marquee, logo, live-player, content-block, global-nav join button (23 new), e.g. --hpe-web-card-layout-gap-x, --hpe-web-marquee-gap-y.
  • Full dark-theme coveragetokens.dark.css grows 67 → 258 vars (component states, backgrounds, gradients now resolve in dark mode).
  • A few value updates from current Figma: critical red and primary-strong green darkened a step; button-link rest/hover color states + hover weight refined; radius-full now aliases a static.
  • Token names lose spaces (content blockcontent-block), and the DTCG source path src/component/button.jsonsrc/component/component.json. CSS consumers are unaffected by both.

Font-size (rem), line-height (unitless ratio), letter-spacing (em), and spacing are emitted exactly as in 1.3.1.

Full changelog →


Install

npm install @hpe-web/design-tokens

Usage

CSS (recommended)

Load the base file and any overrides your app needs. The cascade handles viewport, theme, and locale simultaneously.

<!-- Required -->
<link rel="stylesheet" href="node_modules/@hpe-web/design-tokens/css/tokens.css">

<!-- Optional -->
<link rel="stylesheet" href="node_modules/@hpe-web/design-tokens/css/tokens.dark.css">
<link rel="stylesheet" href="node_modules/@hpe-web/design-tokens/css/tokens.md-lg.css">
<link rel="stylesheet" href="node_modules/@hpe-web/design-tokens/css/tokens.xl.css">

<!-- Locales (if your app serves multiple languages) -->
<link rel="stylesheet" href="node_modules/@hpe-web/design-tokens/css/locales/de.tokens.css">
<link rel="stylesheet" href="node_modules/@hpe-web/design-tokens/css/fonts/de.css">

| File | Contents | Applied when | |------|----------|-------------| | tokens.css | All tokens — xs-sm base, light theme | Always | | tokens.dark.css | Dark theme color overrides | [data-theme="dark"] | | tokens.md-lg.css | Typography + border-radius overrides | @media (min-width: 992px) | | tokens.xl.css | Typography + border-radius overrides | @media (min-width: 1600px) | | locales/{lang}.tokens.css | Font-size + font-family overrides | [lang="xx"] | | fonts/{lang}.css | @font-face declarations | Always (locale-specific) |

Then use tokens in your CSS:

.card {
  background:    var(--hpe-web-color-background-card);
  padding:       var(--hpe-web-space-medium);
  border-radius: var(--hpe-web-border-radius-medium);
  font-size:     var(--hpe-web-text-medium-font-size);
}

No breakpoint logic needed in component CSS. Token values shift automatically as viewport, theme, and lang attributes change.

Dark mode:

<body data-theme="dark">…</body>

Locale switching:

<html lang="de">…</html>

Token audit workflow (Figma parity + 1:1 mapping)

When auditing component styles against Figma, use this workflow to guarantee Light/Dark parity and one canonical mapping per variable.

  1. Start from Figma variables for both Light and Dark modes.
  2. Resolve each variable to DTCG source in src/primitive, src/semantic, or src/component.
  3. Validate the generated CSS property in docs/tokens/token-mapping.doc.md.
  4. Enforce canonical 1:1 mapping: one Figma variable maps to one CSS custom property.
  5. Enforce mode parity for colors: semantic aliases must exist in both color.light.json and color.dark.json.
  6. Record unresolved gaps in docs/tokens/missing-tokens.doc.md with:
  • Light value
  • Dark value
  • Canonical target CSS property
  • Mode coverage status (Light only, Dark only, Light+Dark missing)

Audit Definition of Done:

  • Every Figma variable used by a component has exactly one canonical CSS property.
  • Every color variable has Light and Dark semantic coverage.
  • Component CSS uses canonical token variables only (no raw fallback values for tokenized properties).
  • Missing token backlog has no unresolved rows for the audited component.

Static metadata

All three metadata files live in static/:

import breakpoints from '@hpe-web/design-tokens/src/breakpoints.json' assert { type: 'json' };
// { values: { xs: '0px', md: '992px', xl: '1600px' },
//   ranges: { 'md-lg': { mediaQuery: '(min-width: 992px)' }, ... } }

import locales from '@hpe-web/design-tokens/src/locales.json' assert { type: 'json' };
// locales.de.coefficient.display === 0.75
// locales.ja.minFontSize === '14px'

import fonts from '@hpe-web/design-tokens/src/fonts.json' assert { type: 'json' };

breakpoints.json is generated from DTCG token values at build time. fonts.json and locales.json are hand-maintained. All three are for tooling and pipeline scripts — the browser gets everything it needs from the CSS files.

Bring your own Style Dictionary

For custom output formats (AEM, native, SCSS), run your own SD pipeline against our DTCG source:

import StyleDictionary from 'style-dictionary';
import { lineHeightUnitless, letterSpacingEm } from '@hpe-web/design-tokens/transforms';

const sd = new StyleDictionary({
  source: [
    'node_modules/@hpe-web/design-tokens/src/primitive/primitives.json',
    'node_modules/@hpe-web/design-tokens/src/semantic/color.light.json',
    'node_modules/@hpe-web/design-tokens/src/semantic/dimension.xs-sm.json',
  ],
  platforms: { /* your config */ },
});

sd.registerTransform(lineHeightUnitless);  // px line-height → unitless ratio
sd.registerTransform(letterSpacingEm);     // px letter-spacing → em

await sd.buildAllPlatforms();

See src/hpe.resolver.json for the canonical token load order.

Locale metadata for custom pipelines:

import locales from '@hpe-web/design-tokens/src/locales.json' assert { type: 'json' };
// locales.de.coefficient.display === 0.75
// locales.ja.minFontSize === '14px'

Package Contents

| Export | What | |--------|------| | @hpe-web/design-tokens/css/* | CSS custom properties (primary format) | | @hpe-web/design-tokens/src/* | DTCG source + system metadata (breakpoints.json, locales.json, fonts.json) | | @hpe-web/design-tokens/transforms | SD transforms + applyLocale utility |

License

Proprietary — Hewlett Packard Enterprise