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

@mjpvs/agentic-component-library-test

v1.4.0

Published

[![npm](https://img.shields.io/npm/v/@mjpvs/agentic-component-library-test)](https://www.npmjs.com/package/@mjpvs/agentic-component-library-test) [![Test Coverage](https://img.shields.io/badge/coverage-100%25-brightgreen)](https://github.com/your-org/your

Readme

React Component Library

npm Test Coverage

A modern React component library built with TypeScript, Storybook, and Vitest. Generated entirely agentically as a learning experiment to explore automated component library creation.

Features

  • Component Library - Collection of reusable React components
  • Design Tokens - Centralized design system with colors, typography, spacing, and more
  • Storybook - Component documentation and visual testing
  • Vitest - Fast unit testing with React Testing Library
  • Semantic Release - Automated versioning and npm publishing
  • Conventional Commits - Enforced commit message format

Available Scripts

# Development
npm run dev              # Start Vite dev server
npm run storybook        # Start Storybook on port 6006

# Building
npm run build            # Build library (tokens + bundle + types)
npm run build:tokens     # Generate design tokens only
npm run build-storybook  # Build static Storybook

# Testing
npm test                # Run tests in watch mode
npm test run            # Run tests once
npm test run --coverage # Run tests with coverage report

# Publishing
npm run commit          # Interactive commit (commitizen)
npm run release         # Run semantic-release (manual)

Components

Layout

  • Box - Base container component
  • Flex - Flexible layout with direction, justify, align, gap
  • Grid - 12-column grid system with span and start props
  • Container - Responsive max-width container

UI

  • Button - Primary, secondary, outline variants; small, medium, large sizes
  • Card - Content container with optional title and padding
  • Heading - Levels 1-6

Media

  • Video - YouTube embed with aspect ratio options

Design Tokens

Tokens are defined in tokens/design-tokens.json and generate CSS variables in src/tokens/_variables.css.

Categories:

  • Colors (primary, gray, white, black)
  • Typography (family, size, weight, line-height)
  • Spacing
  • Border radius
  • Shadows
  • Transitions

Publishing

The project uses semantic-release for automatic versioning:

  1. Create a commit with a conventional commit message:

    npm run commit
    # Or: git commit -m "feat: add new component"
  2. Push to main branch

  3. CI/CD runs tests and publishes to npm

Tech Stack

  • React 18+
  • TypeScript 5+
  • Vite
  • Storybook 8
  • Vitest
  • CSS Modules
  • Style Dictionary
  • Semantic Release

License

MIT