Bump @typescript-eslint/parser from 5.62.0 to 7.4.0

[dependabot]

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

Release notes

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

v7.4.0

7.4.0 (2024-03-25)

🚀 Features

• eslint-plugin: [consistent-type-imports] ignore files with decorators, experimentalDecorators, and emitDecoratorMetadata (#8335)
  • Check out our blog post on this change for more information! https://typescript-eslint.io/blog/changes-to-consistent-type-imports-with-decorators
• eslint-plugin: [no-unnecessary-type-arguments] handle tagged templates (#8708)
• eslint-plugin: deprecate no-throw-literal and add a renamed only-throw-error (#8701)

🩹 Fixes

• eslint-plugin: [prefer-optional-chain] address multipart nullish checks false positive (#8678)
• eslint-plugin: [prefer-optional-chain] properly disambiguate between boolean and false (#8685)
• eslint-plugin: [no-unnecessary-type-assertion] avoid remove const casting on template literals with expressions inside (#8740)
• typescript-eslint: declare peer dependency on utils to ensure npm correctly installs dependencies (#8738)
• website: visual Editor is not scrolled (#8709)
• website: make 404 page good again (#8750)

❤️ Thank You

• Abraham Guo
• Brad Zacher @​bradzacher
• Josh Goldberg ✨
• Kim Sang Du @​developer-bandi
• Kirk Waiblinger @​kirkwaiblinger
• Marco Pasqualetti @​marcalexiei
• YeonJuan @​yeonjuan

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

v7.3.1

7.3.1 (2024-03-18)

🩹 Fixes

• eslint-plugin: [no-floating-promises] revert disable of ignoreVoid in strict config (#8718)

❤️ Thank You

• Josh Goldberg ✨

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

v7.3.0

7.3.0 (2024-03-18)

Note that this release enables rules to have more restrictive default options as configured in the strict and strict-type-checked configs. See #8364 for more details.

... (truncated)

Changelog

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

7.4.0 (2024-03-25)

🚀 Features

• eslint-plugin: [consistent-type-imports] ignore files with decorators, experimentalDecorators, and emitDecoratorMetadata

❤️ Thank You

• Abraham Guo
• Brad Zacher
• Josh Goldberg ✨
• Kim Sang Du
• Kirk Waiblinger
• Marco Pasqualetti
• YeonJuan

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

7.3.1 (2024-03-18)

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.3.0 (2024-03-18)

🩹 Fixes

• correct engines.node constraints in package.json

❤️ Thank You

• Abraham Guo
• Alexu
• Arka Pratim Chaudhuri
• auvred
• Derrick Isaacson
• fnx
• Josh Goldberg ✨
• Kirk Waiblinger
• Marta Cardoso
• Michaël De Boey
• Tristan Rasmussen
• YeonJuan

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

... (truncated)

Commits

• 5d24691 chore(release): publish 7.4.0
• e408b93 feat(eslint-plugin): [consistent-type-imports] ignore files with decorators, ...
• 5995614 chore(release): publish 7.3.1
• 4cf8ec7 chore(release): publish 7.3.0
• 883f220 fix: correct engines.node constraints in package.json (#8671)
• 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
• 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 #177.