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

nirtz-test

v1.0.4

Published

Optimized template repository for React component libraries.

Downloads

7

Readme

react-component-library-boilerplate

Optimized template repository for React component libraries.

GitHub package.json version David Node.js CI CodeQL

Introduction

This template will give you a jumpstart on designing, testing, and publishing your very own React component library!

Click on the Use this template button to generate your own repository from this one.

Usage

Prerequisites

Commands

Run npm install first to install package dependencies.

  • npm start - Shortcut for npm run styleguide:serve
  • npm run lint - Run the StandardJS linter to check for warnings and errors
  • npm run build - Build the component library to the dist folder
  • npm test - Run the Jest testing suite to verify that the components will behave correctly
  • npm run storybook:serve - Run the Styleguidist server for component visualization
  • npm run storybook:build - Build a static Styleguidist site to the docs folder

Theme

Import the theme file in your application the apply the correct styling to all components.

import '~@matthewdowns/react-component-library-boilerplate/styles/theme.less';

Colors

Components that use colors will import the LESS variables defined in _colors.less.

#f0f0f0#f0f0f0 light

#353535#353535 dark

#aa55ff#aa55ff primary

#0088ff#0088ff secondary

#aaffff#aaffff info

#0be06b#0be06b success

#ffff03#ffff03 warning

#db3a35#db3a35 error

Publishing

Package publishing is handled automatically via GitHub Actions. You can view the publishing workflow here.

How to trigger the publish workflow

First, create a new branch - release/vx.x.x - and run the `npm version {major,minor,patch,etc.} command to update the package.json version automatically.

For example, if the lastest tag version is v1.0.4, then you would create a new branch off of main called v1.0.5, and then run npm version patch to upgrade the packge version from 1.0.4 to 1.0.5.

Please note that the package.json version should never include the "v" prefix, according to the semantic versioning specification. However, it does specifies that tags on GitHub or other version control systems can be prefixed with a "v".

After you've pushed the branch to GitHub, you can create a new release, where the Choose a tag dropdown lets you specify the tag version (remember to include a "v" prefix) as well as the target, which would be your release branch.

At this point, the publish workflow should be running - you can see the status of all actions on the repository here.

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Matthew Downs

Email: [email protected]

Twitter: @mdownsxy

Project Link: https://github.com/matthewdowns/react-component-library-boilerplate