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

@coara/eslint-config-ng

v3.0.0

Published

Shareable eslint ng config for Coara ÖU projects

Readme

@coara/eslint-config-ng

Supports Angular 20, 21 and 22, on eslint 9 or 10.

Upgrading to 3.0

Nothing to do in most projects: install it and delete any overrides block you were using to force the old peer ranges.

The only breaking part is a swapped plugin. eslint-plugin-import has no eslint 10 release — 2.32.0 is current and its peer range stops at eslint 9 — so this config now uses eslint-plugin-import-x, the maintained fork, which supports eslint 8, 9 and 10.

It is registered under the import namespace, so rule names do not change: import/newline-after-import and import/no-deprecated behave exactly as before, and any rulesOverride you already pass keeps working untouched. What does change is the package you install alongside this one:

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

Peer ranges after this release:

| peer | range | | --- | --- | | eslint | ^9.29.0 \|\| ^10.0.0 | | angular-eslint | ^20.1.1 \|\| ^21.0.0 \|\| ^22.0.0 | | @ngrx/eslint-plugin | ^20.1.0 \|\| ^21.0.0 | | @stylistic/eslint-plugin | ^4.4.1 \|\| ^5.0.0 | | eslint-plugin-import-x | ^4.6.0 | | typescript-eslint | ^8.34.1 |

Verified against both an Angular 21 / eslint 9 project and an Angular 22 / TypeScript 6 / eslint 10 one.

Installation

$ npm i -D @coara/eslint-config-ng

Usage

  1. Run Angular ESLint:

    ng add angular-eslint
  2. Install @coara/eslint-config-ng:

    npm i -D @coara/eslint-config-ng
  3. Replace the file content and configure the parser's relative path:

    // eslint.config.js
    
    import createEslintConfig from "@coara/eslint-config-ng";
    import { dirname } from "path";
    import { fileURLToPath } from "url";
    
    const __filename = fileURLToPath(import.meta.url);
    const __dirname = dirname(__filename);
    export default createEslintConfig({
      project: "./tsconfig.json",
      tsconfigRootDir: __dirname,
    });
  4. Add module compatibility:

    // package.json
    {
      "type": "module"
    }
  5. Recommended: Install Prettier:

    npm install prettier --save-dev
  6. Recommended: Configure Prettier with the print width option:

    // prettier.config.js
    export default {
      printWidth: 120,
    };
  7. Optional: For VSCode auto formatting, linter fixes, and differentiating linter from TypeScript errors:

    // .vscode/settings.json
    {
      "editor.defaultFormatter": "esbenp.prettier-vscode",
      "eslint.rules.customizations": [{ "rule": "*", "severity": "warn" }],
      "editor.codeActionsOnSave": {
        "source.fixAll.eslint": true
      },
      "eslint.useFlatConfig": true,
      "editor.formatOnSave": true
    }