A very opinionated Eslint and Prettier configuration for JavaScript and TypeScript projects.
It also includes an experimental Stylelint configuration for CSS, SASS and SCSS files.

In the near future this might hold a configuration for Oxlint as well.

Make sure to install the necessary peer dependencies:

npm i -D @enke.dev/lint eslint prettier @awmottaz/prettier-plugin-void-html

For Typescript support, additionally install:

npm i -D jiti typescript typescript-eslint

Create a eslint.config.js (or eslint.config.ts) file in the root of your project. There are three ways to consume the configuration, from least to most control: the legacy all-in-one config, a ready-made preset, or the individual single configs.

import config from '@enke.dev/lint';

export default config;

Ready-made combinations for common project types. Import the one that matches your project and export it directly:

import { frontend } from '@enke.dev/lint/eslint/presets/frontend';

export default frontend;

Available presets:

Presets are flat config arrays, so they can be extended — e.g. to point the TypeScript parser at your tsconfig.json:

import { defineConfig } from 'eslint/config';

import { setTsConfigRootDir } from '@enke.dev/lint';
import { frontend } from '@enke.dev/lint/eslint/presets/frontend';

export default defineConfig([...frontend, setTsConfigRootDir(import.meta.dirname)]);

For full control, compose the individual chunks yourself. Each is a flat config array; spread the ones you need:

import { defineConfig } from 'eslint/config';

import { bun } from '@enke.dev/lint/eslint/bun';
import { html } from '@enke.dev/lint/eslint/html';
import { json } from '@enke.dev/lint/eslint/json';
import { lit } from '@enke.dev/lint/eslint/lit';

export default defineConfig([
  ...bun, // TypeScript + import rules, bun module resolver
  ...lit, // web components, lit and inline-html linting
  ...html, // standalone .html files
  ...json, // .json files
]);

Available configs:

By default the rules are syntactic only (typescript-eslint strict + stylistic), so no tsconfig is required. Every TypeScript base — the node / bun single configs and all three presets — additionally ships a type-checked variant that enables the type-aware rule sets (strictTypeChecked + stylisticTypeChecked, e.g. no-floating-promises, no-misused-promises, await-thenable).

Each variant is an extra export from the same module — just add the TypeChecked suffix:

import { frontendTypeChecked } from '@enke.dev/lint/eslint/presets/frontend';

export default frontendTypeChecked;

The VSCode Eslint plugin can be configured to pick up packages correctly by updating your settings.json, e.g.:

{
  "eslint.workingDirectories": ["./packages/*"]
}

A shared prettier configuration can be used by creating a prettier.config.js (or prettier.config.ts) file in the root of your project with the following content:

import config from '@enke.dev/lint/prettier.config.js';

export default config;

Uses some common presets and can be used in CSS, SASS and SCSS files.
It will enforce a specific property order and specific custom property prefixes if configured.

As this is totally opt-in, all necessary dependencies must be installed first:

npm i -D @enke.dev/lint stylelint stylelint-config-rational-order stylelint-config-standard-scss stylelint-order

Create a stylelint.config.js file in the root of your project and add the following content:

// @ts-check

import { defineConfig } from '@enke.dev/lint/stylelint.config.js';

export default defineConfig({ cssCustomPropertyPrefix: 'your-prefix' });

For now, no TypeScript support is possible.

Prerequisites:

• Node — version pinned in .node-version (use nvm/fnm to match it).
• bun — required for the test:bun suite; install it globally (curl -fsSL https://bun.sh/install | bash).

This repo self-tests the configuration by linting itself: npm run lint.
Therefore, a test.eslint.config.ts is used.

And additionally, naive tests are in place to check that the linter actually finds issues: npm run test.
This runs two suites:

• npm run test:node — the native Node test runner against obviously faulty code in the test directory (default/legacy config, prettier, stylelint).
• npm run test:bun — the bun test runner (test.run.bun.ts), which exercises the bun and type-checked configs against the source directly (bun resolves .js→.ts, so no build is needed). Requires bun.

If not already done via dependabot, dependencies can be updated by running npx --yes npm-check-updates --dep dev,optional,peer,prod,packageManager --upgrade --reject @types/node.