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

@alexlit/config-eslint

v159.1.0

Published

Sharable ESLint configuration

Readme

ESLint Configuration

[!WARNING]
For eslint version < 9 use @alexlit/config-eslint@90 or lower.

There are no presets: base only provides the shared file scope, ignore patterns and globals. Every plugin is enabled explicitly, so you pay only for what you use.

Installation

npm i @alexlit/config-eslint -D

Connection

Always start with base (it must be first) and finish with prettierConfig (it must be last, it disables the formatting rules).

// eslint.config.js
import {
  // foundation
  base,

  // plugins
  deMorgan,
  importX,
  javascript,
  jsdoc,
  json,
  perfectionist,
  prettierConfig,
  regexp,
  sonar,
  stylistic,
  typescript,
  unicorn,

  // framework plugins
  pinia,
  tailwindcss,
  tanstackQuery,
  unocss,
  vitest,
  vue,
  vueAccessibility,
  vueI18n,
  zod,
} from '@alexlit/config-eslint';

export default [
  ...base, // must be first

  ...deMorgan,
  ...importX,
  ...javascript,
  ...jsdoc,
  ...json,
  ...perfectionist,
  ...regexp,
  ...sonar,
  ...stylistic,
  ...typescript,
  ...unicorn,

  ...pinia,
  ...tanstackQuery,
  ...unocss,
  ...vitest,
  ...vue,
  ...vueAccessibility,
  ...vueI18n,
  ...zod,

  // `tailwindcss` is the only plugin exported as a factory, because it needs a path to your CSS entrypoint
  ...tailwindcss({ cssConfigPath: './src/assets/css/main.css' }),

  ...prettierConfig, // must be last

  // Custom rules example
  // { files: ['**/*.js'], rules: { 'no-console': 'off' } },
];

Drop what you do not need.

Type-aware rules (optional)

Type-aware rules (no-floating-promises, no-misused-promises, await-thenable, no-unsafe-*, switch-exhaustiveness-check, no-unnecessary-condition, …) require type information, which makes linting slower. They are not enabled by default.

To enable them, replace typescript with typescriptTypeChecked:

import {
  base,
  typescriptTypeChecked,
  prettierConfig,
} from '@alexlit/config-eslint';

export default [
  ...base,
  // ...other plugins
  ...typescriptTypeChecked, // instead of ...typescript
  ...prettierConfig,
];

[!NOTE] typescriptTypeChecked needs a tsconfig.json in your project root (projectService is used, so keep both tsconfig.json and tsconfig.node.json etc. in a single root if needed). Use it instead of typescript, not alongside.

Formatting: prettier vs prettierConfig

Both are included, and they are not interchangeable.

| Export | From | Effect | | ---------------- | ------------------------ | ------------------------------------------------ | | prettierConfig | eslint-config-prettier | only turns off formatting rules that conflict | | prettier | eslint-plugin-prettier | additionally runs Prettier itself as a lint rule |

Use prettierConfig when Prettier runs as a separate step (editor, prettier CLI, Husky). Use prettier if you want ESLint to report and fix formatting in one pass — it is slower and duplicates the formatter.

Usefull links