"@typescript-eslint/eslint-plugin" and "@typescript-eslint/parser" fail to resolve with yarn versions >= 3.0.0

[NickLediet]

I was following the "Running the demo" section of the contribution page in the wiki and came across the following error when running yarn to install the dependencies:

➤ YN0001: │ Error: @typescript-eslint/eslint-plugin@^6.2.00 isn't supported by any available resolver

I noticed the extra 0 on the end of the semver and figured that was the culprit. It also appeared that @typescript-eslint/parser also had an extra 0 on the end of the semver.

I retried running yarn at version 1.22.22 like the CI and it resolved the dependencies without any issues.
I tested various major and minor releases of yarn and it appears the issue is replicated on all versions >= 3.0.0.

I wanted to confirm that the additional 0 at the end of the semver was not intentional before opening a PR to address it.

Details

• Browser and browser version: N/A
• OS version: macos sequoia 15.0
• xterm.js version: 5.5.0
• Yarn Version: 3.0.0 or greater

Steps to reproduce

1. Install yarn 3.0.0 or greater (or use a version manager for this, I'm using volta
2. Reset yarn cache with yarn cache clean
3. Remove node modules rm -rf node_modules
4. Install and resolve fresh deps with yarn (or volta run --yarn 3.0.0 yarn)

[jerch]

@NickLediet I'd say those are typos, which entered the stage in this PR #4612 (commit: 859c9ec)

Interesting, that yarn on an older version would let this pass, as far as I understand semver rules, leading zero should not be allowed to not mess up version sorting. My guess is, that the newer yarn package fixed that, while we did not spot the typo due to still being on older yarn.