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

wcommit

v1.3.1

Published

Commit prompt for Wizz repo

Downloads

36

Readme

Simple Wizz Commits

Simple commit prompt for Wizz repo

Just work on the task, add the changes and you're ready to commit. Push it if you want! The wcommit also handles the "--set-upstream" push.

The wcommit stores the data previously entered, so you don't have to re-enter it every time. If for some reason you don't want a commit to overwrite a previous state or you don't want to use the previous state, use the --no-store option.

Install

npm install -g wcommit

Useage

  1. develop => 2. git add => 3. run wcommit => 4. push (if you want)
wcommit

or

npx wcommit

Options

| Option | Description | | --------------- | ------------------------------------------------------------------------ | | -v, --version | Get current version | | -h, --help | Get options | | -c, --clear | Clear all stored commit parameters | | -a, --clear-all | Clear all stored data | | --no-store | Saved commit parameters are not loaded and new parameters are not saved. |

Examples

Clear all stored commit parameters from actual branch:

wcommit -c

Saved commit parameters are not loaded and new parameters are not saved:

wcommit --no-store

Store

Location:

# MacOs:
'/Users/<user>/Library/Preferences/wcommit-nodejs/config.json'