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 posts
Reusable ESLint packages, migrations, and team workflows for consistent JavaScript and TypeScript code.
Latest first
Back to blogPosts 1–7 of 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.
Migrate ESLint 8 to 9 by converting .eslintrc to eslint.config.js, moving ignore patterns, and checking the rules used by your files.
Configure ESLint for Next.js with TypeScript and Vitest integration. Covers code quality rules, import conventions, and a scalable setup for React projects.
Related topics
All 112 topicsBeyond this topic
Follow another topic or return to the full writing archive.