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

@vettvangur/design-system

v2.0.78

Published

This package is a CLI that pulls design tokens and component metadata from a Figma file, then writes generated, framework-specific artifacts into your repo.

Readme

@vettvangur/design-system

This package is a CLI that pulls design tokens and component metadata from a Figma file, then writes generated, framework-specific artifacts into your repo.

It is not a runtime component library.

What It Does

  • Connects to the Figma API and fetches:
    • Variables (design tokens)
    • Components/component sets (for props/variants)
    • Effect styles (shadows/blur) referenced by nodes
  • Normalizes + groups tokens (for example colors are grouped by the first segment of the token key)
  • Emits deterministic, static output files (no runtime dependency on Figma)

What It Generates

From Figma Variables + Components it generates:

  • Tailwind v4 token CSS (via @theme) under styles/config/*.css (colors, typography, fonts, weights, shadows, scales, screens, sources)
  • Tailwind core CSS under styles/core/*.css (bodies, headlines, button variants)
  • Umbraco/Razor design-system partials under Views/Partials/<Namespace>/DesignSystem/*.cshtml
  • A top-level view at Views/<Namespace>DesignSystem.cshtml that composes the partials

Requirements

Figma access

  • FIGMA_TOKEN in the environment (falls back to FIGMA_KEY for older setups)
  • The token must have access to the target Figma file

Project config

The CLI reads vettvangur.config.mjs from the current working directory.

requited shape in vettvangur.config.mjs:

{
  ...rest of config
  figma: {
    key: process.env.FIGMA_KEY,
    file: "<figma-file-id>" 
  },
}