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

@vagarylabs/ui

v0.5.1

Published

Shared frontend system for Vagary Labs products and integrations.

Downloads

2,054

Readme

@vagarylabs/ui

The shared frontend system used across Vagary Labs products and integrations: primitives, design tokens, and layout components built on React 19, Tailwind CSS 4 and Radix UI.

MIT licensed. Trademarks are not included in that grant — see LICENSE.

Install

npm install @vagarylabs/ui

react, react-dom and tailwindcss are peer dependencies you already have in a React app.

motion is an OPTIONAL peer. Nothing in the package root imports it, so install it only if you use the @vagarylabs/ui/motion entry point:

npm install motion

Use

import { Button, Card, StatusPill } from '@vagarylabs/ui';

export function Example() {
  return (
    <Card>
      <StatusPill status="healthy" />
      <Button variant="primary">Continue</Button>
    </Card>
  );
}

Add the stylesheet after Tailwind in your own CSS, so the tokens and component styles are present and Tailwind scans this package for the utility classes it uses:

@import "tailwindcss";
@import "@vagarylabs/ui/styles.css";

Entry points

| Import | Contents | |---|---| | @vagarylabs/ui | components and hooks | | @vagarylabs/ui/motion | motion presets, Reveal, Presence, the reduced-motion config, and the components that animate — needs the optional motion peer | | @vagarylabs/ui/tokens | brand token presets and applyBrandTokens | | @vagarylabs/ui/cn | the cn class-merge helper | | @vagarylabs/ui/styles.css | design tokens and component styles | | @vagarylabs/ui/registry.json | the component registry, for copying source instead of importing |

Animated components

motion is an optional peer: nothing in the root entry point reaches it, so you only install it if you import @vagarylabs/ui/motion.

npm install motion
import { AnimatedOTPInput } from '@vagarylabs/ui/motion';

Every animated component honours prefers-reduced-motion.

Copy the source instead

Some teams would rather own the file than import it. registry.json is a shadcn registry whose items carry the component source inline as files[].content, so you can copy a component into your own codebase and change it freely — it is MIT either way. llms.txt is the same catalogue in plain text, for agents.

Each item's meta records where the component came from: whether it was written here or adapted from an upstream project, and for adapted ones the upstream URL, the exact commit, its licence and what we changed. THIRD_PARTY_NOTICES.md carries the upstream licence texts.

Versioning

Pre-1.0: the public surface is still settling, and minor versions may change it. Each release records its provenance in provenance.json and third-party attribution in THIRD_PARTY_NOTICES.md.