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

polite-linter

v1.2.1

Published

Polite linter to be used with prepush githook

Downloads

350

Readme

Polite linter for git prepush hooks

Everybody likes git prepush hooks – they prevent us from pushing invalid code to repository.

But there are always few problems:

  • hooks run on current INDEX, so if your commits are pure, but INDEX is dirty and contains some lint errors, it won't be pushed.
  • or vice versa, you have committed files with mistakes, fixed them after and would easily push them if prepush runs on current INDEX
  • linters run on whole project, no matter that you have committed one file

Polite linter analyzes your log and runs linter only on files which are committed since last push, linting their HEAD version.

All linting runs in memory, not using or affecting local files at all

linter example

How to use

Polite linter for now supports eslint and tslint linters(contributions for another linters are welcome!)

npm i polite-linter --save-dev

If you are using husky, just add to your package.json

"prepush": "polite-tslint --rules=path_to_custom_rules --config=path_to_tslint_config

or

"prepush": "polite-eslint"

-- If you are using pure git hooks, use in your pre-push

polite-tslint --rules=path_to_custom_rules --config=path_to_tslint_config

Options

tslint

If you are using tslint, there are two options you can provide:

  • --rules – path to your custom rules directory(if you are using one)
  • --config – path to your basic config file. By default ./tslint.json is used

eslint

Eslint for now does not support any flags – it will find .eslintrc by itself and use it to lint your files

License

MIT