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

@nish1896/eslint-config

v3.0.9

Published

eslint and stylistic rules for eslint 8.57.1 or below to catch potential errors and take care of the code formatting.

Readme

@nish1896/eslint-config

NPM Version NPM Downloads NPM Downloads Per Month node-current GitHub Release Date - Published_At

A set of developer-friendly eslint, stylistic, typescript and accessibility configuration rules to help you and fellow developers follow the industry-recommended coding practices for easier readability, maintenance and productivity !

This package is compatible with eslint 8.57.1 or below. For usage with eslint 9.0.0 or above check @nish1896/eslint-flat-config.

⚠️ Deprecated ESLint Version

You might be using ESLint v8 with this package, which is deprecated. It is recommended to upgrade to ESLint v9 and @nish1896/eslint-flat-config for continued support and improvements.

👉 Follow the migration guide for a smooth and minimal-change upgrade process.

Quick Setup

Copy the code snippet most relevant to your application and paste it in the .eslintrc, .eslintrc.js or .eslintrc.json file in your project root.

Node.js

Use the ts module only if your code is written in Typescript.

module.exports = {
  extends: [
    "@nish1896/eslint-config/js",
    "@nish1896/eslint-config/ts"
  ]
}

React.js & Vite

Use the ts module only if your code is written in Typescript.

module.exports = {
  extends: [
    "@nish1896/eslint-config/js",
    "@nish1896/eslint-config/ts",
    "@nish1896/eslint-config/jsx"
  ]
}

Next.js

Update the existing .eslintrc.json file provided by Next.js app. Include the next/typescript and next-ts modules only if your code is written in Typescript.

module.exports = {
  extends: [
    "next/core-web-vitals",
    "next/typescript",
    "@nish1896/eslint-config/js",
    "@nish1896/eslint-config/next-ts",
    "@nish1896/eslint-config/next"
  ]
}

For comprehensive details on installation, setup, rules, and usage, please refer the Documentation 📖.

If you are a React developer, I highly recommend checking out my package, @nish1896/rhf-mui-components.