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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@blaze-money/kindling

v1.0.24

Published

Shared utilities for frontend and backend

Downloads

1,287

Readme

Kindling

Kindling is a shared utility library that provides common functionality used across Blaze's applications. It is published as an NPM package and serves as a core dependency for our main projects:

Publishing

This project uses automated semantic versioning and publishing to NPM through GitHub Actions. The process is triggered when a pull request is merged with one of the following labels:

  • patch - For backwards-compatible bug fixes
  • minor - For new backwards-compatible functionality
  • major - For breaking changes

How it works

  1. Create a pull request with your changes
  2. Add one of the version labels (patch, minor, or major) to the pull request
  3. When the pull request is merged, GitHub Actions will automatically:
    • Bump the version in package.json according to the label
    • Create a new git tag
    • Build the project
    • Publish the new version to NPM

Example

  1. You fix a bug and create a pull request
  2. Add the patch label to the pull request
  3. After the pull request is merged, the version will automatically bump (e.g., 1.0.01.0.1)
  4. The new version will be published to NPM

Requirements

  • NPM token must be configured in repository secrets as NPM_TOKEN
  • Pull request must have one of the version labels
  • User merging must have appropriate repository permissions