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

@padiworks/padiworks-ui-system

v0.0.6

Published

A React project bootstrapped with **Vite**, styled using **TailwindCSS**, and documented with **Storybook**. Unit and component tests are handled with **Vitest** + **Storybook Addon Vitest**.

Readme

Padiworks System UI

A React project bootstrapped with Vite, styled using TailwindCSS, and documented with Storybook.
Unit and component tests are handled with Vitest + Storybook Addon Vitest.


🚀 Getting Started

1. Clone the Repository

git clone https://github.com/PadiWorks/Padiworks-ui-system.git
cd padiworks-system-ui

2. Install Dependencies

npm install

(or use yarn install / pnpm install if your team prefers)


🖥️ Development

Run the App

npm run dev

This starts the Vite dev server. Open http://localhost:5173 in your browser.

Run Storybook

npm run storybook

This launches Storybook on http://localhost:6006, where you can explore components in isolation.

We organize stories under src/stories/:

src/stories/
  button/
    Button.tsx
    Button.stories.ts

🧪 Testing

We use Vitest with Storybook’s Vitest addon for integration.

Run Tests

npm run test

Run Tests with UI (optional)

npm run test:ui

📂 Project Structure

project/
  ├─ .storybook/          # Storybook config
  ├─ public/              # Static assets
  ├─ src/
  │   ├─ components/      # Reusable React components
  │   ├─ stories/         # Storybook stories
  │   │   └─ button/
  │   │       ├─ Button.tsx
  │   │       └─ Button.stories.ts
  │   └─ App.tsx          # Main app entry
  └─ vite.config.ts       # Vite config

📖 Useful Commands

| Command | Description | |---------------------------|-------------------------------------------| | npm run dev | Start the Vite development server | | npm run build | Build the project for production | | npm run preview | Preview the production build locally | | npm run storybook | Start Storybook for component development | | npm run build-storybook | Build a static Storybook site | | npm run test | Run Vitest test suite |


🤝 Contributing

  • Keep components inside src/components/
  • Write stories for each component in src/stories/
  • Use consistent naming: ComponentName.stories.ts
  • Run npm run storybook to preview your stories before pushing

🛠️ Tech Stack

  • React 18 + Vite (fast dev/build tool)
  • TailwindCSS (utility-first styling)
  • Storybook (UI component explorer)
  • Vitest (unit + integration testing)
  • TypeScript (type safety)

📌 Notes

  • Make sure Node.js >= 18 is installed
  • Storybook stories must be placed under src/stories/ with the .stories.tsx or .stories.ts suffix
  • If you encounter issues with Node imports (path, url), ensure @types/node is installed