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

captain-githook

v1.1.0

Published

An NPM module to allow managing git hooks with source control.

Downloads

14

Readme

captain-githook

Install

npm install --save-dev captain-githook

Usage

Install this module to your repository, and put any repository-wide hooks in ./.githooks. You'll now be able to commit and share these hooks. Each of the hooks in ./.githooks must be executable and may only be a file with no extension, named after the hook it should run on. These can be used to run multiple other scripts or not, the choice is yours. There are some example hooks in the example-hooks directory of this repository.

How?

Upon install, this module will run a postinstall hook. This moves any existing hooks you may have into .git/hooks/local, and symlinks .git/hooks/shared to ./.githooks. Git hook hardlinks are then created pointing to split-hook.js, which when called will look first for the name of the called hook in local and run if present, and then do the same for a shared hook.

Why?

Initially created for my own pre-commit linting, but found to be useful in bigger teams to enforce code guidelines before any code makes it up to the repository.

Uninstall

There is an uninstall task which can be run, this clears up the .git/hooks directory, but leaves the ./.githooks directory intact. This allows you to easily switch to another githook management tool without clearing up manually.