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

@mdwrk/ui-tokens

v1.3.1

Published

Shared package-owned CSS tokens, markdown class names, and theme mapping helpers for MdWrk packages.

Readme

@mdwrk/ui-tokens

Shared token defaults and class helpers

This package exposes the shared MdWrk markdown-package token defaults, markdown class contracts, bridge variables, and CSS custom-property helpers used by the portable markdown, renderer, and editor packages.

Why

Use it when you need the package-owned markdown token, class-name, and renderer/editor bridge contract directly without importing the full theme authoring surface.

What

  • Stable token names and defaults.
  • Stable markdown class names and renderer/editor bridge definitions.
  • CSS custom-property lists for the shared UI contract.
  • CSS defaults for markdown, renderer, and editor surfaces only.
  • Studio shell and application-chassis tokens now live in mdwrk-studio and should be consumed there through the studio-owned token package and @mdwrk/theme-contract.

Installation

Node.js 20.x through 22.x, matching the workspace engine contract in the root package manifest.

npm install @mdwrk/ui-tokens

Usage

import { MARKDOWN_PACKAGE_TOKEN_DEFAULTS } from "@mdwrk/ui-tokens";

console.log(MARKDOWN_PACKAGE_TOKEN_DEFAULTS["bg-panel"]);

Surface

  • Theme bridge helpers now cover renderer, editor, html, and pdf targets.
  • Use createHtmlThemeBridgeVariableRecord() and createPdfThemeBridgeVariableRecord() when exporting HTML or PDF-specific token bridges.
  • The bridge inventory continues to expose applicability through stable CSS custom-property contracts rather than app-shell selectors.

Related