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

@formtrieb/token-resolver

v0.3.0

Published

Tokens-Studio JSON → CSS variables, utility classes, SCSS mixins, and Figma↔CSS lookup map. Driven by a project-local config.

Downloads

386

Readme

@formtrieb/token-resolver

Tokens-Studio JSON → CSS variables, utility classes, SCSS mixins, and Figma↔CSS lookup map. Driven by a project-local config.

Install

npm install --save-dev @formtrieb/token-resolver

Your consumer project's package.json must have "type": "module" (this package is ESM-only). The CLI loads .ts, .mjs, and .js config files.

Quick start

Create formtrieb-tokens.config.ts in your project root:

import { defineConfig } from '@formtrieb/token-resolver';
import { typography, directional, container } from '@formtrieb/token-resolver/builders';

export default defineConfig({
  prefix: 'mp-',
  paths: {
    tokens: './tokens',
    output: './src/css',
    tokenMap: './src/tokens/token-map.json',
  },
  themeGroups: {
    Foundation: { useReferences: false },
  },
  defaultGroupBehavior: { useReferences: true },
  utilities: [
    typography(),
    directional({
      name: 'p',
      source: 'spacing.component.*',
      property: 'padding',
      sides: ['t', 'b', 's', 'e', 'x', 'y', 'all'],
    }),
    container({
      name: 'content',
      rules: {
        'max-width': '{content.max-width}',
        'padding-inline': '{layout.grid.margin}',
        'margin-inline': 'auto',
      },
    }),
  ],
});

Build:

npx formtrieb-tokens

Watch:

npx formtrieb-tokens --watch

Output

For the example above, the generator produces:

src/css/
  variables/
    foundation.css       (raw values; useReferences: false)
    mode.css             ([data-mode="…"] selectors)
    typography.css       (with text-indent, margin-block-end vars)
    …
  utilities/
    typography.css       (.mp-display-1, .mp-display-1--paragraph, …)
    p.css                (.mp-p-md, .mp-p-t-md, .mp-p-s-md, …)
    content.css          (.mp-content)
  main.css               (@imports of variables/* + utilities/*)
  bundle.css             (everything inlined for library consumers)
src/tokens/
  token-map.json         (figma↔css lookup map)

Builders

| Builder | Purpose | | ------------------ | --------------------------------------------------------------- | | single | One CSS property per token, one class per token. | | directional | Property with logical-axis sides (t/b/s/e/x/y/all), RTL-aware. | | container | Multi-rule class mixing token references and CSS literals. | | typography | Type-driven typography classes with --paragraph helper. | | typographyMixin | SCSS mixin partial — same data, different output format. |

Logical-Property Side Mapping (directional)

| Side | CSS | LTR | RTL | | ----- | ------------------------------ | ------ | ------ | | t | padding-block-start | top | top | | b | padding-block-end | bottom | bottom | | s | padding-inline-start | left | right | | e | padding-inline-end | right | left | | x | padding-inline | both | both | | y | padding-block | both | both | | all | padding | all | all |

For full builder API and design rationale, see docs/specs/2026-05-08-token-resolver-package-design.md.

Theme Switching

Multi-theme groups in $themes.json produce [data-{group}="{name}"] selectors automatically. Toggle a theme by setting the corresponding HTML attribute — no JS framework required:

<html data-mode="dark" data-device="mobile">

CLI Reference

formtrieb-tokens [options]

Options:
  -w, --watch              Re-run pipeline on tokens/ changes
  -c, --config <path>      Override config-file location
  -h, --help               Show usage

The CLI auto-discovers formtrieb-tokens.config.{ts,mjs,js} by walking from cwd up to the filesystem root.

Programmatic API

import { runPipeline } from '@formtrieb/token-resolver';
import config from './formtrieb-tokens.config.ts';

await runPipeline(config);
// or partial: await runPipeline(config, { only: ['utilities'] });

License

MIT