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

@thegpvc/ui

v0.3.0

Published

GP Design System - Shared UI components for internal tools

Readme

TheGP Design System — @thegpvc/ui

Shared UI components for TheGP internal applications.

View Playground →

Quick Start

1. Install the package

npm install @thegpvc/ui

2. Configure your CSS

Add these lines to your app's main CSS file (e.g., src/index.css):

@import url('https://fonts.googleapis.com/css2?family=DM+Sans:ital,opsz,wght@0,9..40,400;0,9..40,500;0,9..40,600;0,9..40,700;1,9..40,400&family=JetBrains+Mono:wght@400;500&display=swap');
@import "tailwindcss";
@import "@thegpvc/ui/theme";
@source "../node_modules/@thegpvc/ui/dist";

Why each line matters:

  • @import "tailwindcss" — Base Tailwind utilities (your app provides this)
  • @import "@thegpvc/ui/theme" — GP design tokens (colors, fonts, component classes)
  • @source "..." — Tells Tailwind to scan our components so utility classes aren't purged

3. Use components

import { Button, Badge, Card } from '@thegpvc/ui'

function App() {
  return (
    <Card>
      <Card.Header>Welcome</Card.Header>
      <Card.Body>
        <Button variant="primary">Get Started</Button>
      </Card.Body>
    </Card>
  )
}

Vite Setup

Ensure your vite.config.ts includes the TailwindCSS plugin:

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import tailwindcss from '@tailwindcss/vite'

export default defineConfig({
  plugins: [react(), tailwindcss()],
})

Components

  • Button - Primary action buttons with variants (primary, secondary, ghost, destructive)
    • Sizes: sm, md, lg
    • Features: loading state, icon support
  • Badge - Status indicators with variants (success, warning, error, info, neutral)
  • Card - Content containers with compound pattern (Card.Header, Card.Body, Card.Footer)
  • StatCard - Metric displays with trend indicators (up/down)
  • Alert - Contextual messages with variants (info, warning, error, success)
    • Features: dismissible, title support
  • Skeleton - Loading states and skeleton screens
    • Includes: Skeleton, SkeletonText, SkeletonStatCard, SkeletonListItem

Icons

Common icons are re-exported from lucide-react for convenience:

import { Search, User, Mail, Calendar, Loader2, TrendingUp } from '@thegpvc/ui'

Note: Your app must have lucide-react installed as a peer dependency.

Utilities

cn() - ClassName Utility

Merge Tailwind classes with proper precedence:

import { cn } from '@thegpvc/ui'

<Button className={cn('extra-class', isActive && 'active-class')} />

Development

Developing gp-ui Itself

To work on the design system components:

# Install dependencies
npm install

# Build the library
npm run build

# Watch mode for development (rebuilds on file changes)
npm run dev

Running the Playground

The playground provides an interactive environment to view and test all components:

npm run playground

This starts a local dev server at http://localhost:5174 with hot reloading. To build the playground for deployment:

npm run build:playground

Using gp-ui in Your Project

For production use, install via your package manager (see Installation above). For local development with a linked version:

Using npm link

In the gp-ui directory:

npm link

In your project directory:

npm link @thegpvc/ui

To unlink:

# In your project
npm unlink @thegpvc/ui

# In gp-ui (optional cleanup)
npm unlink

Making Changes While Developing Another Project

Recommended workflow:

  1. Terminal 1 (gp-ui): Run npm run dev to watch for changes
  2. Terminal 2 (your project): Use npm link @thegpvc/ui dependency
  3. Make changes to components in gp-ui
  4. Watch mode automatically rebuilds
  5. Your project's dev server (Vite HMR) picks up the changes

Peer Dependencies

This package requires the following peer dependencies to be installed in your app:

{
  "react": ">=18.0.0",
  "react-dom": ">=18.0.0",
  "lucide-react": ">=0.400.0"
}

Design Guidelines

See DESIGN_GUIDE.md for:

  • Color usage guidelines
  • Typography scale
  • Spacing system
  • Component design patterns

Claude Code Integration

This library includes a Claude Code plugin that provides AI assistance when building UIs with @thegpvc/ui components.

Enable the Plugin

In Claude Code, run:

/plugin add github:thegpvc/gp-ui

What It Provides

The plugin gives Claude knowledge of:

  • All available components and their props
  • Design system colors, typography, and spacing
  • Icon exports and naming conventions
  • Setup and migration guidance

When building UIs, Claude will automatically use the correct components, variants, and patterns from @thegpvc/ui.