fix: skip parseESlint if eslint filepath is a js file

[yy4382]

Description

Focusing on the same bug in #498 .

If eslintrc.filepath ends with "js", it will generate a javascript file (which is add in #494 ), however the parseESlint function still treat it as JSON file, which triggers an error.

In this PR, parseESlint returns {} if filepath ends with "js", instead of the String.replace() method used in #498 . Parsing is skipped in non-json mode.

If I understand correctly, skipping the parsing of previously generated eslint files would only have an impact on artifacts when the generated file was manually modified or the scope of automatic imports is narrowed. I'm not sure if resolve work fine, since I haven't use them.

Linked Issues

null

Additional context

Maybe it will be better to be able to "import" it, but I cannot find an elegant way to do that.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.