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

@dobuki/autocommit

v1.0.11

Published

[![npm version](https://badge.fury.io/js/@dobuki%2Fautocommit.svg)](https://www.npmjs.com/package/@dobuki/autocommit)

Downloads

64

Readme

autocommit

npm version

Bash script hooked up with npm for auto-committing changes into git. Just run one command, and all changes are committed immediately.

It comes up with a default non-descriptive message, so other devs get confused when they see your commit message with no context whatsoever.

Using autocommit in your project shows others that you're an 10x developer, who doesn't even bother wasting time manually committing your own code.

usage

execute:
$ ./autocommit.sh     # This commits all your code.

or

$ npm run autocommit

Run from npm dependency

First import dependency in your package.json:

  "devDependencies": {
    "@dobuki/autocommit": "^1.0.3"
  }

Then add a script to execute it:

  "scripts": {
    "tsc": "tsc",
    "autocommit": "npm explore @dobuki/autocommit -- npm run autocommit \"$(pwd)\"",
  }