Eslintrc format compatibility during migrations

[Polm1]

Description

Ensure compatibility for .eslintrc.js during migrations as .eslintrc.json format currently supported.

Motivation

.js can provide access to some advantages such as exported functions benefits.

Suggested Implementation

I imagine that .eslintrc format can be choose in NX generators, then during migration will be equally treated both .json and .js formats.

[Polm1]

@meeroslav here it is the issue, many thanks again for support!

[meeroslav]

Hey @Polm1, sorry for the delay in response.

EsLint is working on the new format - eslint.config.js (you can read about it more here: https://github.com/eslint/rfcs/tree/main/designs/2019-config-simplification).

Unfortunately, due to high complexity and lack of time, instead of creating support for .eslintrc.js now and then again for new config once it lands, we would rather wait until the new format comes as it will also include compatibility mapper.

Here is the progress: eslint/eslint#13481
We will start with the adoption after stage 2.

[Polm1]

Many thanks, @meeroslav will follow updates :)

[martinplavek]

Hello @meeroslav,

is there please any chance you have started to work on adoption of the eslint.config.js files? The stage 2 should be finished except of one Change Request. I cannot see any task planned in the linter scope. Thanks for the update

[meeroslav]

Hi, not yet but it's on the list.
The new format is already implemented in eslint, although hidden behind a flag.

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.