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

@overclock/fuse-ui

v0.8.0

Published

FUSE UI registry and CLI: copy Vue components and their source into your project.

Readme

@overclock/fuse-ui

FUSE UI is a Vue 3 + TypeScript component registry. The CLI copies component source into your project; it is not a runtime UI dependency.

Copied components and composed sections live in ui/. Design tokens and CSS live in assets/css/. Each project can edit its own source independently. Existing files are preserved unless you explicitly pass --overwrite; use diff before applying upstream changes.

Requirements

  • Node.js >= 18
  • A Vue 3 project using Tailwind v4 and TypeScript

Quick start

# 1. Set up the project (design tokens in globals.css + cn() helper)
npx @overclock/fuse-ui init

# 2. Add the components you need
npx @overclock/fuse-ui add button input dialog

You can also install it globally:

npm i -g @overclock/fuse-ui
fuse-ui add button

Commands

| Command | Description | | ---------------------- | ------------------------------------------------------------------------------------------------------ | | init | Set up the project: design tokens (globals.css) and cn(). | | add <components...> | Copy one or more components from the registry into your project (dependencies resolved automatically). | | list | List every item available in the registry. | | diff [components...] | Show how your local components differ from the registry. |

Shared options

| Option | Description | | ----------------- | ------------------------------------------------------------------------------------------------- | | -d, --dir <dir> | Directory to copy files into. Defaults to resources/js, src, app, or the current directory. | | --no-install | Skip installing npm dependencies. | | --overwrite | Overwrite files that already exist. |

Examples

# List everything available
npx @overclock/fuse-ui list

# Add a few components
npx @overclock/fuse-ui add card badge avatar

# Add into a custom directory, without auto-installing deps
npx @overclock/fuse-ui add table --dir resources/js --no-install

# See what changed between your copy and the registry
npx @overclock/fuse-ui diff button

How it works

The CLI ships with the registry bundled. add resolves a component's registryDependencies (other components, utils, theme) and npm dependencies, copies the source files into your project, and installs the missing npm packages with your detected package manager.

Because you own the copied source, upgrades are opt-in: run diff to see what changed upstream, then re-add with --overwrite when you want to pull it in.

License

MIT