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

@jchiam/eslint-config

v7.0.0

Published

my personal ESLint rules

Readme

ESLint Config

npm

My personal shareable ESLint config. Targets TypeScript projects, with an optional React extension.

Requirements

  • ESLint 9 or 10
  • typescript-eslint ^8
  • eslint-plugin-import-x ^4.16

React projects additionally need:

  • eslint-plugin-react-hooks ^7.1

Usage

npm i -D @jchiam/eslint-config eslint typescript-eslint eslint-plugin-import-x

Create eslint.config.js in your project root:

// eslint.config.js — TypeScript project
import jchiamConfig from '@jchiam/eslint-config';

export default [...jchiamConfig];
// eslint.config.js — React + TypeScript project
// The /react config is self-contained — it includes the base config, so spread
// it alone. Do not also spread the base, or it will be included twice.
import jchiamReact from '@jchiam/eslint-config/react';

export default [...jchiamReact];

Override rules by appending a config object to the array:

import jchiamConfig from '@jchiam/eslint-config';

export default [
  ...jchiamConfig,
  {
    rules: {
      'prefer-const': 'warn', // override to warn instead of error
    },
  },
];

What's included

recommended.js

react.js

Self-contained — includes everything in recommended.js, plus:

Spread it on its own ([...jchiamReact]); there is no need to also spread the base config.

Breaking Changes

v6 to v7

The /react config is now self-contained — it includes the base config, so React projects spread a single array instead of composing base + react themselves.

// Before (v6)
import jchiamConfig from '@jchiam/eslint-config';
import jchiamReact from '@jchiam/eslint-config/react';
export default [...jchiamConfig, ...jchiamReact];

// After (v7)
import jchiamReact from '@jchiam/eslint-config/react';
export default [...jchiamReact];

Spreading both as before still "works" but includes the base config twice. Non-React projects are unaffected — keep using recommended as before.

v5 to v6

Replaced eslint-plugin-import with its maintained fork eslint-plugin-import-x. The original plugin does not support ESLint 10 (it crashes at runtime under ESLint 10); import-x does, and is lighter and faster.

Swap the peer dependency:

npm uninstall eslint-plugin-import
npm i -D eslint-plugin-import-x

This also unblocks ESLint 10 — you can now bump eslint to ^10.

Rule references are unchanged. import-x is a drop-in fork with identical rule names, and this config registers it under the import namespace, so existing import/... rule overrides in your eslint.config.js keep working with no changes.

One caveat — resolver/import settings renamed. import-x reads its settings under an import-x/ prefix. If your own config overrides import settings (e.g. a custom resolver), rename the keys:

// Before
settings: { 'import/resolver': { /* ... */ } }
// After
settings: { 'import-x/resolver': { /* ... */ } }

React projects: eslint-plugin-react-hooks must be ^7.1 (earlier 7.x does not support ESLint 10). The bundled @eslint-react/eslint-plugin was also upgraded to v5 for ESLint 10 support — no install needed, but its recommended rule set has changed across that upgrade.

v4 to v5

Migrated to ESLint flat config (required for ESLint 9+). The .eslintrc format is no longer supported.

Note: delete your existing node_modules and package-lock.json before reinstalling — the old lockfile pins conflicting major versions and will cause resolution errors.

Install the new peer dependencies:

npm i -D typescript-eslint

Remove the old peer dependencies (now bundled or renamed):

npm uninstall @typescript-eslint/eslint-plugin @typescript-eslint/parser

Config format changes from .eslintrc.js:

// Before (.eslintrc.js)
module.exports = {
  extends: ['@jchiam/eslint-config/recommended'],
};

To eslint.config.js:

// After
import jchiamConfig from '@jchiam/eslint-config';
export default [...jchiamConfig];

Rule changes:

  • Formatting rules moved from ESLint core to @stylistic/eslint-plugin (same rules, prefixed with @stylistic/)
  • no-shadow / no-use-before-define replaced by their @typescript-eslint/* equivalents (TS-aware, no false positives on type declarations)
  • no-new-object renamed to no-object-constructor
  • vars-on-top removed (redundant — no-var is enforced and @typescript-eslint/no-use-before-define covers the intent)
  • @typescript-eslint/indent removed (was deprecated and broken; @stylistic/indent is used instead)

v3 to v4

The original config file was split from index.js into recommended.js and react.js to allow non-React projects to use only the base config.

// Before
{ "extends": "@jchiam" }

// After
{ "extends": ["@jchiam/eslint-config/recommended", "@jchiam/eslint-config/react"] }