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

inkbridge-starter

v0.1.0

Published

A minimal Next.js + Tailwind CSS + Storybook project pre-configured with [Inkbridge](https://inkbridge.io) — so you can generate a pixel-accurate design system in Figma in minutes, without writing any components first.

Readme

Inkbridge Starter

A minimal Next.js + Tailwind CSS + Storybook project pre-configured with Inkbridge — so you can generate a pixel-accurate design system in Figma in minutes, without writing any components first.

What's included

  • Next.js 15 (App Router, TypeScript)
  • Tailwind CSS v4 + shadcn/ui components
  • Storybook with stories for every component
  • Inkbridge pre-wired — scanner route, token patch route, and scripts ready to go

Demo components

| Component | Type | |---|---| | Button | CVA variants (default / secondary / outline / ghost / destructive / link) + sizes | | Card | Compound (header / title / description / content / footer) | | Badge | CVA variants | | Input | States (default / disabled / invalid) | | Alert | CVA variants (default / destructive) | | Gradient Showcase | Gradient rendering demo (linear / radial / 3-stop / blob) |


Quick start

Prerequisites

  • Figma Desktop (not browser — needs localhost access)
  • Node.js 18+ and pnpm

1. Use this template

Click "Use this template""Create a new repository" on GitHub, then clone your new repo.

Or clone directly to try it out locally:

git clone https://github.com/inkn9ne/inkbridge-starter.git
cd inkbridge-starter
pnpm install

2. Load the plugin in Figma Desktop

  1. Open Figma Desktop
  2. Go to Plugins → Development → Import plugin from manifest...
  3. Select the file at:
    node_modules/inkbridge/manifest.json

Figma remembers this path — you only do this once per project.

3. Start the dev server

pnpm figma:dev

4. Generate your design system

In Figma: Plugins → Development → Inkbridge → Generate Design System Page

The plugin scans your Storybook stories and builds a "Design System" page with all components rendered as native Figma frames.


Adding your own components

  1. Create a component in src/components/
  2. Add a .stories.tsx file alongside it
  3. Re-run Generate Design System Page — it always reflects the current state

See the Inkbridge docs for full documentation.


Scripts

| Script | What it does | |---|---| | pnpm figma:dev | Start Next.js dev server (required for plugin) | | pnpm figma:scan | Manually run the component scanner | | pnpm dev | Start Next.js normally | | pnpm storybook | Start Storybook |


Configuration

Edit inkbridge.config.json to control which paths the scanner searches:

{
  "componentPaths": ["src"],
  "exclude": ["stories", "storybook-static"],
  "onlyWithStories": true
}

License

MIT