Bump @typescript-eslint/parser from 5.62.0 to 7.2.0

[dependabot]

Bumps @typescript-eslint/parser from 5.62.0 to 7.2.0.

Release notes

Sourced from @​typescript-eslint/parser's releases.

v7.2.0

7.2.0 (2024-03-11)

🚀 Features

• support TS 5.4 (#8630)
• eslint-plugin: [prefer-string-starts-ends-with] add allowSingleElementEquality option (#8374)

🩹 Fixes

• eslint-plugin: expose *-type-checked-only configs for extension (#8600)
• eslint-plugin: [member-ordering] report alphabetical sorting for all groups instead of just the first failing group (#8263)
• eslint-plugin: [no-var-requires, no-require-imports] support template literal (#8408)
• eslint-plugin: [no-useless-template-literals] detect TemplateLiteral (#8575)
• eslint-plugin: [no-unnecessary-condition] handle union array and tuple type (#8592)
• eslint-plugin: [prefer-find] support ternary branches in prefer-find (#8421)
• typescript-eslint: set sourceType: "module" in base shared config (#8622)
• typescript-eslint: export ConfigWithExtends type (#8621)

❤️ Thank You

• Arka Pratim Chaudhuri @​arka1002
• auvred @​auvred
• Chris Plummer
• Fotis Papadogeorgopoulos @​fpapado
• Josh Goldberg ✨
• Kirk Waiblinger @​kirkwaiblinger
• Wayne Zhang
• YeonJuan @​yeonjuan

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

v7.1.1

7.1.1 (2024-03-04)

🩹 Fixes

• typescript-eslint: apply ignores to all extended configs passed to config helper function (#8567)

❤️ Thank You

• auvred @​auvred

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

v7.1.0

7.1.0 (2024-02-26)

... (truncated)

Changelog

Sourced from @​typescript-eslint/parser's changelog.

7.2.0 (2024-03-11)

🚀 Features

• support TS 5.4

❤️ Thank You

• Arka Pratim Chaudhuri
• auvred
• Chris Plummer
• Fotis Papadogeorgopoulos
• Josh Goldberg ✨
• Kirk Waiblinger
• Wayne Zhang
• YeonJuan

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

7.1.1 (2024-03-04)

This was a version bump only for parser to align it with other projects, there were no code changes.

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

7.1.0 (2024-02-26)

This was a version bump only for parser to align it with other projects, there were no code changes.

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

7.0.2 (2024-02-19)

🩹 Fixes

• fix tsconfig-less check errors, fix @types/eslint incompatibilities, add tests

❤️ Thank You

• Brad Zacher
• Gareth Jones

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

7.0.1 (2024-02-12)

... (truncated)

Commits

• 95cf139 chore(release): publish 7.2.0
• 88b7463 chore(release): publish 7.1.1
• 4bc6944 chore(release): publish 7.1.0
• 677e7cc chore(release): publish 7.0.2
• 4f3215f chore(release): publish 7.0.1
• b27de99 chore(release): publish 7.0.0
• 1aa393c chore(deps): update dependency prettier to v3.2.5 (#8401)
• 8ef5f4b feat: add support for flat configs (#7935)
• 1200b4c chore(deps): update nx to v17.3.0 (#8317)
• 584db29 feat: bump ESLint, NodeJS, and TS minimum version requirements (#8377)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[pull-request-quantifier-deprecated]

This PR has 2 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       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

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.

[dependabot]

Superseded by #173.