chore(deps): update dependency prettier to v2.8.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
prettier (source)	2.3.1 → 2.8.8

---

Release Notes

prettier/prettier (prettier)

v2.8.8

Compare Source

v2.8.7

Compare Source

v2.8.6

Compare Source

v2.8.5

Compare Source

v2.8.4

Compare Source

v2.8.3

Compare Source

v2.8.2

Compare Source

v2.8.1

Compare Source

v2.8.0

Compare Source

v2.7.1

Compare Source

v2.7.0

Compare Source

v2.6.2

Compare Source

v2.6.1

Compare Source

diff

Ignore loglevel when printing information (#​12477 by @​fisker)

v2.6.0

Compare Source

prettier --loglevel silent --find-config-path index.js

v2.5.1

Compare Source

diff

Improve formatting for empty tuple types (#​11884 by @​sosukesuzuki)

// Input
type Foo =
  Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooo extends []
    ? Foo3
    : Foo4;

// Prettier 2.5.0
type Foo = Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooo extends [

]
  ? Foo3
  : Foo4;

// Prettier 2.5.0 (tailingCommma = all)
// Invalid TypeScript code
type Foo = Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooo extends [
  ,
]
  ? Foo3
  : Foo4;

// Prettier 2.5.1
type Foo =
  Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooo extends []
    ? Foo3
    : Foo4;

Fix compatibility with Jest inline snapshot test (#​11892 by @​fisker)

A internal change in Prettier@​v2.5.0 accidentally breaks the Jest inline snapshot test.

Support Glimmer's named blocks (#​11899 by @​duailibe)

Prettier already supported this feature, but it converted empty named blocks to self-closing, which is not supported by the Glimmer compiler.

See: Glimmer's named blocks.

// Input
<Component>
  <:named></:named>
</Component>

// Prettier 2.5.0
<Component>
  <:named />
</Component>

// Prettier 2.5.1
<Component>
  <:named></:named>
</Component>

v2.5.0

Compare Source

diff

🔗 Release Notes

v2.4.1

Compare Source

diff

Fix wildcard syntax in @forward (#​11482) (#​11487 by @​niksy)

// Input
@​forward "library" as btn-*;

// Prettier 2.4.0
@​forward "library" as btn- *;

// Prettier 2.4.1
@​forward "library" as btn-*;

Add new CLI option debug-print-ast (#​11514 by @​sosukesuzuki)

A new --debug-print-ast CLI flag for debugging.

v2.4.0

Compare Source

diff

🔗 Release Notes

v2.3.2

Compare Source

diff

Fix failure on dir with trailing slash (#​11000 by @​fisker)

$ ls
1.js  1.unknown

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin"} (current: {"os":"linux","arch":"x64"})
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  undefined
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: x64

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/3b6f6f/cab01e/cache/others/npm/_logs/2023-05-28T12_25_42_995Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code EBADPLATFORM
npm error notsup Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin"} (current: {"os":"linux"})
npm error notsup Valid os:  darwin
npm error notsup Actual os: linux
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-12T17_27_30_851Z-debug-0.log