chore(deps): update dependency prettier to ^3.2.5

[tradeshift-renovate]

This PR contains the following updates:

Package	Type	Update	Change
prettier (source)	devDependencies	patch	^3.0.0 -> ^3.2.5

---

Release Notes

prettier/prettier (prettier)

v3.2.5

Compare Source

diff

Support Angular inline styles as single template literal (#​15968 by @​sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@​Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.4
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.5
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `
    h1 {
      color: blue;
    }
  `,
})
export class AppComponent {}

Unexpected embedded formatting for Angular template (#​15969 by @​JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

@​Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.4
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.5
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

Use "json" parser for tsconfig.json by default (#​16012 by @​sosukesuzuki)

In v3.2.0, we introduced "jsonc" parser which adds trailing comma by default.

When adding a new parser we also define how it will be used based on the linguist-languages data.

tsconfig.json is a special file used by TypeScript, it uses .json file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing .json file extension.

We decide to treat it as a JSON file for now to avoid the extra configuration step.

To keep using the "jsonc" parser for your tsconfig.json files, add the following to your .prettierrc file

{
  "overrides": [
    {
      "files": ["tsconfig.json", "jsconfig.json"],
      "options": {
        "parser": "jsonc"
      }
    }
  ]
}

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "every weekday in 2125" in timezone Europe/Copenhagen.

🚦 Automerge: Enabled.

♻️ Rebasing: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Renovate Bot.

[tradeshift-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 config cert `key` and `cert` are no longer used for most registry operations.
npm WARN config Use registry scoped `keyfile` and `certfile` instead.
npm WARN config     Example:
npm WARN config     //other-registry.tld/:keyfile=/path/to/key.pem
npm WARN config     //other-registry.tld/:certfile=/path/to/cert.crt
npm WARN config key `key` and `cert` are no longer used for most registry operations.
npm WARN config Use registry scoped `keyfile` and `certfile` instead.
npm WARN config     Example:
npm WARN config     //other-registry.tld/:keyfile=/path/to/key.pem
npm WARN config     //other-registry.tld/:certfile=/path/to/cert.crt
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @rollup/plugin-babel@6.0.3
npm ERR! Found: rollup@4.9.6
npm ERR! node_modules/rollup
npm ERR!   dev rollup@"^4.0.0" from the root project
npm ERR!   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0||^4.0.0" from @rollup/plugin-json@6.1.0
npm ERR!   node_modules/@rollup/plugin-json
npm ERR!     dev @rollup/plugin-json@"^6.0.0" from the root project
npm ERR!   2 more (@rollup/plugin-node-resolve, @rollup/pluginutils)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/plugin-babel@6.0.3
npm ERR! node_modules/@rollup/plugin-babel
npm ERR!   dev @rollup/plugin-babel@"^6.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: rollup@3.29.4
npm ERR! node_modules/rollup
npm ERR!   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/plugin-babel@6.0.3
npm ERR!   node_modules/@rollup/plugin-babel
npm ERR!     dev @rollup/plugin-babel@"^6.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-06T11_29_58_884Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-06T11_29_58_884Z-debug-0.log