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

@ikenga/tokens

v0.3.0

Published

Canonical design tokens for the Ikenga design system. CSS custom properties + TypeScript references. Shared by the shell and every UI pkg.

Vulnerabilities

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

Links

Git

Maintainers

nedjameznedjamez

Keywords

Readme

@ikenga/tokens

Version License

Canonical design tokens for Ikenga — one source of truth for the CSS custom properties the shell and every UI pkg share.

What it is

@ikenga/tokens is the design-system package consumed by the Ikenga shell and every UI pkg. It ships the full set of :root custom properties (dark default + light) plus TypeScript helpers, so a pkg mini-app looks native inside the shell without redefining a palette.

Install

pnpm add @ikenga/tokens

In the workspace, this is workspace:*.

Usage

CSS

Import once in your app's root stylesheet:

@import '@ikenga/tokens/tokens.css';

This defines the full set of :root custom properties for both data-mode="dark" (default) and data-mode="light". Toggle by setting the attribute on <html>.

TypeScript

import { setMode, applyHostStyles, MCP_UI_APPS_TOKEN_KEYS } from '@ikenga/tokens';

setMode('light');                               // flip mode
applyHostStyles(hostContext.styles.variables);  // apply incoming CSS vars from AppBridge

Token surface

  • Backgrounds: --bg-base, --bg-surface, --bg-raised, --bg-sunken
  • Foregrounds: --fg, --fg-muted, --fg-subtle
  • Borders: --border, --border-soft, --border-strong
  • Brand + semantic: --primary, --accent, --info, --success, --warning, --danger, --agent
  • Spacing: --space-{1,2,3,4,5,6,8}
  • Radii: --radius-{xs,sm,md,lg,xl,pill}
  • Typography: --font-{sans,display,mono}, --text-{caption,body,h3,h2,h1}
  • Shadows: --shadow-{1,2,3}
  • Tints: --tint-bg-active, --tint-fg-active
  • MCP UI Apps schema bridge: --color-{background,text,border,ring}-* mapped to the slots above

Why a workspace pkg

Pkgs run in isolated iframes and can't share the shell's stylesheet. Without a shared tokens source they'd vendor frozen approximations and drift the moment the shell evolves its palette. By importing @ikenga/tokens/tokens.css, every pkg picks up palette changes on its next build.

For live theme flips (user toggles dark/light at runtime), the shell additionally pushes a curated subset of these tokens to each pkg via the AppBridge host-context-changed notification — apply with applyHostStyles(). Tokens outside the MCP UI Apps schema allowlist (spacing, radii, typography, custom semantic slots) are picked up at build time only.

Links

License

Apache-2.0 — see LICENSE.