chore: fix CI failure and ensure the latest @eslint/core is used

[lumirlumir]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

This PR provides one possible fix for #308.

It partially reverts commit 02bac50.

---

I'm not entirely sure about this fix for the following reason:

• @eslint/core is in a 0.x release, so these breakages may be acceptable.
• Technically, making fix?: RuleFixer | null | undefined; required under suggest wouldn't cause a problem, but I think the SuggestedEditBase type is used incorrectly somewhere, which is causing the issue.

I believe there may be a better solution, so please consider this PR a hotfix for the problem. (Or any other suggestions would be welcome.)

What changes did you make? (Give an overview)

This PR provides one possible fix for #308.

It partially reverts commit 02bac50.

Related Issues

Closes: #308

Is there anything you'd like reviewers to focus on?

N/A

[lumirlumir]

Pending verification of #308 (comment).

[fasttime]

I'm not sure if it's necessary to merge this fix because this would revert the types to a less correct stand. I think the build is failing because we didn't do a minor release @eslint/[email protected] for the changes in 02bac50. Instead, everything was released in @eslint/[email protected], which npm treats as a a major release and that means that npm cannot pick it automatically when it resolves the dependencies for eslint. So eslint it continues to depend on @eslint/[email protected] and that is where the inconsistency arises:

$ ...\rewrite> npm list @eslint/core
[email protected] ...\rewrite
├─┬ @eslint/[email protected] -> .\packages\compat
│ └── @eslint/[email protected] deduped -> .\packages\core
├─┬ @eslint/[email protected] -> .\packages\config-helpers
│ └── @eslint/[email protected] deduped -> .\packages\core
├── @eslint/[email protected] -> .\packages\core
├─┬ @eslint/[email protected] -> .\packages\migrate-config
│ └── @eslint/[email protected] deduped -> .\packages\core
├─┬ @eslint/[email protected] -> .\packages\plugin-kit
│ └── @eslint/[email protected] deduped -> .\packages\core
└─┬ [email protected]
  └── @eslint/[email protected]

Another way to fix the build failure is to use an overrides in package.json make sure that eslint uses the local version of @eslint/core when it runs in this repo:

"overrides": {
  "eslint": {
    "@eslint/core": "file:packages/core"
  }
}

[lumirlumir]

@fasttime Thanks for the solution and guidance!

I've updated this PR according to your comment, and I've also updated the PR title to reflect the change.

[fasttime]

LGTM, thanks!