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

@barrelrolla/react-components-library

v0.2.2

Published

Personal react components library

Readme

A react components library for personal use

A collection of react components for personal use.

How to use

Assuming you already have react and tailwind installed, install the package through npm:

npm install @barrelrolla/react-components-library

Ideally there should be a separate package for the tailwind plugin, but for the moment you have to export it yourself. Create a plugin.ts file in the same folder as your index.css or wherever you want and add the following in it:

import { Plugin } from "@barrelrolla/react-components-library";
export default Plugin;

In your .css file add

@import "tailwindcss";
@plugin "./plugin";
@source "../node_modules/@barrelrolla/react-components-library/";

This adds the tailwind plugin, so you can use the provided components and utilities and the @source directive is requred to use the pre-built components, otherwise tailwind won't recongnize the classes used in the library and won't build the styles for them.

Customization

Everything is built with tailwind so you can just use tailwind classes and utilities to style everything to your liking. To adjust the colors, simply override them like this:

:root {
  --color-main: #yourColor;
  --color-main-content: #yourColor;
  --color-primary: #yourColor;
  --color-primary-content: #yourColor;
}

No need to use dark:bg-dark just override the colors for dark mode:

.dark {
  --color-main: #yourDarkColor;
  --color-main-content: #yourDarkColor;
  --color-primary: #yourDarkColor;
  --color-primary-content: #yourDarkColor;
}

The library is adjusting the l value of the lch colors to lighten or darken components on hover:. If you want to use a color that's not from the color list, you can assign it to the --bg-color or --fg-color variable and retain the hover effects. Or you can provide your own.

<Button style={{ "--bg-color": "var(--color-red-500)" } as  CSSProperties}>
  button
</Button>

There is also a hover modifier variable --mod-highlight that's used to adjust the color's l value. You can modify that value to change the hover effect for all colors, or if a specific color needs adjustment, you can use --mod-highlight-primary or any other color name you want to override the value for that specific color.

For the full documentation, check the storyboard on github pages: Docs section.