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

@whoisryosuke/react-music

v1.0.0

Published

Create code libraries using React, Typescript, and Vite to automatically release to NPM.

Readme

React Vite Library Boilerplate

Create code libraries using React, Typescript, and Vite to automatically release to NPM.

For example, you could create a component library for a design system (so someone can import { ComponentName } from 'your-custom-library').

Getting Started

Preview the code

  1. Clone this project: git clone [email protected]:whoisryosuke/react-vite-library-boilerplate.git
  2. Install dependencies: yarn
  3. Start the dev server: yarn dev

Open the app in your web browser: http://localhost:5174/

You can also install libraries like Storybook to preview UI components. See oat-milk-design for reference.

Write code

Write code in src/ and export any components, functions, etc in the index.ts.

Tips:

  • Installing a package? If you don't want to include it in the bundle, install it as a peer dependency and add it to the vite.config.js file and the build.rollupOptions.external array. You can see we do this with React - since we expect the user to bring their own copy.

Release

First time setup:

  1. Edit the package.json and change name to your module's name (anything-dash-separated). Then find and replace the old name with the new name (like the main or module properties).
  2. Go to the project settings and allow Read/Write access for Actions (Settings > Code and Automation > Actions > General - the Workflow permissions part of the page)
  3. Add your NPM_TOKEN as a repository secret for Actions. Make sure it's a "Granular access token" - the legacy type requires a one-time password (which doesn't work with this workflow).

Using GitHub:

  1. Run the new version GitHub action. This updates your package.json with the new version and creates a new tag on GitHub.
  2. Create a new release with the new version tag. This triggers a build that automatically gets pushed to NPM.

Or manually:

  1. Bump version in package.json
  2. yarn build
  3. npm publish
  4. Create new tag and release on GitHub.