fix(deps): update typescript-eslint monorepo to v6 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@typescript-eslint/eslint-plugin	^5.62.0 -> ^6.0.0
@typescript-eslint/parser	^5.62.0 -> ^6.0.0

---

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v6.0.0

Compare Source

Bug Fixes

• bumped ts-api-utils to 0.0.39 (#​6497) (217c710)
• correct handling of additionalProperties in object schemas (#​6939) (489c7a5)
• correct lint error after merge (277fdb5)
• eslint-plugin: [explicit-module-boundary-types] remove shouldTrackReferences option from schema (#​5399) (6d32734)
• eslint-plugin: allow parser@^6.0.0 (#​6630) (92908bd)
• eslint-plugin: remove valid-typeof disable in eslint-recommended (#​5381) (b82df5e)
• fix illegal decorator check (#​6723) (c456f8c)
• rename typeParameters to typeArguments where needed (#​5384) (08d757b)
• replace tsutils with ts-api-tools (#​6428) (79327b4)
• type-utils: treat intrinsic types as if they are from lib and never match error types (#​6869) (ecb57de)
• typescript-estree: account for namespace nesting in AST conversion (#​6272) (09e3877)
• update exports field in package.json files (#​6550) (53776c2)

chore

• drop support for node v14.17, v17 (#​5971) (cc62015)

Features

• add new package rule-tester (#​6777) (2ce1c1d)
• add package.json exports for public packages (#​6458) (d676683)
• bump minimum supported TS version to 4.2.4 (#​5915) (a8e71d5)
• bump ts-api-utils to v0.0.21 (#​6459) (3915661)
• bump ts-api-utils to v0.0.22 (#​6472) (b88cd23)
• drop support for ESLint v6 (#​5972) (bda806d)
• drop support for node v12 (#​5918) (7e3fe9a)
• drop support for node v14 and test against node v20 (#​7022) (e6235bf)
• eslint-plugin: [prefer-nullish-coalescing]: add support for assignment expressions (#​5234) (4bdbe67)
• eslint-plugin: [prefer-optional-chain] handle cases where the first operands are unrelated to the rest of the chain and add type info (#​6397) (02a37c4)
• eslint-plugin: [prefer-readonly-parameter-types] added an optional type allowlist (#​4436) (c9427b7)
• eslint-plugin: [restrict-plus-operands] change checkCompoundAssignments to skipCompoundAssignments (#​7027) (dc801d8)
• eslint-plugin: add config that disables type-aware linting (#​6470) (3b063cf)
• eslint-plugin: apply final v6 changes to configs (#​7110) (c13ce0b)
• eslint-plugin: deprecate no-type-alias (#​6229) (820bdf2)
• eslint-plugin: final final config changes for v6 (#​7157) (e35c5c1)
• eslint-plugin: rework configs: recommended, strict, stylistic; -type-checked (#​5251) (5346b5b), closes #​5036 #​5834 #​5882 #​5864 #​3076 #​5834 #​5882 #​5864 #​5889 #​5834 #​5882 #​5864 #​5883 #​4863 #​5381 #​5256 #​5399
• fork json schema types for better compat with ESLint rule validation (#​6963) (a4967f2)
• improve rule schemas, add test to validate schemas, add tooling to generate schema types (#​6899) (acc1a43)
• made BaseNode.parent non-optional (#​5252) (a4768f3), closes #​5036 #​5834 #​5882 #​5864 #​3076 #​5834 #​5882 #​5864 #​5889 #​5834 #​5882 #​5864 #​5883 #​4863 #​5381 #​5256 #​5399
• remove RuleTester in /utils in favour of the new /rule-tester package (#​6816) (c33f497)
• remove partial type-information program (#​6066) (7fc062a)
• typescript-estree: add type checker wrapper APIs to ParserServicesWithTypeInformation (#​6404) (62d5755)
• typescript-estree: added allowInvalidAST option to not throw on invalid tokens (#​6247) (a3b177d)
• typescript-estree: check for illegal decorators on function declarations (#​6590) (1b39cfd)
• typescript-estree: check modifiers on every node (#​6615) (62d6230)
• typescript-estree: remove optionality from AST boolean properties (#​6274) (df131e2)
• typescript-estree: throw errors for object methods without function bodies (#​6589) (1d78576)
• typescript-estree: throw errors when abstract property has initializer (#​6613) (dcdbc76)

BREAKING CHANGES

• eslint-plugin: Adds an additional class of checks to the rule
• drop support for ESLint v6
• drops support for node v17
• Bumps the minimum supported range and removes handling for old versions
• drops support for node v12

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v6.0.0

Compare Source

Bug Fixes

• update exports field in package.json files (#​6550) (53776c2)

chore

• drop support for node v14.17, v17 (#​5971) (cc62015)

Features

• add new package rule-tester (#​6777) (2ce1c1d)
• add package.json exports for public packages (#​6458) (d676683)
• drop support for ESLint v6 (#​5972) (bda806d)
• drop support for node v12 (#​5918) (7e3fe9a)
• drop support for node v14 and test against node v20 (#​7022) (e6235bf)
• remove partial type-information program (#​6066) (7fc062a)
• scope-manager: ignore ECMA version (#​5889) (f2330f7), closes #​5834 #​5882 #​5864 #​5883
• typescript-estree: added allowInvalidAST option to not throw on invalid tokens (#​6247) (a3b177d)
• typescript-estree: allow providing code as a ts.SourceFile (#​5892) (af41b7f)
• typescript-estree: deprecate createDefaultProgram (#​5890) (426d6b6)
• typescript-estree: remove optionality from AST boolean properties (#​6274) (df131e2)

BREAKING CHANGES

• drop support for ESLint v6
• drops support for node v17
• drops support for node v12

You can read about our versioning strategy and releases on our website.

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

Merging #1003 (7b2a776) into main (046d35b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main     #1003   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines           57        57           
  Branches         2         2           
=========================================
  Hits            57        57           

[pull-request-quantifier-deprecated]

This PR has 8 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +4 -4
Percentile : 3.2%

Total files changed: 3

Change summary by file extension:
.json : +4 -4
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.