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

@kachkaev/eslint-config-base

v1.1.1

Published

A collection of carefully picked ESLint rules and plugins for TypeScript projects.

Readme

@kachkaev → eslint config (base)

A collection of carefully picked ESLint rules and plugins for TypeScript projects.

Compatible with ESLint v9+ (Flat config). Requires TypeScript to be present as a dependency.

See also @kachkaev/eslint-config-next.

Principles

This configuration uses warnings for rules that are related to code style (the ones that are not likely to prevent runtime errors), and errors otherwise. This looks less noisy than using errors for all rules. Both severity levels fail CI when eslint is called with --max-warnings=0.

It is assumed that all files are written in TypeScript and use ESM (not CommonJS).

Adding to project

  1. Ensure your package.json contains "type": "module".

  2. Ensure your project has a tsconfig.json file.

  3. Install these packages as dev dependencies:

    ## If you use NPM
    npm install -D eslint @kachkaev/eslint-config-base
        
    ## If you use PNPM
    pnpm add -D eslint @kachkaev/eslint-config-base
        
    ## If you use Yarn
    yarn add -D eslint @kachkaev/eslint-config-base

    If you don't keep your Node.js runtime up-to-date, you might need to install jiti to enable *.ts files -- see ESLint docs for details.

  4. Create eslint.config.ts with the following contents:

    import { defineConfig } from "eslint/config";
    import { generateBaseConfigs } from "@kachkaev/eslint-config-base";
    
    export default defineConfig([
      ...generateBaseConfigs(),
    
      // ... Place additional configs here if needed ...
    ]);

    If you work in a monorepo, you may need to specify tsconfigRootDir for some rules to work correctly:

    - generateBaseConfigs();
    + generateBaseConfigs({ tsconfigRootDir: import.meta.dirname });
  5. Add package.json scripts:

    {
      "...": "...",
      "scripts": {
        "...": "...",
        "fix:eslint": "eslint --max-warnings=0 --fix",
        "...": "...",
        "lint:eslint": "eslint --max-warnings=0",
        "...": "..."
      }
    }

You can now run [npm/pnpm/yarn] run fix:eslint to lint your code and [npm/pnpm/yarn] run lint:eslint to fix linting errors.