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

@vanduo-oss/core

v1.0.1

Published

Vanduo design-system source of truth — framework-agnostic design tokens (DTCG) for the Vanilla and Vue engines.

Readme

@vanduo-oss/core

The source of truth for Vanduo's design system — framework-agnostic design tokens shared by every engine:

  • framework (Vanilla — zero-build CDN / static / SPA)
  • vd2 (Vue 3 + SSR)

Both engines serve the same look, feel, and design philosophy (Open Color palette, Fibonacci scale). This package owns the values; each engine owns its own rendering. Zero runtime and zero build dependencies — the generator is plain Node.

Install

pnpm add @vanduo-oss/core
// TS / JS consumers (e.g. vd2)
import { PRIMARY_COLORS, NEUTRAL_COLORS, DEFAULTS, tokens } from "@vanduo-oss/core";
/* CSS consumers — :root { --vd-*: … } */
@import "@vanduo-oss/core/css";

| Export | Path | Contents | | --- | --- | --- | | . | dist/index.js + dist/index.d.ts | typed customizer arrays, DEFAULTS, resolved tokens map | | ./css | dist/vanduo-core.css | :root custom properties (--vd-*) | | ./tokens.json | dist/tokens.json | flat, resolved, Figma-ready token map |

What's here

tokens/                     # W3C DTCG source of truth (edit these)
  primitive/color.tokens.json    palette scales (Open Color)
  primitive/scale.tokens.json    spacing (Fibonacci), radius, type, shadow
  semantic/color.tokens.json     canonical --vd-color/bg/text/border-* aliases
  customizer/options.json        theme-customizer option metadata
scripts/
  extract-from-framework.mjs # one-time seed of palette from the framework CSS
  build.mjs                  # DTCG -> CSS + TS + JSON (zero dependencies)
  verify-parity.mjs          # assert primitives match the framework's values
dist/                       # generated (gitignored)
  vanduo-core.css            :root { --vd-*: … }
  index.js / index.d.ts      typed customizer data + resolved token map
  tokens.json                flat, resolved, Figma-ready

Develop

pnpm build     # regenerate dist/ from tokens/
pnpm test      # build determinism, token schema, ref integrity, parity (node:test)
pnpm verify    # assert dist parity with the Vanilla framework's authored values
pnpm extract   # re-seed primitive palette from ../framework (rarely needed)

The test suite is dependency-free (Node's built-in node:test). It checks that the build is deterministic, that the generated CSS exposes only --vd-* properties with no dangling var() references, that tokens.json is fully resolved, that the public API surface is intact, and that every customizer default points at a real option. The parity check runs when a framework checkout is available (sibling dir, or VANDUO_FRAMEWORK_DIR) and is skipped otherwise.

Scope & roadmap

Now: design tokens only. The vd2 Vue engine consumes the customizer token data from here instead of hardcoding it.

Deferred: the framework (Vanilla) engine consuming core's CSS (collapsing the two value sources so core becomes the singular truth); component specs; Figma variables generated from the DTCG tokens.json.

The Vanilla framework's colors.css/tokens.css remain the live values until that migration; pnpm verify guards against drift in the meantime.