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

vue-harvest

v0.0.4

Published

Extract reusable component libraries and design tokens from any Vue application

Readme

vue-harvest

Extract reusable component libraries and design tokens from Vue applications.

Point it at a Vue project. It parses every .vue file, maps the dependency graph, classifies components by reusability, and auto-extracts the safe ones into standalone bundles. It also pulls out your design tokens (colors, typography, spacing) and generates a CSS token library.

Quick start

npx vue-harvest analyze ./my-vue-app

This creates a .vue-harvest/ directory with:

  • registry.json : machine-readable component registry
  • catalog.html : browsable catalog with tier filters
  • analysis.json : full analysis for the MCP server
  • SUMMARY.md : human-readable report
  • components/ : extracted component bundles

Commands

vue-harvest analyze [path]       # full analysis + auto-extraction
vue-harvest list [path]          # list components by confidence
vue-harvest inspect <name>       # deep-inspect a single component
vue-harvest extract <name>       # extract a component into a bundle
vue-harvest tokens [path]        # extract design system tokens
vue-harvest init                 # create harvest.config.json

Flags

| Flag | Commands | Description | |------|----------|-------------| | --threshold <n> | analyze | Confidence threshold 0-100 (default: 70) | | --output <dir> | analyze, extract, tokens | Output directory | | --json | analyze, list, inspect, tokens | JSON output to stdout | | --tier <tier> | list | Filter by tier | | --force | extract | Extract below threshold |

Component tiers

| Tier | Confidence | Meaning | |------|-----------|---------| | Primitive | 85-100% | Pure UI, no business logic | | Composite | 70-85% | Built from primitives | | Feature | 50-70% | Has business logic, potentially reusable | | Page-bound | 30-50% | Coupled to a specific route | | App-specific | 0-30% | Deeply coupled |

Programmatic usage

import { analyze, writeOutput, analyzeTokens } from 'vue-harvest'

const report = await analyze('./my-vue-app')
console.log(report.summary)
await writeOutput(report)

const tokens = await analyzeTokens('./my-vue-app')
console.log(tokens.palette)

Configuration

harvest.config.json (optional):

{
  "include": ["**/*.vue"],
  "exclude": ["node_modules/**", "dist/**"],
  "extractionThreshold": 70,
  "outDir": ".vue-harvest"
}

Path aliases are auto-detected from tsconfig.json.

MCP server

For AI-assisted extraction of harder components, see vue-harvest-mcp.

Full documentation

See the project README for complete docs on architecture, coupling issues, MCP tools, and internal workings.

License

MIT