Skip to content

feat: ESLint 10 support#280

Open
mdjastrzebski wants to merge 4 commits intomainfrom
feat/eslint-10-support
Open

feat: ESLint 10 support#280
mdjastrzebski wants to merge 4 commits intomainfrom
feat/eslint-10-support

Conversation

@mdjastrzebski
Copy link
Copy Markdown
Member

@mdjastrzebski mdjastrzebski commented Apr 13, 2026

Summary

Fix ESLint 10 compatibility for JS/JSX flat config consumers by preserving the original @babel/eslint-parser export shape in babel-eslint-parser.compat.js.

This keeps the parser meta field available, which ESLint 10 uses when serializing config objects.

What changed

  • preserve the original Babel parser export and override only parseForESLint
  • keep the addGlobals compatibility patch used by eslint-plugin-flowtype
  • extend the ESLint 10 test workspace to also run --print-config as a regression check

Why

Normal linting was already passing, but config serialization flows for JS/JSX files could still fail under ESLint 10 because the compat wrapper dropped parser metadata.

That affected tooling and debugging flows such as:

  • eslint --print-config
  • config inspection
  • direct calculateConfigForFile() serialization

Testing

  • yarn test
  • verified ESLint v8, v9, and v10 test workspaces pass
  • verified the ESLint 10 lane now succeeds for both linting and --print-config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant