Designing ESLint Packages Teams Actually Adopt
What separates ESLint configurations that spread across a codebase from ones that get removed after the first sprint.
- ESLint
- Code quality
7 artículos
Paquetes reutilizables de ESLint, migraciones y flujos de equipo para mantener código JavaScript y TypeScript consistente.
Más recientes primero
Volver al blogArtículos 1–7 de 7
What separates ESLint configurations that spread across a codebase from ones that get removed after the first sprint.
Explore @santi020k/eslint-config-basic v2 with ESLint 10, one-package setup, lazy framework support, monorepo tooling, lite mode, and CLI checks.
AI speeds up code changes, but ESLint, tests, snapshots, and end-to-end checks are what keep probabilistic output from turning into production risk.
Why I deprecated @santi020k/eslint-config-santi020k in favor of a composable monorepo with clearer packages, better docs, and stronger DX.
Reusable ESLint library for React, Next.js, and TypeScript projects. Enforces code quality with flat config support and simplifies the move from ESLint 8 to 9.
A practical guide to moving from ESLint 8 to flat config in ESLint 9, with a cleaner setup for React, Next.js, and TypeScript projects.
Configure ESLint for Next.js with TypeScript and Vitest integration. Covers code quality rules, import conventions, and a scalable setup for React projects.
Temas relacionados
Los 112 temasMás allá de este tema
Sigue otro tema o vuelve al archivo completo de artículos.