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

designmd-live

v0.1.3

Published

Live editor for DESIGN.md, wired on your real codebase

Downloads

472

Vulnerabilities

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

Links

Git

Maintainers

vianneybertrandvianneybertrand

Keywords

design-tokensdesign-systemdesign.mdtailwindtailwindcssdesign-toolsclilive-previewdtcg

Readme

designmd-live

Live editor for DESIGN.md — mounts as a Shadow DOM overlay on top of your real dev app.

Tweak the tokens of your DESIGN.md in a sidebar that lives inside your dev page, watch your actual app re-render. No iframe, no proxy, no design system rebuild, no reload.

Install

pnpm add -D designmd-live

Quick start

# 1. From your project root
npx designmd-live init        # creates DESIGN.md, wires the agent script tag

# 2. Start the overlay server (any spare terminal)
npx designmd-live dev         # http://localhost:3030

# 3. Run your normal dev server, e.g.
pnpm dev                      # http://localhost:3000

Open your normal dev URL (e.g. http://localhost:3000). A 420px sidebar appears on the left with your token tree, edits live-update the page, save persists DESIGN.md on disk.

init auto-detects Next.js App Router projects (src/app/layout.tsx) and inserts the dev-only script tag for you. It's idempotent: rerunning is a no-op if the tag is already present.

Manual wiring

If your project layout isn't auto-detected, add the snippet inside <body> in dev only:

{process.env.NODE_ENV === 'development' && (
  <script src="http://localhost:3030/client.js" async data-designmd-live />
)}

That's the only project-side change. Everything else stays untouched.

How tokens map to CSS

Tokens in your DESIGN.md are converted to CSS custom properties on :root, with the path joined by -:

| DESIGN.md | CSS variable | |---|---| | color.background | --color-background | | color.brand.500 | --color-brand-500 | | spacing.4 | --spacing-4 | | radius.lg | --radius-lg |

This matches Tailwind v4's @theme {} convention out of the box. If your project uses Tailwind v4, your tokens will already be exposed under matching variable names — the agent simply overrides them in a higher-specificity <style> block.

Flags

| Flag | Default | Notes | |---|---|---| | --port | 3030 | Port for the overlay server | | --cwd | process.cwd() | Where to read/write DESIGN.md |

Endpoints

  • GET / — plain text instructions for wiring the agent
  • GET /api/health — { ok: true }
  • GET /api/design-md — read & parse the current DESIGN.md
  • POST /api/design-md — write a new DESIGN.md (validated)
  • GET /client.js — the browser agent IIFE bundle (panel + inspector)
  • WS /ws — broker (panel ↔ target page)

Requirements

  • Node.js 24+
  • A project that uses CSS custom properties for design tokens. Tailwind v4 with @theme is the most direct fit; any framework that consumes :root { --foo: ... } will work.

License

MIT