Built for JavaScript and TypeScript teams

Santi020k ESLintFlat config that scales from a starter repo to a real team

DX-first documentation for @santi020k/eslint-config-basic, a composable ESLint 9/10+ toolkit for JavaScript and TypeScript teams shipping React, Next.js, Astro, Vue, Svelte, Solid, Angular, NestJS, Expo, Qwik, and Remix.

FocusFlat configZero-config auto-detectionFramework packagesPlayground-backed docs

Start with the guide

Explore frameworks

Open GitHub

Base

JavaScript, TypeScript, runtime presets, and strict mode.

Scale

12 frameworks, 26 integrations, docs, API, and playgrounds.

Composable by default

Start with the base package, add explicit framework packages, and layer in only the integrations your project actually needs.

Zero-config auto-detection

Let the library detect TypeScript, runtimes, frameworks, and optional tooling from your repo so teams spend less time on lint wiring.

12 framework guides

React, Next.js, Astro, Vue, Svelte, Solid, Angular, NestJS, Expo, Qwik, Remix, and TypeScript each have dedicated setup docs.

26 optional integrations

Tailwind CSS, Vitest, Playwright, Markdown, Prettier, Unicorn, Security, Storybook, i18next, and more are documented with the same model.

Strict mode for teams

Promote warnings to errors when you want cleaner CI pipelines, stronger review signals, and fewer style debates in pull requests.

Playground-backed confidence

Docs stay close to the code because framework packages, optionals, and examples are validated against real playground packages and tests.

Why this library exists

Lower lint setup friction without shipping a giant monolith.

@santi020k/eslint-config-basic was built for the kind of projects teams actually maintain: JavaScript and TypeScript apps, framework-heavy frontends, monorepos, and codebases that need strong defaults without turning every setup into a custom linting project.

This docs site is the fastest way to choose the right package, compose a flat config, and roll the setup across React, Next.js, Astro, Vue, Svelte, Solid, Angular, NestJS, Expo, Qwik, Remix, and modern tooling.

12framework guides

Explicit packages for the stacks you actually ship, not vague one-size-fits-all presets.

26optional integrations

Tailwind CSS, Vitest, Playwright, Markdown, Prettier, Storybook, i18next, and more.

DX-firstfrom install to CI

Auto-detection, strict mode, real playgrounds, and docs that stay tied to the working codebase.

ESLint 9/10+flat config ready

Built around modern ESLint workflows instead of legacy config patterns teams are trying to leave behind.

Start hereGet running in minutes

Learn the base package, the first config file, the auto-detection model, and the right next page for your stack.

Open guide FrameworksChoose the exact framework package

Every supported framework has its own page with install notes, config examples, and package relationships.

Browse frameworks ToolingLayer in optional integrations

Libraries, testing tools, file formats, standalone tools, and extension packs are documented in one place.

See tooling PackagesUnderstand the monorepo layout

See what the main package owns, what lives in core or optionals, and how the repo stays composable.

Inspect packages ExamplesValidate ideas against playgrounds

Jump into real framework and tooling playground packages before you adopt a new stack or integration.

Open playgrounds ReferenceBrowse the generated API

Keep guides, package docs, and generated reference in the same place so canonical links stay stable.

Read API docs

Build the right linting stack

Framework packages stay explicit on purpose.

Use dedicated framework packages when the runtime actually requires them. That keeps the final config readable, makes package boundaries obvious, and reduces hidden behavior for teams onboarding into an existing repo.

React
Next.js
Astro
Vue
Svelte
Solid
Angular
NestJS
Expo
Qwik
Remix
TypeScript

Optional tooling is grouped the way teams think about work.

Instead of memorizing custom preset names, enable categories that mirror real project needs: libraries, testing, formats, standalone tools, and extension packs.

Tailwind CSS
Vitest
Playwright
Testing Library
Markdown
MDX
Prettier
CSpell
Storybook
i18next
Unicorn
Security

Choose the fastest path

Use the docs like a product guide, not just a file index.

Start with Getting Started if you are new to the library, jump to Configuration if you already know the shape of the final config, or go straight to Optional Tooling and Framework Guides when the application stack is already defined.

The generated API reference, package docs, and playground guidance all stay inside the same site so contributors, tech leads, and individual developers can move from install to real repo decisions without losing context.