Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

ESLint fails with 'No Babel config file detected'

ErrorParsing error: No Babel config file detected

Short answer

@babel/eslint-parser needs a Babel configuration file by default. The error means Babel found none from where ESLint is running. Either add a babel.config.json at the project root, run ESLint from that root, or set requireConfigFile to false and give the parser its own babelOptions.

  • Applies to ESLint 9, @babel/eslint-parser 7, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Look for a Babel config in the folder ESLint runs from. Babel searches the current working directory as its root.

    pwd
    ls babel.config.* .babelrc*
  2. 2Match what you see, then jump to its fix

    1. 1The ls command above prints nothing.The project has no Babel config fileFix
    2. 2The config exists at the repository root, but ESLint runs in a package folder.ESLint runs from a sub-folder, so Babel misses the root configFix

What does the error look like?

  • Parsing error: No Babel config file detected
  • ESLint stops on a file before any rule runs

Cause 1 of 2

The project has no Babel config file

1Check

The parser requires @babel/core and a valid Babel configuration file.

npm ls @babel/core @babel/eslint-parser

2Fix

Tell the parser not to require one and give it options directly, as the ESLint docs show. Or create babel.config.json instead.

// eslint.config.js
import babelParser from "@babel/eslint-parser";

export default [
  {
    languageOptions: {
      parser: babelParser,
      parserOptions: {
        requireConfigFile: false,
        babelOptions: { presets: ["@babel/preset-env"] },
      },
    },
  },
];

3Verify

ESLint parses the files.

npx eslint src

Confirmed by eslint.org

Did this fix it?

Cause 2 of 2

ESLint runs from a sub-folder, so Babel misses the root config

1Check

Babel treats the working directory as its root. A babel.config.json in a parent folder is not seen unless you ask for it.

pwd
ls ../babel.config.*

2Fix

Run ESLint from the folder that holds the config, or set rootMode to upward so Babel searches parent folders.

parserOptions: {
  babelOptions: { rootMode: "upward" },
}

3Verify

Lint the same file again.

npx eslint src/main.js

Confirmed by babeljs.io

Did this fix it?

How do I stop it coming back?

  • Keep one Babel config at the project root and run lint scripts from there.
  • Document the lint command in package.json scripts, not in editor settings.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

ng serve says it cannot determine the project or target

Cannot determine project for command.

The Angular CLI looked through angular.json for a project that defines the target you asked for (serve, build, test) and found none, or found several and could not pick one.

3 causes, each with a fix

Back end

ng serve cannot find the dev-server builder package

Could not find the implementation for builder @angular/build:dev-server

The builder named in angular.json (for example @angular-devkit/build-angular:dev-server) is looked up as an npm package starting from the workspace root.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.