Should We Replace eslint-config-galex with a Maintained Alternative?

[walesch-yan]

The eslint-config-galex repository has been archived and is no longer maintained. Furthermore, it cannot be used with eslint v.9.*+ and unfortunately older versions have reached EOL (see version support).

It seems that there are alternative ESLint Config packages, does anyone have experiences with any alternative or suggestions on which one we could use to replace the current?

[fabcor-maxiv]

Not something I know much about.

A colleague mentioned they used the Airbnb style and quite liked it, but apparently this one also does not support ESLint 9. They also mentioned the Typescript style.

[axelboc]

The typeScript-eslint plugin is essential in TypeScript projects, but it's just a plugin. A full config should configure core ESLint rules and many other plugins depending on the needs of the project (regexp, unicorn, promise, react, jsx-a11y, vitest...)

Forget about Airbnb's config, it's outdated, and just plain bad: it's way too lose in some aspects (including potential errors in code), and way too strict/opinionated in others (like formatting)...

One promising project I've come across with is Sheriff but it's made some debatable stylistic choices. It's a good source of ideas for plugins, though.

I think I was just sick of fighting with other people's configs...

[axelboc]

I ended up rewriting my own config in H5Web... It's 1200 lines-long! 😅 Obviously it's opinionated, like any ESLint config, but at least it's in line with the existing opinions of the project... 😂 See this PR for more details: silx-kit/h5web#1726

I've kept the dynamic aspect of Galex: it can detect a project's dependencies by looking at its package.json and enable only the corresponding plugins/rules (e.g. TypeScript, React, Vitest, etc.)

My goal is to eventually share this config as an NPM package, but I want to test it in a few projects first. Happy to set it up in MXCuBE if you think it's a good fit. Of course, the idea would not to be to enforce the same rules as in H5Web (it's way too strict) but rather to start from a strict base and then disable the rules we don't want (at least for the moment) or that y'all find too opinionated.

[walesch-yan]

As you mentioned, ESLint configs are always opinionated 😅. Personally, I believe that if you have your own configs, that you plan to maintain anyway, we could definitely try them in MXCuBE (with the rules configured for this project). Of course this decision should be taken by the developers in the collaboration as we all should agree/vote on the rules we like to follow :)

[mockoocy]

I took a quick glance at the plugins used and disabled rules and it seems good, wouldn't object adding it :)