Bump eslint from 9.39.3 to 10.0.0

[dependabot]

Bumps eslint from 9.39.3 to 10.0.0.

Release notes

Sourced from eslint's releases.

v10.0.0

Breaking Changes

• f9e54f4 feat!: estimate rule-tester failure location (#20420) (ST-DDT)
• a176319 feat!: replace chalk with styleText and add color to ResultsMeta (#20227) (루밀LuMir)
• c7046e6 feat!: enable JSX reference tracking (#20152) (Pixel998)
• fa31a60 feat!: add name to configs (#20015) (Kirk Waiblinger)
• 3383e7e fix!: remove deprecated SourceCode methods (#20137) (Pixel998)
• 501abd0 feat!: update dependency minimatch to v10 (#20246) (renovate[bot])
• ca4d3b4 fix!: stricter rule tester assertions for valid test cases (#20125) (唯然)
• 96512a6 fix!: Remove deprecated rule context methods (#20086) (Nicholas C. Zakas)
• c69fdac feat!: remove eslintrc support (#20037) (Francesco Trotta)
• 208b5cc feat!: Use ScopeManager#addGlobals() (#20132) (Milos Djermanovic)
• a2ee188 fix!: add uniqueItems: true in no-invalid-regexp option (#20155) (Tanuj Kanti)
• a89059d feat!: Program range span entire source text (#20133) (Pixel998)
• 39a6424 fix!: assert 'text' is a string across all RuleFixer methods (#20082) (Pixel998)
• f28fbf8 fix!: Deprecate "always" and "as-needed" options of the radix rule (#20223) (Milos Djermanovic)
• aa3fb2b fix!: tighten func-names schema (#20119) (Pixel998)
• f6c0ed0 feat!: report eslint-env comments as errors (#20128) (Francesco Trotta)
• 4bf739f fix!: remove deprecated LintMessage#nodeType and TestCaseError#type (#20096) (Pixel998)
• 523c076 feat!: drop support for jiti < 2.2.0 (#20016) (michael faith)
• 454a292 feat!: update eslint:recommended configuration (#20210) (Pixel998)
• 4f880ee feat!: remove v10_* and inactive unstable_* flags (#20225) (sethamus)
• f18115c feat!: no-shadow-restricted-names report globalThis by default (#20027) (sethamus)
• c6358c3 feat!: Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#20160) (Milos Djermanovic)

Features

• bff9091 feat: handle Array.fromAsync in array-callback-return (#20457) (Francesco Trotta)
• 290c594 feat: add self to no-implied-eval rule (#20468) (sethamus)
• 43677de feat: fix handling of function and class expression names in no-shadow (#20432) (Milos Djermanovic)
• f0cafe5 feat: rule tester add assertion option requireData (#20409) (fnx)
• f7ab693 feat: output RuleTester test case failure index (#19976) (ST-DDT)
• 7cbcbf9 feat: add countThis option to max-params (#20236) (Gerkin)
• f148a5e feat: add error assertion options (#20247) (ST-DDT)
• 09e6654 feat: update error loc of require-yield and no-useless-constructor (#20267) (Tanuj Kanti)

Bug Fixes

• 436b82f fix: update eslint (#20473) (renovate[bot])
• 1d29d22 fix: detect default this binding in Array.fromAsync callbacks (#20456) (Francesco Trotta)
• 727451e fix: fix regression of global mode report range in strict rule (#20462) (ntnyq)
• e80485f fix: remove fake FlatESLint and LegacyESLint exports (#20460) (Francesco Trotta)
• 9eeff3b fix: update esquery (#20423) (cryptnix)
• b34b938 fix: use Error.prepareStackTrace to estimate failing test location (#20436) (Francesco Trotta)
• 51aab53 fix: update eslint (#20443) (renovate[bot])
• 23490b2 fix: handle space before colon in RuleTester location estimation (#20433) (Francesco Trotta)
• f244dbf fix: use MessagePlaceholderData type from @eslint/core (#20348) (루밀LuMir)
• d186f8c fix: update eslint (#20427) (renovate[bot])
• 2332262 fix: error location should not modify error message in RuleTester (#20421) (Milos Djermanovic)
• ab99b21 fix: ensure filename is passed as third argument to verifyAndFix() (#20405) (루밀LuMir)
• 8a60f3b fix: remove ecmaVersion and sourceType from ParserOptions type (#20415) (Pixel998)
• eafd727 fix: remove TDZ scope type (#20231) (jaymarvelz)

... (truncated)

Commits

• 4e6c4ac 10.0.0
• ddd8a22 Build: changelog update for 10.0.0
• bff9091 feat: handle Array.fromAsync in array-callback-return (#20457)
• 1ece282 chore: ignore /docs/v9.x in link checker (#20452)
• 034e139 ci: add type integration test for @html-eslint/eslint-plugin (#20345)
• f3fbc2f chore: set @eslint/js version to 10.0.0 to skip releasing it (#20466)
• e978dda docs: Update README
• 4cecf83 docs: Update README
• c79f0ab docs: Update README
• afc0681 chore: remove scopeManager.addGlobals patch for typescript-eslint parser (#20...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

QA Instructions

Summary

This PR upgrades eslint from version 9.39.3 to 10.0.0. The upgrade involves major changes, including breaking changes and dependency updates. Key updates involve modifying APIs, adding stricter validations, and updating Node.js requirements.

Test Environment Setup

1. Ensure the local environment satisfies Node.js version requirements (^20.19.0 || ^22.13.0 || >=24 as per eslint 10.0.0).
2. Remove node_modules and package-lock.json.
3. Run npm install to install dependencies using the updated package.json and package-lock.json files.

Test Scenarios

1. Basic Functionality Test

   • Run npm run lint on the project.
   • Expected Result: ESLint successfully lints all files without crashing, and no unusual errors appear.

2. Updated Rules and Features

   • Test the following scenarios from the breaking changes/new features list to ensure correct handling:
     • Cases involving JSX reference tracking. Verify that unused JSX references are flagged correctly.
     • Cases where eslint-env comments are used. Confirm errors are reported for invalid usages.
     • Validation of func-names schema tightening with function expression cases.
     • Ensure the new max-params rule with countThis works as expected.
     • Test behavior of array-callback-return with Array.fromAsync.
   • Expected Result: ESLint detects issues or passes correctly in line with the updated guidelines.

3. Backward Compatibility Test

   • Review existing .eslintrc.js or configuration files. Verify they do not use any deprecated configurations or removed features (e.g., deprecation of eslintrc support).
   • Verify that existing linting error messages and autofix capabilities still function as expected.
   • Expected Result: Existing configurations work without modification or provide actionable warnings/errors when deprecated or removed features are used.

4. Third-party Plugin Compatibility

   • If third-party ESLint plugins are in use, run tests with those plugins enabled (e.g., eslint-plugin-prettier) to ensure compatibility.
   • Expected Result: No critical errors arise, and the plugins work as expected with the updated ESLint version.

Regression Risks

1. Rule Changes:

   • Rule behavior has changed for several rules like func-names, no-useless-constructor, etc. Some previously acceptable/tested code may now break or raise warnings/errors.

2. Configuration:

   • .eslintrc support has been removed. Ensure existing projects are compliant with the updated ESLint configuration standards.

3. Node.js Compatibility:

   • Verify compatibility for development environments using Node.js versions older than 20 or unsupported minor versions before upgrading.

Things to Watch For

1. Run tests in CI environments to confirm no environment-specific Node.js version issues arise.
2. Watch for potential changes in error formats or locations that could affect test scripts or reports dependent on previous error reporting formats.

---

Generated by QA Instructions Action