ESLint equivalent?

[recursive-franciscop]

I love this plugin and I'm trying to use it in a project, however we already have a eslint enabled that checks for the sorting. So those two are in conflict now; also I don't want to fully remove the eslint (since it's good for the CI), so I'm looking into replacing my current eslint for some that is compatible with @ianvs/prettier-plugin-sort-imports.

That way when I save, the imports get sorted automatically. And when the eslint runs, the imports are as expected. Is there any recommended eslint that is compatible with the @ianvs/prettier-plugin-sort-imports default sorting?

For reference we are using perfectionist/sort-imports and it's no compatible by default with @ianvs/prettier-plugin-sort-imports, they try to apply different rules.

[fbartho]

@recursive-franciscop I make prettier run in CI on my repositories. Originally I had made it throw an error if there were any modified files, but eventually (in a controlled environment) I made prettier automatically commit the changes to the repo (to the PR, more specifically).

It's an automatic change that keeps everything in sync so there's no need to nag the Engineer! (I also do this for auto-fixable eslint errors too).

[recursive-franciscop]

Thanks, the latter seems a bit tricky but the former "I had made it throw an error if there were any modified files" seems like a solution we could use, thanks for the input!

This is a good alternative for me, but not a direct answer (and I couldn't find much info about a compatible eslint), do you prefer me to close as resolved? Or leave open in case there's someone who can bring some eslint-compatible library recommendation?

[fbartho]

Feel free to keep the discussion open. I don't have a direct answer to your request for an eslint tool here, sorry. Ian might have a different memory, but I think this is the first time I heard anybody ask for that!

I am a maintainer of DangerJS as well so I glue any custom PR Feedback tooling with that.
(There are plugins for inline reporting eslint issues, and I also have one that comments on the PR with info around package.json dependency changes)

[IanVS]

Right, generally when I've set up prettier and ESLint in a project, I decide to let prettier do the formatting, and ESLint handle potential code problems. You run into trouble if you try to use both for formatting. That's why projects like https://github.com/prettier/eslint-config-prettier exist, to disable all the eslint rules that might conflict with prettier.

In short, I think you should decide whether to use eslint to sort imports, or prettier to sort them, but not both. Then you can enforce in CI that your code is correct, using either tool you prefer (or both for different purposes, like I do).