Linter Beta Version

[husseinraoouf]

I know you have been giving focus to other parts of the project like transformer and so on, but i think you should give a little focus to linter too, it is one step away from being the best linter for the javascript ecosystem, why stopping here, i am not talking about adding new rules you already done a great job there, but about making the linter more stable and easier to use

I have been wanting to use the linter for so long, but i was always kept away by many minor issues (ex. #7118, #4146 )

[Sysix]

Tl:dr: we are working on it with a smaller team and need to solve some core problems first

---

The core team is focused on making rolldown ready.
Meanwhile there is a small team which still looks into the linter and the Language-Server.

#7118 is currently on hold because this needs a refactor of the architecture.
Currently we are working on nested configuration, see #9152.
Before this is not intergrated, vscode-plugin will wait to fix the import plugin problem.

#4146 is not forgotten but we need to define a core structure how we handle plugins and rules.
We are checking how to solve this to report "invalid" configuration. You can read more here: #9421

[husseinraoouf]

Thank you for the answer,

Do you have any ETA on when those issues will be solved, i am not rushing you here but just to see if it is soon enouph to wait for or should i use another linter ( biome for example ) and consider oxlint later

[Sysix]

Sadly there is no ETA, all contributors are doing this work on their free time.
So it is hard to predict one.

I suggest to use both. eslint and oxlint at the same time.
There are plugins like eslint-plugin-oxlint and oxlint-migrate which should help to make a smooth transition.
For your import problem: just use eslint at the moment.
There is a eslint-plugin import-x which maybe help with speed-problems for the moment.

[husseinraoouf]

Make sense, i will try eslint and oxlint combination, thank you