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

commitr

v1.1.5

Published

A background script that automatically makes between 3 and 13 random Github commits in a dummy repo per day (to keep commit counts high).

Downloads

35

Readme

Commitr

commitr downloads commitr downloads

Commitr is a local background script that makes a random number of Github commits once a day. This keeps your Github commit chart nice and green, even if you need to work on other things - like a frantic job search.

Installation

  1. Create a folder in your root directory (~) called 'new_projects'
  2. Create a folder inside 'new_projects' called 'projects'
  3. Create a file inside 'projects' called 'test.txt'
  4. From inside your 'new_projects' folder, do a git init and then push the repository up to your Github account

Then either:

npm install

  1. From inside your 'new_projects' folder, do an npm init -y
  2. npm install commitr
  3. cd node_modules/commitr
  4. npm start

or

clone install

  1. From inside your 'new_projects' folder, use the command git clone https://github.com/dainchatel/commitr.git
  2. cd commitr
  3. npm start

Commitr will then run in the background on your machine.

To stop it, run npm stop. If you stop it, it's important to run npm run-script clear before you restart, or it may try to create files that already exist or delete ones that don't.

Issues

  • You must open your computer once a day for this locally-running script to work. Be sure to check Github so you know your commits are going through.
  • Commitr has not yet integrated Upstart, so it needs to be cleared and restarted after the computer is turned off.
  • Commitr could be made more simple by incorporating the Commander plugin, so users can flag their own repository path from the command line instead of creating the exact file path necessary.

Disclaimer

Commitr uses the child_process module to access your command line. Open the commitr.js file before you start the script so you can see exactly what commands it will call. Giving this kind of control to a file you downloaded can be dangerous.

Author

Dain Chatel

website | linkedin | github

Open Source

Fork and Clone this repository to submit a Pull Request