eslint-config-santi020k
Turned internal linting conventions into a reusable package that standardized React and TypeScript projects and paved the way for @santi020k/eslint-config-basic.
En esta página 1 sección
Project notes
Completed project
Building my original ESLint toolkit
- Estimated reading time
- About 2 minutes
- In this project story
- 5 sections
@santi020k/eslint-config-santi020k was my first published ESLint package, an opinionated set of rules for JavaScript and TypeScript projects designed to enforce consistency, catch common mistakes early, and reduce setup work across the kinds of apps I was building most often.
Outcomes
Shared one reusable lint baseline across multiple React and TypeScript projects
Reduced repeated setup work for new apps and experiments
Created the foundation later rebuilt into eslint-config-basic
Goals
Standardize code quality across my own projects and the teams I worked with.
Reduce setup friction when spinning up React, Next.js, and TypeScript applications.
Make good defaults portable so linting could be part of the workflow instead of an afterthought.
What it included
Strict TypeScript and JavaScript defaults
aimed at preventing common errors and review churn.
Built-in support for React and Next.js
with optional presets for
Expo,Astro,TailwindCSS,Vitest, andi18next.Modular add-ons
so projects could opt into framework-specific needs without copying configuration by hand.
Automated publishing and examples
that made the package practical to maintain and easier to adopt.
Why it was replaced
As my projects grew and ESLint’s flat config format became the standard, the original package architecture became harder to extend and maintain. Rather than continuing to patch it, I rebuilt the idea from scratch as @santi020k/eslint-config-basic, a more composable toolkit with a wider framework footprint and better documentation.
Why it mattered
This project was the first time I turned internal engineering preferences into a reusable public tool.
It helped clarify how I think about developer tooling in general: remove repetitive setup, codify what matters, and make quality easier to keep.
De este proyecto
Dentro del trabajo.
What replaced it
Why I Moved My ESLint Library to @santi020k/eslint-config-basic
Why I deprecated @santi020k/eslint-config-santi020k in favor of a composable monorepo with clearer packages, better docs, and stronger DX.
Leer artículoOriginal introduction
Boosting Code Quality and Efficiency with My ESLint Configuration Library
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.
Leer artículoComparte este artículo
Compártelo.
La copia automática no está disponible.
