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

@fingood/components

v0.1.280

Published

Fingood shared components

Readme

This library containts Ui components for Fingood React apps.

Available scripts

In the project directory you can run:

yarn dev

Starts the project for development.

yarn run build:package

Builds the app for packge publishing into dist/ folder.

Commit with commitlint

As this is npm package, we should want to generate changelog with every release. Changelog draws information from commits included in the release, so commit message quality ensures changelog comprehensibility and adds more semantic meaning to our git history.

Use git add . and yarn run commit to launch the commitlint cli.

You will be prompted to choose commit type. It can be one of these: ['feat', 'fix', 'docs', 'style', 'refactor', 'test', 'revert']. Type is required. The type feat must be used when a commit adds a new feature.

You can optionally fill in scope. It is a noun describing a section of the codebase. It is surrounded by parenthesis. It could be '(ui)', '(lang)', '(parser)', etc. There can be multiple scopes, which can be separated by ',', '/' or ''.

You can add ! after type or scope to draw attention to a breaking change.

Next, subject is required. This is a short summary of the code changes.

body and footer are optional, they enable multi-paragraph commit messages and are used to provide more context to commited changes.

Text in footer usually serves to warn about breaking changes - ideally concurrently with ! mentioned above. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g., BREAKING CHANGE: environment variables now take precedence over config files.

Example: fix(ui): Button was not showing up properly on mobile view Here the type is fix <==> a fix for a bug, the scope is ui as the fix was related to ui, and the subject provides more context about the issue.

Ready to publish to NPM?

The repo lives at https://www.npmjs.com/package/@fingood/components. You need to have an npm profile with 2FA enabled and be part of the Fingood organisation to be able to publish new versions there. Ask your FE colleagues to add you there.