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

@element-software/ui.components

v0.1.0

Published

- Clone it - Remove the .git folder - Run `git init .` - Then run `git add .` - And finally run `git commit -m "First commit"`

Readme

Storybook, and Tailwind Component Library with TypeScript support.

To use this template:

  • Clone it
  • Remove the .git folder
  • Run git init .
  • Then run git add .
  • And finally run git commit -m "First commit"

Structure of the template

.
├── LICENSE
├── README.md
├── jest.config.js
├── package.json
├── postcss.config.js
├── public
│   ├── next.svg
│   └── vercel.svg
├── rollup.config.js
├── setup-tests.js
├── src
│   ├── assets
│   ├── components
│   ├── stories
│   └── styles
├── tailwind.config.js
└── tsconfig.json

Getting Started

First, install the packages:

npm install
# or
yarn install
# or
pnpm install

Then run the Storybook development server:

npm run storybook
# or
yarn storybook
# or
pnpm storybook

Open http://localhost:6006 with your browser to see the Storybook dev server.

You can start creating components or modifying existing ones and the changes will hot-reload and update in the browser.

Developing Components

Components are built in isolation and design to run on their own. To create a new component you should create a folder in the components folder named after the component e.g. Table, and the folder will have the below structure:

├── components
    └── Table
        ├── table.css
        ├── Table.spec.tsx
        ├── Table.types.ts
        └── index.tsx

The index.tsx file contains the component itself. Types for the component can be defined in Table.types.ts. Unit tests are written in Table.spec.tsx, and finally the table.css file contains the base Tailwind class imports, plus any additional CSS if required for the component.

Copy the below into your Table.css file:

@tailwind base;
@tailwind components;
@tailwind utilities;

Testing

After adding unit tests you can run npm run test:watch to run tests in watch mode. When testing you should consider what you are testing and why.