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

productive-eslint

v4.1.0

Published

Mildly strict and sufficiently practical ESLint config based on Evgeny Orekhov's eslint-config-hardcore

Readme

An ESLint config for practical code analysis

This package provides an AI-friendly ESLint flat config for repository-wide mechanical checks. It is heavily inspired by Evgeny Orekhov's eslint-config-hardcore.

The default preset is intentionally limited to rules that are safe as permanent lint noise: autofixable rules plus trivial non-autofixable checks that do not require architecture, API, or product decisions.

productive-eslint targets modern TypeScript-only ESM codebases. Project configs must use eslint.config.ts or eslint.config.mts.

Documentation:


📦 Installation

pnpm add -D productive-eslint eslint typescript prettier prettier-plugin-jsdoc
# or
npm i -D productive-eslint eslint typescript prettier prettier-plugin-jsdoc

🚀 Usage

  1. Make sure you have the following dependencies installed:

    • ESLint 10+
    • TypeScript 5.9+ (required)
    • Prettier 3.6+
  2. Create eslint.config.ts or eslint.config.mts in project root:

    import { createConfig } from 'productive-eslint'
    
    export default createConfig()
  3. Add scripts to package.json:

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

Options

createConfig accepts an options object:

| Option | Type | Default | Description | |---|---|---|---| | preset | Preset.AUTO_FIXABLE \| Preset.RECOMMENDED | Preset.RECOMMENDED | Rule preset | | ignores | string[] | [] | Additional glob patterns to ignore | | vue | boolean | auto-detect | Enable Vue/Nuxt rules | | rxjs | boolean | auto-detect | Enable RxJS rules |

By default, vue and rxjs are auto-detected based on installed packages.

Presets

import { createConfig, Preset } from 'productive-eslint'

Preset.AUTO_FIXABLE enables only rules with reliable ESLint autofix support.

export default createConfig({
  preset: Preset.AUTO_FIXABLE,
})

Preset.RECOMMENDED is the default permanent baseline. It includes AUTO_FIXABLE plus mechanical non-autofixable rules.

export default createConfig({
  preset: Preset.RECOMMENDED,
})

Monorepo setup

When the ESLint config lives at the workspace root, auto-detection may not find packages installed only in sub-packages. In this case, enable framework configs explicitly:

import { createConfig } from 'productive-eslint'

export default createConfig({
  rxjs: true,
  vue: true,
})

On-Demand Code Review Diagnostics

Repository-wide ESLint is kept mechanical on purpose. Nuanced checks such as type-safety debt, architecture boundaries, async correctness, migration tails, framework lifecycle risk, and complexity should be handled by focused diagnostics instead of being enabled as permanent lint noise.

These diagnostics are intended for explicit review/audit requests, not as an always-on agent tool loop during ordinary coding tasks.

Available CLI diagnostics:

productive-eslint analyze types
productive-eslint analyze architecture
productive-eslint analyze complexity
productive-eslint analyze async
productive-eslint analyze suppressions
productive-eslint analyze dead-code
productive-eslint analyze imports
productive-eslint analyze api
productive-eslint analyze vue
productive-eslint analyze rxjs
productive-eslint analyze migrations
productive-eslint analyze risk

Run one diagnostic at a time from an explicit project root:

productive-eslint analyze types --cwd /path/to/project
productive-eslint analyze complexity --cwd . --top 20
productive-eslint analyze suppressions --cwd . --include "src/**/*.ts" --exclude "**/*.test.ts"

Recommended first audit pass:

productive-eslint analyze risk --cwd .
productive-eslint analyze types --cwd .
productive-eslint analyze suppressions --cwd .
productive-eslint analyze async --cwd .
productive-eslint analyze architecture --cwd .
productive-eslint analyze complexity --cwd . --top 20

Use framework-specific diagnostics only when the target project enables the matching preset support:

productive-eslint analyze vue --cwd .
productive-eslint analyze rxjs --cwd .
productive-eslint analyze migrations --cwd .

The CLI requires the target project to export a marked productive-eslint composer from eslint.config.ts or eslint.config.mts.


📄 License: MIT © Bogdan Binitskiy 💻 Contributor: Roman Nikitin