Update dependency prettier to v1.19.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
prettier (source)	1.17.0 → 1.19.1

---

Release Notes

prettier/prettier (prettier)

v1.19.1

Compare Source

diff

CLI

Fix --stdin regression in 1.19.0 (#​6894 by @​lydell)

// Prettier stable
$ echo "test" | prettier --stdin --parser babel
[error] regeneratorRuntime is not defined

// Prettier master
$ echo "test" | prettier --stdin --parser babel
test;

TypeScript

Fix formatting of union type as arrow function return type (#​6896 by @​thorn0)

// Input
export const getVehicleDescriptor = async (
  vehicleId: string,
): Promise<Collections.Parts.PrintedCircuitBoardAssembly['attributes'] | undefined> => {}

// Prettier stable
export const getVehicleDescriptor = async (
  vehicleId: string
): Promise<| Collections.Parts.PrintedCircuitBoardAssembly["attributes"]
| undefined> => {};

// Prettier master
export const getVehicleDescriptor = async (
  vehicleId: string
): Promise<
  Collections.Parts.PrintedCircuitBoardAssembly["attributes"] | undefined
> => {};

v1.19.0

Compare Source

diff

🔗 Release Notes

v1.18.2

Compare Source

diff

• TypeScript: only add trailing commas in tuples for --trailing-comma=all (#​6199 by @​duailibe)

  In Prettier 1.18 we added trailing commas in tuples when --trailing-comma=all, but it was also adding for --trailing-comma=es5.

v1.18.1

Compare Source

diff

• TypeScript: Add trailing comma in tsx, only for arrow function (#​6190 by @​sosukesuzuki)

  Prettier inserts a trailing comma to single type parameter for arrow functions in tsx, since v 1.18. But, this feature inserts a trailing comma to type parameter for besides arrow functions too (e.g, function , interface). This change fix it.

  // Input
  interface Interface1<T> {
    one: "one";
  }
  function function1<T>() {
    return "one";
  }
  
  // Output (Prettier 1.18.0)
  interface Interface1<T,> {
    one: "one";
  }
  function function1<T,>() {
    return "one";
  }
  
  // Output (Prettier 1.18.1)
  interface Interface1<T> {
    one: "one";
  }
  function function1<T>() {
    return "one";
  }

• Config: Match dotfiles in config overrides (#​6194 by @​duailibe)

  When using overrides in the config file, Prettier was not matching dotfiles (files that start with .). This was fixed in 1.18.1

v1.18.0

Compare Source

diff

🔗 Release Notes

v1.17.1

Compare Source

diff

• Range: Fix ranged formatting not using the correct line width (#​6050 by @​mathieulj)

  // Input
  function f() {
    if (true) {
      call("this line is 79 chars", "long", "it should", "stay as single line");
    }
  }
  
  // Output (Prettier 1.17.0 run with --range-start 30 --range-end 110)
  function f() {
    if (true) {
      call(
        "this line is 79 chars",
        "long",
        "it should",
        "stay as single line"
      );
    }
  }
  
  // Output (Prettier 1.17.0 run without range)
  function f() {
    if (true) {
      call("this line is 79 chars", "long", "it should", "stay as single line");
    }
  }
  
  // Output (Prettier 1.17.1 with and without range)
  function f() {
    if (true) {
      call("this line is 79 chars", "long", "it should", "stay as single line");
    }
  }

• JavaScript: Fix closure compiler typecasts ([#​5947] by @​jridgewell)

  If a closing parenthesis follows after a typecast in an inner expression, the typecast would wrap everything to the that following parenthesis.

  // Input
  test(/** @​type {!Array} */(arrOrString).length);
  test(/** @​type {!Array} */((arrOrString)).length + 1);
  
  // Output (Prettier 1.17.0)
  test(/** @​type {!Array} */ (arrOrString.length));
  test(/** @​type {!Array} */ (arrOrString.length + 1));
  
  // Output (Prettier 1.17.1)
  test(/** @​type {!Array} */ (arrOrString).length);
  test(/** @​type {!Array} */ (arrOrString).length + 1);

• JavaScript: respect parenthesis around optional chaining before await (#​6087 by @​evilebottnawi)

  // Input
  async function myFunction() {
    var x = (await foo.bar.blah)?.hi;
  }
  
  // Output (Prettier 1.17.0)
  async function myFunction() {
    var x = await foo.bar.blah?.hi;
  }
  
  // Output (Prettier 1.17.1)
  async function myFunction() {
    var x = (await foo.bar.blah)?.hi;
  }

• Handlebars: Fix {{else}}{{#if}} into {{else if}} merging (#​6080 by @​dcyriller)

  // Input
  {{#if a}}
    a
  {{else}}
    {{#if c}}
      c
    {{/if}}
    e
  {{/if}}
  
  // Output (Prettier 1.17.0)
  {{#if a}}
    a
  {{else if c}}
    c
  e
  {{/if}}
  
  // Output (Prettier 1.17.1)
  Code Sample
  {{#if a}}
    a
  {{else}}
    {{#if c}}
      c
    {{/if}}
    e
  {{/if}}
  

• JavaScript: Improved multiline closure compiler typecast comment detection (#​6070 by @​yangsu)

  Previously, multiline closure compiler typecast comments with lines that
  start with * weren't flagged correctly and the subsequent parenthesis were
  stripped. Prettier 1.17.1 fixes this issue.

  // Input
  const style =/**
   * @​type {{
   *   width: number,
   * }}
  */({
    width,
  });
  
  // Output (Prettier 1.17.0)
  const style =/**
   * @​type {{
   *   width: number,
   * }}
  */ {
    width,
  };
  
  // Output (Prettier 1.17.1)
  const style =/**
   * @​type {{
   *   width: number,
   * }}
  */({
    width,
  });

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 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 warn ERESOLVE overriding peer dependency
npm warn While resolving: eslint-plugin-graphql@2.1.1
npm warn Found: graphql@14.2.0
npm warn node_modules/graphql
npm warn   peer graphql@"^14.1.0" from @gatsbyjs/relay-compiler@2.0.0-printer-fix.2
npm warn   node_modules/@gatsbyjs/relay-compiler
npm warn     @gatsbyjs/relay-compiler@"2.0.0-printer-fix.2" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn   9 more (apollo-link, apollo-utilities, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer graphql@"^0.12.0 || ^0.13.0" from eslint-plugin-graphql@2.1.1
npm warn node_modules/eslint-plugin-graphql
npm warn   eslint-plugin-graphql@"^2.0.0" from gatsby@2.3.4
npm warn   node_modules/gatsby
npm warn
npm warn Conflicting peer dependency: graphql@0.13.2
npm warn node_modules/graphql
npm warn   peer graphql@"^0.12.0 || ^0.13.0" from eslint-plugin-graphql@2.1.1
npm warn   node_modules/eslint-plugin-graphql
npm warn     eslint-plugin-graphql@"^2.0.0" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: express-graphql@0.6.12
npm warn Found: graphql@14.2.0
npm warn node_modules/graphql
npm warn   peer graphql@"^14.1.0" from @gatsbyjs/relay-compiler@2.0.0-printer-fix.2
npm warn   node_modules/@gatsbyjs/relay-compiler
npm warn     @gatsbyjs/relay-compiler@"2.0.0-printer-fix.2" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn   9 more (apollo-link, apollo-utilities, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer graphql@"^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0" from express-graphql@0.6.12
npm warn node_modules/express-graphql
npm warn   express-graphql@"^0.6.12" from gatsby@2.3.4
npm warn   node_modules/gatsby
npm warn
npm warn Conflicting peer dependency: graphql@0.13.2
npm warn node_modules/graphql
npm warn   peer graphql@"^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0" from express-graphql@0.6.12
npm warn   node_modules/express-graphql
npm warn     express-graphql@"^0.6.12" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: gatsby-plugin-sass@2.0.11
npm error Found: node-sass@7.0.0
npm error node_modules/node-sass
npm error   node-sass@"7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer node-sass@"^4.9.0" from gatsby-plugin-sass@2.0.11
npm error node_modules/gatsby-plugin-sass
npm error   gatsby-plugin-sass@"2.0.11" from the root project
npm error
npm error Conflicting peer dependency: node-sass@4.14.1
npm error node_modules/node-sass
npm error   peer node-sass@"^4.9.0" from gatsby-plugin-sass@2.0.11
npm error   node_modules/gatsby-plugin-sass
npm error     gatsby-plugin-sass@"2.0.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-08T17_57_40_563Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-08T17_57_40_563Z-debug-0.log