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

@monholm/eslint-config

v3.0.0

Published

Shared ESLint configurations using ESLint 9's flat config format.

Readme

@monholm/eslint-config

Shared ESLint configurations using ESLint 9's flat config format.

Formatting

This ESLint config does not include Prettier rules. We recommend:

  • Setting up format-on-save in your editor with Prettier
  • Running prettier --check in CI

Getting Started

All configs in this package require TypeScript, meaning they can't be used in pure JavaScript projects.

Installation

pnpm add -D @monholm/eslint-config eslint typescript typescript-eslint @eslint/js eslint-plugin-import @stylistic/eslint-plugin

TypeScript Configuration

The ESLint configuration uses projectService which automatically finds and uses your tsconfig.json. For this to work correctly, all files being linted must be included in the tsconfig.

The recommended approach is to use your root tsconfig.json for linting by omitting the include option, which will make TypeScript target all files by default. Then create a separate tsconfig.build.json for compilation that includes only the source files.

tsconfig.json (used for linting and type checking)

{
  "extends": "@monholm/tsconfig",
  "exclude": ["node_modules", "dist"],
  "compilerOptions": {"noEmit": true}
}

tsconfig.build.json (used for building)

{
  "extends": "./tsconfig.json",
  "include": ["src"],
  "compilerOptions": {"outDir": "dist", "noEmit": false}
}

Then build with tsc -p tsconfig.build.json and type check with tsc.

If you need to use a different tsconfig setup, please reference the typescript-eslint documentation on how to set up projectService instead of using the example eslint config provided later in this readme.

Available Configs

This package uses subpath exports in its package.json. You should import the configs as follows:

  • Base config:
    import {baseConfig} from '@monholm/eslint-config';
  • Node.js config:
    import {nodeConfig} from '@monholm/eslint-config/node';
  • React config:
    import {reactConfig} from '@monholm/eslint-config/react';

Setup

Base Config (TypeScript)

eslint.config.js

import {baseConfig} from '@monholm/eslint-config';
import {defineConfig} from 'eslint/config';

export default defineConfig([
  baseConfig,
  {languageOptions: {parserOptions: {projectService: true}}},
]);

Node.js

This config extends from the base config. You'll need to install the Node.js ESLint plugin:

pnpm add -D eslint-plugin-n

For eslint-plugin-n to work correctly, you must specify the engines field in your package.json so it knows your target Node.js version:

{"engines": {"node": ">= 20"}}

eslint.config.js

import {nodeConfig} from '@monholm/eslint-config/node';
import {defineConfig} from 'eslint/config';

export default defineConfig([
  nodeConfig,
  {languageOptions: {parserOptions: {projectService: true}}},
]);

React

This config extends from the base config. You'll need to install the React ESLint plugins:

pnpm add -D eslint-plugin-react eslint-plugin-react-hooks

eslint.config.js

import {reactConfig} from '@monholm/eslint-config/react';
import {defineConfig} from 'eslint/config';

export default defineConfig([
  reactConfig,
  {languageOptions: {parserOptions: {projectService: true}}},
]);