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

cwsn

v1.0.3

Published

commit with story number

Downloads

1

Readme

Commit with prefix

Simple CLI tool built for personal use

Motivation :

In my current work assignment, there is a practice to add a certain prefix in the commit message based on the feature that we are working on. This prefix is then used to track the work around that feature.

If we put a wrong prefix in the commit message then it won't be able to track that commit for that specific feature.

I tended to mess up this prefix a couple of times. And hence decided to build this tool to rectify that.

Installation :

This tool can be installed using npm i -g cwsn

cwsn stands for commit with story number

Usage :

There are four flags - -i, -v, -m

cwsn -i <prefix> : This will instantiate the commit prefix.

cwsn -v : This will show the currently set commit prefix.

cwsn -m <message_without_prefix> : This will commit the message along with the prefix automatically.

cwsn -h : This will show how this tool can be used.

Common problem

If the command does not work due to the error node not found, follow the below steps:

  1. Run the command which node to find the current node executable path in your machine.
  2. Then run the command cp <current_path> /usr/local/bin/node

This will resolve the problem being faced.

Considerations :

The prefix message has to be initialised again on machine startup as it will be lost when the machine is shut down.