chore(deps): update eslint monorepo to v10 (major) with package-lock.json and plugin compatibility fixes

[Copilot]

Changes proposed in this pull request:

• Regenerated package-lock.json to match package.json ESLint v10 dependencies
• Updated package.json to ESLint 10.0.0 and typescript-eslint 8.56.0
• Updated CI workflow to use --legacy-peer-deps for incompatible plugins
• Updated eslint.config.mjs to remove deprecated sonarjs rules
• Replaced eslint-plugin-import with eslint-plugin-import-x for ESLint v10 compatibility

Status: ✅ FIXED - The package-lock.json mismatch has been resolved, and ESLint v10 is now fully functional with working lint, build, and test commands.

Changes Made:

1. package.json - Updated to latest versions from base branch:

   • eslint@10.0.0 and @eslint/js@10.0.1
   • typescript-eslint@8.56.0 (with ESLint v10 support)
   • @eslint/compat@2.0.2 (for plugin compatibility)
   • eslint-plugin-import-x@4.16.1 (replaces eslint-plugin-import)
   • Other dependency updates (eslint-plugin-sonarjs 4.0.0, etc.)

2. package-lock.json - Regenerated with --legacy-peer-deps:

   • Now correctly references eslint 10.0.0 and @eslint/js 10.0.1
   • All dependencies properly resolved

3. CI workflow (.github/workflows/ci.yml):

   • Added --legacy-peer-deps flag to both npm ci commands
   • Required because eslint-find-rules@5.0.0 doesn't support ESLint v10 yet

4. eslint.config.mjs:

   • Updated from base branch to remove deprecated sonarjs/code-eval rule
   • Replaced eslint-plugin-import with eslint-plugin-import-x
   • Added @eslint/compat and wrapped import-x with fixupPluginRules() for ESLint v10 compatibility
   • Disabled incompatible rules:
     • import/enforce-node-protocol-usage (not available in import-x)
     • import/no-unused-modules (uses removed ESLint v10 APIs)
   • Compatible with eslint-plugin-sonarjs 4.0.0

5. Source files:

   • Auto-fixed unused eslint-disable directive in src/file-system-storage.ts
   • Auto-fixed stylistic issue in src/storage.ts

Background:

• ✅ typescript-eslint ESLint v10 support released (tracked in Enhancement: support eslint v10 typescript-eslint/typescript-eslint#11952)
• ✅ typescript-eslint@8.56.0 (released Feb 16, 2026) has peer dependency: eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
• ✅ Fixed: Renovate's automated commit updated package.json but failed to properly update package-lock.json
• ✅ Fixed: eslint-plugin-import doesn't support ESLint v10, replaced with eslint-plugin-import-x

Note: eslint-find-rules@5.0.0 doesn't officially support ESLint v10 yet, requiring the --legacy-peer-deps flag. The npm run lint command works successfully with the updated plugin configuration.

@nicolashenry

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/typescript-eslint/typescript-eslint/pulls/12052
  • Triggering command: /usr/bin/curl curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[nicolashenry]

@copilot is it solved now on typescript-eslint side?

[Copilot]

@copilot is it solved now on typescript-eslint side?

Yes! The typescript-eslint team merged ESLint v10 support on Feb 13, 2026.

Current status:

• ✅ ESLint v10 support is available in the canary version (typescript-eslint@8.55.1-alpha.4)
• ⏳ A stable release with v10 support is expected soon on their standard release schedule (typically every 2 weeks)
• The latest stable version (8.55.0) does NOT support v10 yet

For this PR:
You can wait for the next stable release (likely v8.56.0 or v8.55.1), or use the canary version if you want to test now. Once the stable version is released, renovate should be able to update all dependencies together without conflicts.

[nicolashenry]

@copilot check again

[Copilot]

@copilot check again

✅ Great news! typescript-eslint@8.56.0 was released today (Feb 16, 2026) with full ESLint v10 support!

What this means:

• The blocker is now resolved
• typescript-eslint@8.56.0 has peer dependency: eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
• Renovate should automatically update the base PR (chore(deps): update eslint monorepo to v10 #3084) to include this new version

Current status:

• Base PR renovate/major-eslint-monorepo has typescript-eslint@8.55.0 (updated Feb 12)
• Needs to be bumped to 8.56.0 (released Feb 16)
• Once renovate updates the base PR, the ESLint v10 upgrade should work without conflicts

Note: Some other eslint plugins (eslint-plugin-import, eslint-plugin-jsdoc, eslint-plugin-sonarjs) don't explicitly list v10 in their peer dependencies yet, but they should work with @eslint/compat if needed, or may work without changes since their peer deps use ranges like >=8.23.0.

[nicolashenry]

@copilot There is still issue it seems

[Copilot]

@copilot There is still issue it seems

You're right - there's still an issue. The package.json has been updated to ESLint v10, but the package-lock.json is out of sync and still references ESLint 9.39.2.

The Problem:

npm error Found: @eslint/js@9.39.2
npm error   @eslint/js@"9.39.2" from eslint@9.39.2
npm error   dev @eslint/js@"10.0.1" from the root project

The package.json has:

• eslint: "10.0.0"
• @eslint/js: "10.0.1"

But package-lock.json still has:

• eslint: "9.39.2"
• @eslint/js: "9.39.2"

Root Cause:
Renovate's commit on the base PR updated package.json but the package-lock.json wasn't properly regenerated, causing a mismatch.

Solution:
The package-lock.json needs to be regenerated. This typically requires:

1. Deleting package-lock.json
2. Running npm install to create a fresh lock file
3. Committing the updated lock file

Renovate should handle this automatically, but it seems the lock file update didn't work correctly. You may need to manually trigger a rebase on the renovate PR or close/reopen it to force Renovate to regenerate the lock file.

[nicolashenry]

@copilot it does not seem to work please do it

[Copilot]

@copilot it does not seem to work please do it

Done! I've fixed the package-lock.json mismatch issue in commit 98af100.

What was fixed:

• ✅ Regenerated package-lock.json with ESLint 10.0.0 and @eslint/js 10.0.1
• ✅ Updated to typescript-eslint 8.56.0 (supports ESLint v10)
• ✅ Updated CI workflow to use --legacy-peer-deps flag
• ✅ Updated eslint.config.mjs to remove deprecated sonarjs rules

Note: Some plugins (eslint-plugin-import, eslint-find-rules) don't officially support ESLint v10 yet, so --legacy-peer-deps is needed as a temporary workaround. The npm ci command will now succeed, but there may be runtime compatibility issues with certain plugins until they release v10-compatible versions.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f3206b8) to head (98af100).
⚠️ Report is 19 commits behind head on renovate/major-eslint-monorepo.

Additional details and impacted files

@@                       Coverage Diff                        @@
##           renovate/major-eslint-monorepo     #3092   +/-   ##
================================================================
  Coverage                          100.00%   100.00%           
================================================================
  Files                                   8         8           
  Lines                                 684       684           
  Branches                              163       163           
================================================================
  Hits                                  684       684           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nicolashenry]

@copilot npm run lint do not seems to work

[Copilot]

@copilot npm run lint do not seems to work

Fixed in commit ca85f54! The issue was that eslint-plugin-import doesn't support ESLint v10.

Solution:

• Replaced eslint-plugin-import with eslint-plugin-import-x (a maintained fork)
• Added @eslint/compat package and wrapped import-x with fixupPluginRules() for compatibility
• Disabled two incompatible rules:
  • import/enforce-node-protocol-usage (not available in import-x)
  • import/no-unused-modules (uses removed ESLint v10 APIs)

npm run lint now works successfully. There are some warnings from sonarjs about global types (Map, Promise) which are false positives, but the linting process completes without errors.