build(deps-dev): bump prettier from 2.8.8 to 3.2.2

[dependabot]

Bumps prettier from 2.8.8 to 3.2.2.

Release notes

Sourced from prettier's releases.

3.2.2

🔗 Changelog

3.2.1

🔗 Changelog

3.2.0

diff

🔗 Release note

3.1.1

🔗 Changelog

3.1.0

diff

🔗 Release note

3.0.3

🔗 Changelog

3.0.2

🔗 Changelog

3.0.1

🔗 Changelog

3.0.0

diff

🔗 Release note

3.0.0-alpha.6

What's Changed

• Update .d.ts files of plugins to use export default ... by @​fisker in prettier/prettier#14435

Other changes since v2, see 3.0.0-alpha.1 release notes

Full Changelog: prettier/prettier@3.0.0-alpha.5...3.0.0-alpha.6

3.0.0-alpha.5

What's Changed

• Add .d.ts files by @​sosukesuzuki in prettier/prettier#14212
• Support TypeScript 5 via babel-ts parser by @​fisker in prettier/prettier#14391

Other changes since v2, see 3.0.0-alpha.1 release notes

Full Changelog: prettier/prettier@3.0.0-alpha.4...3.0.0-alpha.5

... (truncated)

Changelog

Sourced from prettier's changelog.

3.2.2

diff

Fix crash when parsing template literal CSS in a JSX style tag using a spread attribute (#15896 by @​eelco)

For example this code would crash before:

<style {...spread}>{`.{}`}</style>

Fix formatting error on optional call expression and member chain (#15920 by @​sosukesuzuki)

// Input
a(() => {}, c?.d());
// Prettier 3.2.1
TypeError: Cannot read properties of undefined (reading 'type')
// Prettier 3.2.2
a(() => {}, c?.d());

3.2.1

diff

Fix formatting error on member chain (#15915 by @​sosukesuzuki)

// Input
test().test2().test2(thing?.something);
// Prettier 3.2.0
TypeError: Cannot read properties of undefined (reading 'type')
// Prettier 3.2.1
test().test2().test2(thing?.something);

3.2.0

diff

... (truncated)

Commits

• 5f2c6df Release 3.2.2
• cb8004f Fix formatting error on optional call expression and member chain (#15920)
• 0bfcb2d Fix css embed in JSX when using (only) a spread attribute (#15896)
• 12ab548 Add prettier-plugin-gherkin to the community plugins list (#15919)
• 4ce96dd Fix typo (#15917)
• 08f3796 Run yarn
• 11aea0d Clean changelog_unreleased
• 75e66b8 Git blame ignore 3.2.1
• 5811ad0 Bump Prettier dependency to 3.2.1
• 48ad208 Release 3.2.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 will merge this PR once CI passes on it, as requested by @typestack-ci.

---

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)

[typestack-ci]

@dependabot squash and merge

[dependabot]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

[dependabot]

Superseded by #1670.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.