Running ESLint?

ESLint drowning your pull requests in noise? We tune it.

An ESLint config that inherited a decade of cargo-culted presets often blocks real work and lets real bugs through. We prune the ruleset, finish the flat config migration, align the editor and CI, and leave you with a lint pass that catches the mistakes worth catching without burying the team in noise.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

eslint.log

still noisy

What it is

ESLint at a glance

ESLint is a pluggable static analysis tool for JavaScript and TypeScript, created by Nicholas Zakas in 2013. It parses source files into an AST, walks that tree, and runs rules written by the core team and the community against it, producing warnings and errors with autofix suggestions where possible. It has effectively become the standard linter in the JavaScript ecosystem.

ESLint 9, released in April 2024, made flat config the default and began removing the .eslintrc.* files that teams had used for a decade. The @typescript-eslint parser and plugin run TypeScript-aware rules on top, and most framework ecosystems ship their own plugin, including eslint-plugin-react, eslint-plugin-vue, eslint-plugin-svelte and eslint-plugin-jsx-a11y.

Type
Pluggable static analyser for JavaScript and TypeScript
First released
2013
License
MIT, open source
Maintained by
OpenJS Foundation and the ESLint team
Typically used for
Catching bugs before runtime, enforcing style and best practices, blocking unsafe patterns in CI, authoring team-wide code standards

The honest version

ESLint pros and cons

No technology is all upside. This is where ESLint earns its place and where it tends to cause trouble.

Where ESLint is strong

  • Catches real bugs before CIRules like no-unused-vars, exhaustive-deps and no-floating-promises surface bugs a type checker will not, and the fixes are often one line.
  • The plugin ecosystem is massiveReact, Vue, Svelte, accessibility, security and import ordering all have well-maintained plugins, which means the linter knows about your framework without custom code.
  • Editor integration is first classVS Code, WebStorm, Neovim and every other serious editor light up errors inline as you type, so problems are caught at keystroke speed rather than at CI time.
  • Autofix saves real timeMany rules can fix themselves on save, which turns a long list of warnings into a cleaned-up file without a developer reading each one.
  • Custom rules are tractableWriting a rule for a project-specific pattern is a few hundred lines rather than a research project, and the AST tooling is well documented.
  • TypeScript support is strong@typescript-eslint provides rules that genuinely understand types, filling gaps that the TS compiler leaves open around runtime behaviour.

Where ESLint bites

  • Configs inherit decades of baggageProjects extending airbnb, standard and half a dozen framework presets end up with a rule set nobody fully understands, where disabling anything causes something unrelated to break.
  • Flat config is a disruptive changeESLint 9 moves to flat config by default, which breaks legacy .eslintrc, every plugin that has not released a compatible version, and the muscle memory of every developer on the team.
  • Noise overwhelms signalA config with thousands of warnings teaches developers to ignore the output. By the time a real error lands, the lint log is already being skipped.
  • Performance is not freeOn large monorepos a cold ESLint pass can run for minutes, especially with TypeScript-aware rules enabled across the whole project.
  • Overlap with other toolsESLint, TypeScript, Prettier and Biome overlap in confusing ways, and teams often run two tools to enforce the same rule in contradictory directions.
  • Plugin versions drift quicklyMajor releases of ESLint, @typescript-eslint and framework plugins land out of sync, and matching compatible versions across a project turns into its own small job each quarter.

Sound familiar?

Common ESLint problems we fix

The ESLint problems that bring people to us, and what you have once each one is fixed.

Configuration eslintrc not supported in flat config mode

The flat config migration is only half done

ESLint 9 was installed but the old .eslintrc.* file is still there, the plugins used extendsFrom legacy shareable configs, and the linter refuses to load either shape cleanly.

Flat config running, legacy files retired

843 errors, 1,198 warnings

Pull requests drown in lint noise

A preset was turned on years ago, thousands of pre-existing issues were never cleaned up, and every new file surfaces a hundred findings that are not about the actual change.

Ruleset tuned to what matters

Cannot find module 'eslint-config-airbnb-base'

The config references a package nobody installed

A preset was extended in config but never added to package.json, or it is pinned to a version that does not support the current ESLint release.

Dependencies real and installed

@typescript-eslint parser failed to load

TypeScript-aware rules will not run

Parser not matched to the correct version, parserOptions pointing at a tsconfig that is not current, or the project option left on in a config where it is expensive.

Parser and tsconfig aligned

pre-commit: ESLint ran out of memory

The lint pass eats all available RAM

Parser-aware rules holding the whole project graph in memory, particularly when parserOptions.project is on across a large monorepo with no caching.

Memory reclaimed, cache enabled

prettier/prettier conflicts with indent

ESLint and Prettier fight over formatting

Overlapping rules between the two are both active, and autofix on save flips whitespace back and forth every time the file is touched.

Boundaries clear, one tool per concern

no owner, no documentation

The linter config was written by somebody who left

A long .eslintrc or eslint.config.js with cryptic rule overrides, no comments, and a dozen plugins. Nobody is sure which lines are load-bearing.

Documented, intentional and maintainable

lint pass: 437,221 ms

A full lint takes seven minutes

No cache, every rule running on every file every time, type-aware rules recomputing across the whole project on each run.

Lint back to seconds

What we do

ESLint help, from migration to day-to-day sanity

Call us for one failing config, or let us take the whole ruleset in hand.

Rescue
A linter that will not load, a pre-commit hook that blocks every developer, or a CI check firing thousands of warnings. We get it passing before we decide what to keep.
Flat config migration
Converting eslintrc to the new eslint.config.js format, validating plugin compatibility, and running a diff of what the new config would flag before anyone merges it.
Ruleset tuning
Pruning inherited presets, enabling rules that actually catch bugs in your stack, and turning off the ones that produce only noise for your codebase.
Performance
Caching, scoped project references, parallel linting and eslint-plugin-perf-standard, with the before and after wall-clock measured on your real repo.
Custom rules
Writing project-specific rules for patterns code review keeps flagging, so the linter enforces them automatically instead.
Managed Tech
A regular review of the ruleset as the project and the ecosystem change, with minor version upgrades handled quietly in the background.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running ESLint alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

ESLint questions

Something else? Call+1 737 727 7327

Can you migrate us from .eslintrc to flat config?

Yes. We branch the repo, convert the shape of the config, check each plugin for a flat-config release, and run the new config across the codebase to see what it would flag. Only once the diff is clean and the editor extension picks it up correctly do we merge it to main.

Our ESLint output is pure noise. Can you fix it?

Yes. Most noisy configs come from stacking several opinionated presets on top of each other. We go through the active rules, keep the ones that genuinely catch bugs in your stack, loosen or remove the stylistic ones Prettier should own, and document what is left so no one is afraid to touch it later.

Which preset should we use: airbnb, standard, or just @typescript-eslint/recommended?

For most modern projects we start from @typescript-eslint/recommended and add a small handful of rules the team genuinely cares about, rather than inheriting a thousand decisions from a preset authored for a different stack. Presets are a starting point, not a destination.

Should we switch from ESLint to Biome?

Occasionally yes, in projects where the lint overhead is dominating CI and the plugins you depend on have Biome equivalents. More often we leave ESLint in place and tune it. Biome moves quickly but the plugin coverage is still narrower than ESLint's, and swapping tools has its own cost.

Why does our ESLint pass take minutes?

Usually a few things combined: no caching, the project option on for type-aware rules across the whole monorepo, and rules that walk the AST multiple times. We enable eslint --cache, scope parserOptions.project where it helps, and prune the slowest offenders. Run time usually comes back inside a minute.

How much does ESLint help cost?

A quote is on us. Send the current config and a recent lint log, and we will come back with a price before any files are touched.

Free estimate

ESLint burying your pull requests?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.