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 🙏

© 2026 – Pkg Stats / Ryan Hefner

eslint-config-heyitsbash

v0.2.6

Published

"ESlint & Prettier Config by heyitsbash"

Downloads

37

Readme

Heyitsbash config for EZ linting

Local Install

  1. In your project folder type npm init , and
  2. npx install-peerdeps --dev eslint-config-heyitsbash
  3. Create .eslintrc.js file in the root of your projects folder
  4. Copy this in .eslintrc.js
module.exports = {
  'extends': [
    'heyitsbash',
  ]
};

Add these scripts in package.json

"scripts": {
  "lint": "eslint .",
  "lint:fix": "eslint . --fix"
},

Lint/pretty your code by running npm run lint and npm run lint:fix in the console

Now linting for commit also available

  1. Run npm install husky --save-dev to make sure husky is installed properly
  2. Create commitlint.config.js file in the root of your projects folder
  3. Paste that in commitlint.config.js
module.exports = {
  extends: ['@commitlint/config-conventional'],
  rules: {
    'subject-min-length': [2, 'always', 10],
  }
};

Add these lines in package.json

"husky": {
  "hooks": {
    "commit-msg": "commitlint -E HUSKY_GIT_PARAMS",
    "pre-commit": "npm run lint:fix && git add ."
  }
}

Now all your commits will first be checked by linter rules and then with conventional commit rules, if any of these fail - changes will not get commited.

Be aware that this line in husky hook git add . will always stage all files, if you not commiting all your files at once, you should remove it.

Commit example:

  1. git commit -m "random commit bla bla bla" - this line will fail by conventional commit rules.
  2. git commit -m "chore: test commit with new modules" - this line will pass by conventional commit rules.