feat: get eslint v9 to work

[kristof-mattei]

How?

eslint/use-at-your-own-risk exposes builtinRules, which is the same (albeit updated) ruleset of ESLint.

Since we only need the names of the rules, and not the actual implementation, we're fine using this. eslint-plugin-unicorn uses the same.

The changes below are the absolute minimum, to reduce diff & impact in migrating to eslint-config-love@v64.

Plugin changes:

I replaced eslint-plugin-import by eslint-plugin-import-x, and subsequently renamed all import/ prefixes to import-x/, as eslint-plugin-import doesn't support ESLint v9.

Rule changes:

• no-new-symbol is deprecated, replaced by no-new-native-nonconstructor.
• line-comment-position, multiline-comment-style are no longer part of ESLint, and thus are no longer ignored as part of _rules_to_consider.ts.
• import-x/prefer-default-export popped up as part of the eslint-plugin-import to eslint-plugin-import-x migration. In order to minimize the migration cost, I've added it to _rules_to_consider.ts instead of enabling it.

[mightyiam]

I appreciate this, @kristof-mattei. Did you see discussion in #1734 ?

[kristof-mattei]

@mightyiam the link you posted refers to this PR.

[mightyiam]

Woops. Sorry. I meant #1589

[kristof-mattei]

Woops. Sorry. I meant #1589

That's awesome. Let me revert the import-x changes and give that a shot.

[mightyiam]

I expect a PR from renovate that bumps eslint-plugin-import. But I don't see one. Is there really a new version?

[kristof-mattei]

I expect a PR from renovate that bumps eslint-plugin-import. But I don't see one. Is there really a new version?

#1737

[kristof-mattei]

I expect a PR from renovate that bumps eslint-plugin-import. But I don't see one. Is there really a new version?

Okay, not gonna work as eslint-plugin-import still restricts eslint to be max v8.

At the moment all we can do is switch to eslint-plugin-import-x.

[mightyiam]

Thank you, @kristof-mattei .