@duro-app/eslint-config

Shareable ESLint flat config for the Duro stack — the policies CLAUDE.md and agent memory can only suggest, wired into the linter so every consumer repo gates them at commit time (via amont's built-in pre-commit-lint-js, which activates on the presence of a root ESLint config) and in CI.

Requires ESLint 9 or 10 (flat config). It keeps only the design-system and UI-library policy, as react. The general conventions (base, effect, tests) and the decided-rule bridge (adrLint) come from @aval-adr/eslint-config, which this package extends and declares as a peer: install both.

pnpm add -D @duro-app/eslint-config @aval-adr/eslint-config

Usage

// eslint.config.js (repo root — amont only detects a ROOT config)
import {react} from '@duro-app/eslint-config'
import {effect, tests} from '@aval-adr/eslint-config'

export default [
  {ignores: ['**/dist/**', '**/build/**']},
  ...react,
  ...tests,
  // Server-only packages in a monorepo can scope the effect preset:
  ...effect.map((c) => ({...c, files: ['apps/api/**/*.ts']})),
]

Presets

react reports its import bans as duro/no-restricted-imports, apart from effect's @typescript-eslint/no-restricted-imports and adr-lint's adr-lint/no-restricted-imports, so composing them keeps every ban: none of the three overrides another.

What the policy enforces

• react: UI primitives come from @duro-app/ui only. react-aria, Spectrum, MUI, Radix, Chakra, headlessui, antd and @frontjutsu/ui are banned with a message that says where to add a missing component. Rich text goes through @fredericrous/lexical-multi, never raw lexical. It also carries everything in @duro-app/eslint-plugin: html.* elements, deep token imports, token values and the form kit.
• effect and tests are documented with @aval-adr/eslint-config.

Severity is the one gating line: error gates at commit and CI, warn informs everywhere. Don't add --max-warnings=0 — promote a rule to error here instead if it earns gating.

Adopting 3.0 with existing debt

3.0 promotes duro/no-raw-design-values to error and adds duro/no-raw-breakpoint-query. A repo that already carries raw values keeps the gate for every new file and ratchets the old ones down with an explicit file list — never a glob, never --max-warnings:

// eslint.duro-baseline.js — delete a line when its file is migrated. Never add one.
export const RAW_VALUES_BASELINE = [
  'app/routes/legacy-dashboard.tsx',
  'app/components/OldChart/OldChart.tsx',
]

// eslint.config.js — after the presets, so last-wins downgrades only these
import {RAW_VALUES_BASELINE} from './eslint.duro-baseline.js'
export default [
  ...react,
  {files: RAW_VALUES_BASELINE, rules: {'duro/no-raw-design-values': 'warn'}},
]

Most findings carry a suggestion; the ESLint API can apply them in bulk (message.suggestions[0].fix). What is left is the handful that need a human choice — an off-palette color, an off-scale spacing.

Escape hatches

Flat config is last-wins — scope an override after the preset:

...react,
{
  // The one file allowed to import the raw engine reset:
  files: ['packages/editor/src/usePageNode.ts'],
  rules: {'duro/no-restricted-imports': 'off'},
}

adr-lint rules (opt-in)

adrLint and adrLintTyped add the decided code rules a linter matches exactly. Import them from @aval-adr/eslint-config and put them last. Their bans have their own rule id, so no stack option is needed (6.0 drops it):

import {react} from '@duro-app/eslint-config'
import {adrLint} from '@aval-adr/eslint-config'

export default [...react, ...adrLint()]

Migrating from 5.x

• Add @aval-adr/eslint-config (^0.16.0) beside this package.
• Import base, effect, tests and adrLint from it; keep react from here.
• Drop stack from an adrLint call.
• An override of no-restricted-imports for the UI bans becomes duro/no-restricted-imports.