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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@o2project/design-system

v1.1.0

Published

Design system for O2 Project

Readme

design-system

Design system for O2 Project

🚀 Getting Started

This design system is built with Storybook and styled with Tailwind CSS.

Prerequisites

  • Node.js (version 18 or higher recommended)
  • npm

Installation

npm install

Development

Start the Storybook development server:

npm run storybook

This will start Storybook at http://localhost:15021

Build

Build a static version of Storybook:

npm run build-storybook

The static files will be generated in the storybook-static/ directory.

📦 Component Structure

Components are organized in the src/components/ directory with their stories collocated in the same directory:

src/
└── components/
    ├── Card/
    │   ├── Card.jsx          # Component implementation
    │   └── Card.stories.js   # Storybook stories
    ├── Button/
    │   ├── Button.jsx
    │   ├── Button.stories.js
    │   └── button.css
    └── ...

🎯 Creating New Components

  1. Create a new directory in src/components/ with your component name
  2. Add your component file YourComponent.jsx in that directory
  3. Style it using Tailwind CSS utility classes (or add a CSS file if needed)
  4. Create a story file YourComponent.stories.js in the same directory
  5. The component will automatically appear in Storybook

Example Component

import React from 'react';

export const Button = ({ label, variant = 'primary' }) => {
  return (
    <button className={`px-4 py-2 rounded ${variant === 'primary' ? 'bg-blue-500 text-white' : 'bg-gray-200'}`}>
      {label}
    </button>
  );
};

Example Story

import { Button } from './Button';

export default {
  title: 'Components/Button',
  component: Button,
};

export const Primary = {
  args: {
    label: 'Click me',
    variant: 'primary',
  },
};

🎨 Tailwind CSS

Tailwind CSS is configured and integrated with Storybook. You can use all Tailwind utility classes in your components.

📚 Documentation

Storybook automatically generates documentation for your components. Add JSDoc comments to your component props for better documentation:

/**
 * Primary UI component for user interaction
 */
export const Button = ({ 
  /** Button text */
  label,
  /** Visual style variant */
  variant = 'primary' 
}) => {
  // ...
};

🤝 Contributing

  1. Create a new component in src/components/
  2. Add Tailwind CSS classes for styling
  3. Create stories to showcase different states
  4. Test in Storybook
  5. Submit a pull request

📄 License

MIT