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

@tumbaland/components

v1.15.0

Published

A shared React component library for Tumbaland frontend applications, built with TypeScript and Material-UI.

Readme

@tumbaland/components

A shared React component library for Tumbaland frontend applications, built with TypeScript and Material-UI.

Development

Running Storybook

Start the interactive component development environment:

npm run storybook:dev

Building Documentation

Building the Library

Compile TypeScript and create distribution files:

npm run build

Publishing the Library

  1. NPM Account: You need an NPM account with publish permissions
  2. NPM Token: Set up authentication token for automated publishing
  3. Organization: The package is published under @tumbaland scope

Authentication Setup

  1. Create an NPM token with publish permissions:

    npm login
    # or
    npm token create --read-only=false
  2. Set the token as an environment variable:

    export NPM_TOKEN=your_token_here
  3. Configure npm to use the token:

    echo "//registry.npmjs.org/:_authToken=\${NPM_TOKEN}" > ~/.npmrc

Publishing Process

The library uses standard-version for automated versioning and changelog generation. See the root README's "Commits & Releases" section for the full, authoritative process. Summary:

npm run release

This bumps version from conventional commits since the last components-v* tag, writes CHANGELOG.md, commits chore(release): X.Y.Z, tags it components-vX.Y.Z, builds, and publishes to npm with public access. Always release through this script — never hand-edit version and run npm publish directly, or the package, changelog, and tags drift apart.

Beta Release

npm run release:beta

This publishes a beta version (e.g., 1.0.0-beta.0) with the beta tag.

Manual Publishing Steps

If you need to publish manually:

  1. Build the library:

    npm run build
  2. Test the build:

    npm pack
    # Test the generated .tgz file in a test project
  3. Publish:

    npm publish --access public

License

MIT