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

@martinsura/ui

v0.1.14

Published

Minimal React UI component library built on Tailwind CSS v4

Readme

@martinsura/ui

React UI component library built on Tailwind CSS v4.

Development

Start the local preview app:

npm start

Build the library for publishing:

npm run build

Publishing Workflow

Source code lives in a private GitHub repository:

Publishing to npm is handled by GitHub Actions in publish.yml.

Push changes to GitHub only

If you want to save work to GitHub without creating an npm release, push only the branch:

git add .
git commit -m "Update components"
git push origin main

This does not publish anything to npm.

Publish a new npm version

  1. Update the version in package.json.
  2. Commit and push the branch.
  3. Create a Git tag with the same version prefixed by v.
  4. Push the tag.

Example for version 0.1.1:

git add .
git commit -m "Release 0.1.1"
git push origin main

git tag v0.1.1
git push origin v0.1.1

Important:

  • package.json version should match the tag version
  • example: package.json = 0.1.1, Git tag = v0.1.1
  • the npm publish runs only when the tag is pushed

Emergency local publish

If you ever need an emergency hotfix without waiting for GitHub Actions, you can publish directly from your machine:

npm run build
npm publish --access public

Important:

  • always bump the version in package.json first
  • npm does not allow publishing the same version twice
  • this should be used only as a fallback, not as the default release workflow

GitHub Actions Setup

Before the first npm release, add this repository secret in GitHub:

  • NPM_TOKEN

That token is used by the publish workflow to run:

npm publish