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

@tiny-design/tokens

v1.16.0

Published

Design tokens and v2 theme runtime for Tiny UI

Downloads

322

Vulnerabilities

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

Links

Git

Maintainers

wangdicoderwangdicoder

Keywords

Readme

@tiny-design/tokens

Design tokens and v2 theme runtime for Tiny Design.

Install

npm install @tiny-design/tokens
# or
pnpm add @tiny-design/tokens

Usage

CSS (recommended)

Import the compiled CSS to get all v2 token CSS variables:

import '@tiny-design/tokens';
// or explicitly
import '@tiny-design/tokens/css/base.css';

What's Included

| Module | Description | | --- | --- | | css/base.css | Package CSS entry copied from the base theme CSS | | dist/css/base.css | v2 light/dark/system theme CSS variables | | dist/css/light.css | Light theme CSS variables | | dist/css/dark.css | Dark theme CSS variables | | dist/registry.json | Token registry for tooling | | runtime/* | Theme presets, resolver, and validator runtime modules |

Theming

All visual tokens are delivered as CSS custom properties (--ty-*). Override them in your stylesheet:

:root {
  --ty-color-primary: #007bff;
  --ty-border-radius: 4px;
}

Light and dark themes are supported via the data-tiny-theme attribute on the document root:

<html data-tiny-theme="dark">

Three modes are available: light, dark, and system (follows prefers-color-scheme).

Component Token Conventions

Component tokens are scoped by component name and should not be shared across different components, even when the semantics line up closely.

For example, DatePicker and Calendar intentionally use parallel token groups without sharing the same key space:

  • date-picker.header-* and calendar.header-*
  • date-picker.panel-item-* and calendar.panel-item-*
  • date-picker.today-* and calendar.today-*

This keeps token semantics aligned across related components while allowing each component to evolve or be themed independently.

License

MIT