chore(deps-dev): bump prettier from 2.4.1 to 2.8.4

[dependabot]

Bumps prettier from 2.4.1 to 2.8.4.

Release notes

Sourced from prettier's releases.

2.8.4

🔗 Changelog

2.8.3

Support Angular 15.1

🔗 Changelog

2.8.2

🔗 Changelog

2.8.1

🔗 Changelog

2.8.0

diff

🔗 Release note

2.7.1

🔗 Changelog

2.7.0

diff

🔗 Release note

2.6.2

🔗 Changelog

2.6.1

🔗 Changelog

2.6.0

🔗 Release note

2.5.1

🔗 Changelog

2.5.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

2.8.4

diff

Fix leading comments in mapped types with readonly (#13427 by @​thorn0, @​sosukesuzuki)

// Input
type Type = {
  // comment
  readonly [key in Foo];
};
// Prettier 2.8.3
type Type = {
readonly // comment
[key in Foo];
};
// Prettier 2.8.4
type Type = {
// comment
readonly [key in Foo];
};

Group params in opening block statements (#14067 by @​jamescdavis)

This is a follow-up to #13930 to establish wrapping consistency between opening block statements and else blocks by grouping params in opening blocks. This causes params to break to a new line together and not be split across lines unless the length of params exceeds the print width. This also updates the else block wrapping to behave exactly the same as opening blocks.

{{! Input }}
{{#block param param param param param param param param param param as |blockParam|}}
  Hello
{{else block param param param param param param param param param param as |blockParam|}}
  There
{{/block}}
{{! Prettier 2.8.3 }}
{{#block
param
param
param
param
param
</tr></table>

... (truncated)

Commits

• e681edb Release 2.8.4
• 6bb24b2 Fix leading comments in mapped types with readonly (Cherry-pick #13427) (#1...
• 399f2fa Add changelog for #14206 (#14311)
• 9842b29 Recognize @satisfies in Closure-style type casts (#14262)
• bc18fa4 Fix incorrect removal of parentheses when using an infer with a constraint ...
• f602be5 Update embeddedLanguageFormatting option documentation (#14048)
• 37fb53a [handlebars] group params in opening block statements (#14067)
• 310a5b1 Handlebars: Improve HTML void element check (#14110)
• 62195dd Add .sl to the list of silentlyIgnoredDirs (#14206)
• bf406f7 Clean changelog
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by prettier-bot, a new releaser for prettier since your current version.

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 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-checklist]

Example Check Group #2 (Click here to edit)

• Modify this checklist and click on the save button for it to appear on Github Pull Requests for this repo
• If you would like the checklist state to roll up to the Pull Request status, select the Enforce on Merge checkbox

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
dgiot-dashboard	❌ Failed (Inspect)			Feb 8, 2023 at 5:07AM (UTC)

[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.