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

@designtools/studio

v0.1.23

Published

Visual editing CLI for design tokens, component variants, and Tailwind classes

Readme

@designtools/studio

Visual editing CLI for design tokens, component variants, and Tailwind classes. Proxies your app inside an iframe, injects a selection script, and lets you visually edit tokens, components, and instances — writing changes back to source files.

Install

npm install -g @designtools/studio

Usage

Start your dev server, then run the CLI in your project directory:

designtools-studio

Or use npx without installing:

npx @designtools/studio

The studio opens at http://localhost:4400 with your app proxied inside.

Options

--port <number>   Port your dev server is running on (default: 3000)
designtools-studio --port 5173

What you can edit

  • Tokens — CSS custom properties (colors, spacing, radius) at the system level
  • Components — CVA variant definitions (button sizes, badge styles, etc.)
  • Instances — individual component classNames in your source code

All changes are written directly back to your source files.

Supported styling systems

| System | Detection | |--------|-----------| | Tailwind CSS v4 | tailwindcss ^4 in package.json | | Tailwind CSS v3 | tailwindcss ^3 + config file | | Bootstrap 5 | bootstrap in package.json | | CSS Variables | --* custom properties in :root |

How it works

The CLI scans your project to detect the framework and styling system, starts an Express server that proxies your app, injects a selection overlay script, and serves a React SPA as the editing interface. Edits are regex-based find-and-replace operations on your source files — no AST parsing.

Part of @designtools

This package is part of the @designtools monorepo. See also @designtools/shadows for shadow-specific editing.

License

CC BY-NC 4.0 — free to use and modify for non-commercial purposes with attribution.