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

@prismforge/token-cli

v0.8.0

Published

CLI for validating, building, and exporting PrismForge tokens.

Readme

PrismForge CLI

Commands:

  • prismforge init [--mode <standalone|embedded>] [--layout <workspace|app-first>] [--embedded-path <path>] [--tokens-path <path>] [--studio-name <name>] [--dir <path>] [--provider <github|gitlab|bitbucket|generic>] [--repository <id-or-url>] [--base-branch <name>] [--targets <css,js,android,ios|all>] [--studio <true|false>] [--package-manager <pnpm|npm>] [--prompt] [--yes] [--install]
  • prismforge brand add --brand <id> [--modes <light,dark>] [--from <brand>] [--tokens-root <path>] [--force]
  • prismforge validate
  • prismforge build --brand <id> --mode <id> --target <css|js|android|ios|all>
  • prismforge diff --from <snapshot> --to <snapshot>
  • prismforge release --channel <stable|next|alpha|beta|rc|canary|custom> [--dist-tag <tag>]
  • prismforge figma export --brand <id> --mode <id>

Scaffold a self-hosted Token Studio

Interactive wizard:

npx @prismforge/token-cli init

Non-interactive:

npx @prismforge/token-cli init \
  --dir prismforge-studio \
  --studio-name "Acme Token Studio" \
  --provider github \
  --repository your-org/your-token-repo \
  --base-branch main \
  --targets css,js,ios \
  --studio true

Notes:

  • If run inside an existing git repo, init auto-detects provider/repository from origin.
  • --repository is optional. Leave it empty for new workspaces and set it later in .env.local.
  • Package manager is auto-detected (npm or pnpm) and can be forced with --package-manager.
  • --studio-name customizes the Token Studio header/title (default: PrismForge Token Studio).

Embedded mode (inside existing repo)

npx @prismforge/token-cli init \
  --mode embedded \
  --layout app-first \
  --embedded-path tools/prismforge \
  --tokens-path design-tokens \
  --package-manager npm

This keeps PrismForge inside your current project and adds helper scripts to your root package.json:

  • prismforge:install
  • prismforge:dev
  • prismforge:build
  • prismforge:test

Layout notes:

  • app-first (default for embedded): token source lives at project root (design-tokens/ by default).
  • --tokens-path lets you move token source anywhere in your host repo (for example tokens/design).
  • workspace: token source stays in tools/prismforge/packages/token-source.

Then run:

# from host project root
npm run prismforge:install
# copy tools/prismforge/apps/token-studio/.env.example to .env.local (inside tools/prismforge/apps/token-studio)
npm run prismforge:dev

Tokens-only scaffold (no Studio UI)

npx @prismforge/token-cli init \
  --dir prismforge-tokens \
  --targets ios \
  --studio false

Add your own brand

npx @prismforge/token-cli brand add \
  --brand acme-enterprise \
  --modes light,dark \
  --from acme

This creates semantic/component files for your brand in the detected token source root (design-tokens/src/tokens or packages/token-source/src/tokens).