Support ESLint v9.0

[antfu]

The context interface has changed, and removed in v9.0. For example: https://eslint.org/blog/2023/09/preparing-custom-rules-eslint-v9/#context.getscope()

This plugin on ESLint v9.0.0-rc.0 will throw errors like:

I tried to check the codebase, but it seems the overall dependencies of this repo are still a bit left behind. Like @typescript-eslint/utils is still v5 while now it's v7 - some the we don't even have the compact types for the new APIs - I wonder what's the strategies of this repo, should we keep support eslint v7 and v8, or we could do a major that only support latest v8.40+ + v9?

[SukkaW]

I tried to check the codebase, but it seems the overall dependencies of this repo are still a bit left behind. Like @typescript-eslint/utils is still v5 while now it's v7

I've already attempted that yesterday. I tried to upgrade ts-eslint/utils from version 5 to version 6 but was unsuccessful. The migration needs to change tons of stuff.

[JounQin]

I'm personally fine with dropping legacy eslint versions, but https://github.com/ota-meshi/eslint-compat-utils can also be considered at the same time.

And also I want to upgrade tseslint related packages first, as @SukkaW described, it's not that easy, we need to adapt some rules internally.

[JounQin]

Please help to test [email protected], while flat config is not officially supported yet, it is tracking at #29.

[JounQin]

@SukkaW See #66

[Zxilly]

I noticed import-x still depends on @typescript-eslint/utils at version ^7.4.0, should we bump it to 8.0.0-alpha.39 to remove the recersive dependent on eslint v8?

[GaborTorma]

@typescript-eslint/utils now stable of v8. Please bump it.

[pavitra-infocusp]

Agreed @GaborTorma

 WARN  Issues with peer dependencies found
.
└─┬ @antfu/eslint-config 2.24.1
  └─┬ eslint-plugin-import-x 3.1.0
    └─┬ @typescript-eslint/utils 7.18.0
      └── ✕ unmet peer eslint@^8.56.0: found 9.8.0