Files
at-mintel/packages/eslint-config
Marc Mintel b70a89ec86
Some checks failed
Monorepo Pipeline / ⚡ Prioritize Release (push) Successful in 2s
Monorepo Pipeline / 🧪 Test (push) Successful in 1m15s
Monorepo Pipeline / 🏗️ Build (push) Successful in 3m55s
Monorepo Pipeline / 🧹 Lint (push) Successful in 4m20s
Monorepo Pipeline / 🐳 Build Image Processor (push) Failing after 35s
Monorepo Pipeline / 🐳 Build Gatekeeper (Product) (push) Failing after 45s
Monorepo Pipeline / 🐳 Build Build-Base (push) Successful in 52s
Monorepo Pipeline / 🚀 Release (push) Successful in 3m9s
Monorepo Pipeline / 🐳 Build Production Runtime (push) Successful in 52s
chore: sync versions to v1.9.3
2026-02-27 19:37:34 +01:00
..
2026-02-27 19:37:34 +01:00
2026-02-01 01:01:16 +01:00

@mintel/eslint-config

Shared ESLint configurations for Mintel projects, enforcing code quality and consistent style across Next.js and TypeScript codebases.

📦 Configurations

next

A comprehensive configuration for Next.js projects.

  • Extends: next/core-web-vitals and next/typescript.
  • Custom Rules:
    • _ prefix for unused variables is allowed.
    • any type is permitted (for rapid migration/prototyping).
    • React unescaped entities check is disabled.
    • Image element warnings are enabled (prefer next/image).

🚀 Usage

In a Next.js App

Create an eslint.config.mjs in your project root:

import { nextConfig } from "@mintel/eslint-config/next";

export default nextConfig;

🛠 Development

To add new rules, modify packages/eslint-config/next.js. Remember to create a changeset if you make breaking changes.