centralized-eslint-prettier
Centralized ESLint # Centralized ESLint & Prettier Configuration Prettier Configuration
This is a reference pattern. Learn from the approach, adapt to your context — don't copy verbatim.
Problem: Multi-workspace TypeScript projects (frontend, backend, infrastructure) need consistent linting and formatting without duplication, with support for pre-commit hooks and full-repo formatting.
Solution: Single root-level eslint.config.mjs with workspace-specific rules via file patterns, unified Prettier config, and centralized npm scripts with Husky integration.
Why This Pattern?
Benefits:
- Single Source of Truth: One config file, no duplication
- Workspace Flexibility: Different rules per workspace via file patterns
- Simplified Maintenance: Update rules in one place
- Consistent Pre-commit: Same hooks across all workspaces
- Easy CI/CD: Single command lints entire codebase
- Project Agnostic: Works for any TypeScript monorepo structure
More from loxosceles/ai-dev
static-frontend-hosting
S3 + CloudFront + Lambda@Edge for low-cost global hosting with edge authentication. Apply when setting up frontend hosting infrastructure.
65github-actions-oidc-aws
Secure GitHub Actions to AWS authentication using OIDC without long-lived credentials. CRITICAL PATTERN. Apply when setting up CI/CD pipelines that deploy to AWS.
54code-review
Multi-perspective code review strategy covering architecture, security, performance, and quality. Follow when reviewing code or analyzing changes.
52frontend-code-quality
Essential guidelines for clear, maintainable frontend code. Follow when writing or reviewing frontend components, composables, or pages.
52command-execution
Guidelines for executing commands and running scripts. Follow when running shell commands, installing packages, or using project scripts.
52cdk-bootstrap-configuration
CDK synth-time configuration pattern without context caching. Apply when working on CDK infrastructure code or adding new configuration parameters.
51