Edit(JoshuaKGoldberg): ✨ typescript-eslint@8.10.0 ✨

Edit(JoshuaKGoldberg): We're currently blocked on microsoft/rushstack#4919

We haven't had the bandwidth to investigate and try helping them fix it. If anyone is so motivated - fixing that would unblock us and allow us to support 5.6.

https://devblogs.microsoft.com/typescript/announcing-typescript-5-6-beta/

Please read through our TypeScript version policy: https://typescript-eslint.io/users/dependency-versions#typescript

This issue is just to track all of the new features and their implementation state in this project.
As with all releases, we will not necessarily to support all features until closer to the full release when everything the features are stabilised.

Please be patient.

🔗 Disallowed Nullish and Truthy Checks: #9973

Moved to issue #9973. This does not block supporting TypeScript 5.6.

As they mention in the post - this is essentially a weaker version of no-constant-binary-expression. There will be a lot of overlap between the rules.

Perhaps we should create an extension rule to remove the duplicates so users can have the rest of the rule without the duplicate reports?

🏗 Support for Arbitrary Module Identifiers: #9972

We will need to update our AST types as per the estree spec.

🏗 Search Ancestor Configuration Files for Project Ownership: #9972

Perhaps we should follow their logic and update our project: true logic?

🏗 lib.d.ts Updates: #9972

We will need to regenerate our types within scope-manager.

Other changes with no impact to us

• Iterator Helper Methods
• Strict Builtin Iterator Checks (and --strictBuiltinIteratorReturn)
• The --noUncheckedSideEffectImports Option
• The --noCheck Option
• Allow --build with Intermediate Errors
• Region-Prioritized Diagnostics in Editors
• Notable Behavioral Changes
  • .tsbuildinfo is Always Written
  • Respecting File Extensions and package.json from within node_modules
  • Correct override Checks on Computed Properties