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

git-precheck

v0.2.1

Published

Run pre-commit checks before making commits to projects

Downloads

5

Readme

git-precheck

Installation

$ npm install -g git-precheck

Usage

You can use this from within any git directory to run basic pre-checks before making a commit:

$ git precheck
Installing node dependencies
Extracting build steps from travis

> [email protected] test /home/...
> node scripts/run-tests

# output of your commands...

Summary of build steps:
√  $ npm test
√  $ node scripts/generate-docs.js
√  $ git diff --quiet # make sure no files have changed

What commands does it choose to run? Well, it aims to run whatever Travis CI would attempt to run. How does it decide? Read below...

Integrating within vim

But wait, there's more! If you're a fugitive user, then you get vim-integration for free. You can run prechecks from within vim using:

:Git precheck " or if you were smart and made the short alias...

If you're not a fugitive user (but really, why not?) then you can use it like this:

:!git precheck

Travis CI Compatibility

Yup! It works with Travis as well. If you have a .travis.yml file in your repo, it will attempt to read the script steps from the file and execute those sequentially, just like Travis would. Now you can know if your PR will pass before you push it :+1:

Windows Compatibility???

Windows compatibility isn't my biggest priority, but it should still be there. If it isn't, drop me a line and let me know.