Some checks failed
Monorepo Pipeline / ⚡ Prioritize Release (push) Successful in 2s
Monorepo Pipeline / 🧪 Test (push) Successful in 3m54s
Monorepo Pipeline / 🧹 Lint (push) Successful in 4m12s
Monorepo Pipeline / 🏗️ Build (push) Successful in 2m42s
Monorepo Pipeline / 🐳 Build Directus (Base) (push) Successful in 1m7s
Monorepo Pipeline / 🐳 Build Build-Base (push) Successful in 1m43s
Monorepo Pipeline / 🐳 Build Production Runtime (push) Successful in 1m37s
Monorepo Pipeline / 🐳 Build Image Processor (push) Successful in 2m47s
Monorepo Pipeline / 🐳 Build Gatekeeper (Product) (push) Successful in 6m39s
Monorepo Pipeline / 🚀 Release (push) Successful in 7m18s
🏥 Server Maintenance / 🧹 Prune & Clean (push) Failing after 8s
@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-vitalsandnext/typescript. - Custom Rules:
_prefix for unused variables is allowed.anytype 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.