eslint-config-basic
Built a DX-first ESLint toolkit for JavaScript and TypeScript teams that want stronger defaults, less setup friction, and cleaner reviews.
En esta página 1 sección
Project notes
Active project
Building a DX-first ESLint toolkit
- Estimated reading time
- About 2 minutes
- In this project story
- 5 sections
I built @santi020k/eslint-config-basic to remove lint setup friction from the kind of projects I work on most: React, Next.js, Astro, TypeScript, and monorepos with real teams behind them. It is the successor to my original @santi020k/eslint-config-santi020k package, rebuilt from scratch around ESLint’s flat config format with a much wider framework footprint and better DX throughout.
Outcomes
- 229+ weekly npm downloads across personal, client, and shared codebases
Reduced repeated setup work for new projects and experiments
Encoded strong defaults across React, Next.js, Astro, and monorepos
Goals
Reduce setup friction for new projects so teams can get to useful standards faster.
Encode strong defaults based on real project work across front-end apps, tooling, Astro sites, and monorepos.
Stay composable so different stacks can opt into the pieces they actually need instead of inheriting a giant monolith.
What I built
A composable ESLint core
for JavaScript and TypeScript projects, with auto-detection for the frameworks and tools already in your repo.
Optional packages
for
React,Next.js,Astro,Vue,Svelte,Solid,Angular,NestJS,Expo,Qwik, andRemix.A strict mode
that promotes warnings to errors for CI/CD pipelines and stricter team workflows.
First-class support for Tailwind CSS, Vitest, and Testing Library,
plus documentation and examples that make adoption easier for teams, not just for me.
Results
- 229+ weekly npm downloadsacross personal, client, and shared codebases.
- Less repeated setup workwhenever a new project or experiment starts.
- A reusable expression of my engineering standardsin a form other teams can actually adopt and extend.
Why it matters
Linting is rarely the star of the show, but it changes how teams work.
This project reflects how I think about developer tooling in general: remove friction, encode good defaults, and make quality easier to maintain at scale.
De este proyecto
Dentro del trabajo.
Release guide
What Is New in @santi020k/eslint-config-basic v2.0
Explore @santi020k/eslint-config-basic v2 with ESLint 10, one-package setup, lazy framework support, monorepo tooling, lite mode, and CLI checks.
Leer artículoMigration story
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ículoComparte este artículo
Compártelo.
La copia automática no está disponible.
