View on GitHub

ESLint config for Next.js and Tailwind CSS

A ready-to-use eslint.config.mjs for Next.js with Tailwind CSS: Core Web Vitals, React, accessibility and Tailwind class linting, for ESLint 9 and 10.

IncludesESLint coretypescript-eslintReactReact HooksJSX A11yNext.jsSimple Import SortVitestESLint StylisticTailwind CSS

How it works

  1. Pick your stack

    Start from a preset for JavaScript, TypeScript, React, Next.js, Next.js with Tailwind CSS, Express or NestJS, and choose ESLint 9 or ESLint 10.

  2. Add plugins and tune the rules

    Add plugins from the catalog and switch their shared configs on or off. Set any rule to off, warn or error and edit its options; each rule shows what your configs already set.

  3. Copy, install and lint

    Copy or download eslint.config.mjs, run the install command for npm, pnpm, yarn or bun, then run npx eslint . in your project.

Supported ESLint plugins

Each plugin's rule list is read from its published package, so rule names, recommended settings and deprecations match the version you install.

Core

  • ESLint core@eslint/js

    The rules built into ESLint: likely bugs, best practices and language features.

Languages

  • typescript-eslinttypescript-eslint

    TypeScript parsing plus rules that understand types.

Code quality

  • Unicorneslint-plugin-unicorn

    Hundreds of opinionated rules for modern, consistent JavaScript. Requires ESLint 10.

Frameworks

  • Reacteslint-plugin-react

    React and JSX best practices.

  • React Hookseslint-plugin-react-hooks

    The Rules of Hooks and React Compiler checks.

  • React Refresheslint-plugin-react-refresh

    Checks that components can be safely updated by Fast Refresh.

  • JSX A11yeslint-plugin-jsx-a11y

    Accessibility checks for JSX elements.

  • Next.js@next/eslint-plugin-next

    Next.js checks for images, scripts, fonts and Core Web Vitals.

  • TanStack Query@tanstack/eslint-plugin-query

    Catches common TanStack Query mistakes, such as incomplete query keys.

Backend

  • Node.jseslint-plugin-n

    Node.js checks: deprecated APIs, unsupported features and missing imports.

  • NestJS Typed@darraghor/eslint-plugin-nestjs-typed

    NestJS checks for dependency injection, Swagger decorators and validation.

Testing

  • Vitest@vitest/eslint-plugin

    Vitest checks: focused or skipped tests, missing assertions and more.

  • Jesteslint-plugin-jest

    Jest checks: focused or skipped tests, missing assertions and more.

Imports and sorting

  • Import Xeslint-plugin-import-x

    Validates imports and exports: unresolved paths, duplicates, cycles and ordering.

  • Simple Import Sorteslint-plugin-simple-import-sort

    Automatic, zero-config sorting of imports and exports.

  • Perfectionisteslint-plugin-perfectionist

    Sorts objects, imports, types, JSX props and more.

Style

  • Tailwind CSSeslint-plugin-tailwindcss

    Tailwind CSS class ordering, shorthands and conflicting classes.

  • ESLint Stylistic@stylistic/eslint-plugin

    Formatting rules: indentation, quotes, semicolons, spacing and more.

Frequently asked questions

Short answers about flat config, migrating and how the generator works. Something missing? Open an issue on GitHub.

What is an ESLint flat config?

It is the configuration format ESLint uses from version 9: one eslint.config.js (or .mjs, .ts) file that exports an array of config objects. It replaces .eslintrc files, and plugins are imported as ordinary JavaScript modules instead of being resolved by name.

How do I migrate from .eslintrc to a flat config?

Paste your .eslintrc.json into Import .eslintrc above the editor: it maps extends, plugins, environments and rules onto the generator and lists anything it could not carry over. ESLint's own npx @eslint/migrate-config .eslintrc.json is the alternative for a mechanical conversion.

Should I use ESLint 9 or ESLint 10?

Both use flat config. ESLint 10 removes the old eslintrc format entirely, and some plugins have not declared support for it yet. The generator checks which ESLint versions each plugin supports and warns you before you install one that does not.

Does it support TypeScript and type-aware rules?

Yes. When you enable a typescript-eslint config that needs type information, the output adds the projectService parser setup and turns type-aware rules off for plain JavaScript files.

Can I use it for Next.js and Tailwind CSS?

Yes. The Next.js + Tailwind preset combines the Next.js, React, React Hooks, jsx-a11y and Tailwind CSS plugins with typescript-eslint, import sorting, Vitest and Stylistic. Remove any of them or add more from the catalog.

Is my configuration stored anywhere?

Only in your own browser's local storage. There is no account, server or database. A share link carries the config after the # in the URL, a part browsers never send to a server.

Is it free?

Yes. It is free to use, and the source code is on GitHub under the MIT license.