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

@build-chores/staged

v0.9.0

Published

Staging JS projects is complicated.

Downloads

14

Readme

@build-chores/staged

Staging JS projects is complicated.

Synopsis

License: GPL v3 npm version Build Status

Stage files of your JS project before committing them with git.

Usage

Install the @build-chores/staged package into your project:

yarn install --dev @build-chores/staged

Use Husky to lint your stage whenever you commit.

yarn add --dev husky

Place a pre-commit hook in your .huskyrc. The following example hook only lints your stage when committing to the master branch. See the example .huskyrc for a template.

{
  "hooks": {
    "pre-commit": "! git rev-parse --abbrev-ref HEAD | grep -q master || lint-staged -c @build-chores/staged"
  }
}

To make sure that prettier isn't touching the package.json file during staging, place a .prettierignore file. See the example .prettierignore for a template.

package.json

You are ready to lint your staged files before committing.

Contribute

Check out our contributing.md to get started.

License