JS/TS project migration about eslint-config-galex

[ljosberinn]

ah I believe that actually just needs an additional flag, let me introduce that

[ljosberinn]

should be fixed with enableJavaScriptSpecificRulesInTypeScriptProject in the next release I hope :) docs included https://github.com/ljosberinn/eslint-config-galex#features

[ljosberinn]

great idea, yeah!

would need to extract:

• createPossibleErrorRules -> typescript
• createBestPractices -> typescript
• createVariableRules -> typescript
• createStylisticIssuesRules -> typescript, CRA, Next
• createES6Rules -> typescript

[ljosberinn]

should be fixed with the next release, lmk :)

[axelboc]

Hmm, it seems that the new behaviour is not quite what I expected since my JS files are still not fully linted. They do get fully linted if I enable checkJs, but as mentioned, this is not doable in my project.

The error is mine: checkJs has nothing to do with the issue at hand. Obviously, ESLint only cares about the *.ts glob! It doesn't magically apply the TS override to JS files when checkJs is enabled... Silly me! 😓

So I think the solution is for the new override that disables rules with TS equivalents to only ever apply to TS files -- never to JS files, regardless of checkJs.

If this leads to too many errors in a legacy project, then this is a good use case for your incrementalAdoption feature (which I haven't had time to look into yet but sounds very promising).

[axelboc]

I've just upgraded, and it works great, thanks a lot! 🎉

[axelboc]

As a side benefit, it now also fully lints all the .eslintrc.js, vite.config.js and other jest.config.js files in my monorepo 😄