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

eslint-config-imperium

v4.1.4

Published

Comprehensive ESLint configuration

Readme

Imperium ESLint Config

This is a strict configuration for ESLint. It is meant for those who have never found a linter annoying before.

Currently supports ESLint v10 with the flat config only.

Quickstart

  1. Install dependencies: npm i --save-dev eslint eslint-config-imperium
  2. Create eslint.config.js (see Example Configuration)
  3. Run your linter: npm run lint (or npx eslint)

Example Configuration

// eslint.config.js
import { auto } from "eslint-config-imperium";

export default auto;

auto is the strict core preset of this package. It currently includes base, typescript, stylistic, and perfectionist. It does not detect frameworks or environments automatically.

Configurations

This package is modular and includes several configurations intended to be enabled for certain environments. If you don't know what you need, you should probably use auto. Otherwise, pick a combination of the above configurations.

Main

  • auto - Special configuration in which some of the below configurations are enabled
  • base - Base framework and environment agnostic configuration

Frameworks / Environments

Framework modules are intentionally kept separate from runtime modules. Use browser or node when you want runtime globals and environment-specific rules, and then layer framework or library modules on top.

Style

You should not enable prettier and stylistic at the same time.

Accessibility

Recommended Composition

The package is designed to be composed explicitly. A few common combinations:

Browser TypeScript App

import { auto, browser } from "eslint-config-imperium";

export default [
  ...auto,
  browser,
];

React App

import { auto, browser, jsxA11y, react } from "eslint-config-imperium";

export default [
  ...auto,
  browser,
  react,
  jsxA11y,
];

Next.js App

import { auto, browser, jsxA11y, next, react } from "eslint-config-imperium";

export default [
  ...auto,
  browser,
  react,
  next,
  jsxA11y,
];

Node.js Library

import { auto, node } from "eslint-config-imperium";

export default [
  ...auto,
  node,
];

Vitest + Testing Library

import { auto, browser, react, testingLibrary, vitest } from "eslint-config-imperium";

export default [
  ...auto,
  browser,
  react,
  vitest,
  testingLibrary,
];

Svelte App

svelte is exported as an array of configs (it sets up the Svelte parser and processor), so spread it like auto:

import { auto, browser, svelte } from "eslint-config-imperium";

export default [
  ...auto,
  browser,
  ...svelte,
];

Astro App

astro is also exported as an array of configs (it sets up the Astro parser, processor, and <script> handling), so spread it like auto:

import { astro, auto } from "eslint-config-imperium";

export default [
  ...auto,
  ...astro,
];

Typed Linting

The typescript and auto configurations use parserOptions.projectService to enable type-aware linting. This automatically finds the closest tsconfig.json for each file.

If your editor or environment runs ESLint from a directory other than the project root, you may need to set tsconfigRootDir explicitly:

// eslint.config.js
import { auto } from "eslint-config-imperium";

export default [
  ...auto,
  {
    languageOptions: {
      parserOptions: {
        tsconfigRootDir: import.meta.dirname,
      },
    },
  },
];

Plugins

This is a list of the currently used ESLint plugins:

Building

  1. Clone the repository: git clone https://github.com/Delemangi/eslint-config-imperium.git
  2. Install the dependencies: npm i
  3. Build the package: npm run build

After this, the build output will be placed in the lib folder. You may use it directly, pack it or whatever you'd like afterwards.

License

This project is licensed under the terms of the MIT license.