Search code, repositories, users, issues, pull requests...

Bug Fixes

Override env GIT_DIR variable to resolve to the correct git dir path (#629) (5892455), closes #627

`v8.2.0`

Bug Fixes

normalize gitDir path for Windows compatibility (90e343b)

Features

throw error in runAll if outside git directory (6ac666d)

`v8.1.7`

Bug Fixes

Resolve security vulnerability in dependencies (#615) (315890a), closes #600

`v8.1.6`

Bug Fixes

update yup to 0.27.0 (#607) (0984524)

`v8.1.5`

Bug Fixes

fix issue with scoped pkg listr-update-renderer (#587) (63b085f), closes #585

`v8.1.4`

Bug Fixes

Use lodash version with prototype pollution fix (#578) (0be88a0)

`v8.1.3`

Bug Fixes

Display package name when node-please-upgrade is being used (#575) (f5bed7b)

`v8.1.2`

Bug Fixes

Avoid stashing if no staged files has been changed (#570) (#573) (8c4d9c9)

`v8.1.1`

Bug Fixes

Fix configuration validation and allow specifying custom renderers (#572) (d5e738d), closes #567

prettier/prettier

`v1.19.1`

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`

`v1.18.2`

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.

[#6199]: #6199

@duailibe: https://github.com/duailibe

`v1.18.1`

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`

`v1.17.1`

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(/** @&#8203;type {!Array} */(arrOrString).length);
test(/** @&#8203;type {!Array} */((arrOrString)).length + 1);

// Output (Prettier 1.17.0)
test(/** @&#8203;type {!Array} */ (arrOrString.length));
test(/** @&#8203;type {!Array} */ (arrOrString.length + 1));

// Output (Prettier 1.17.1)
test(/** @&#8203;type {!Array} */ (arrOrString).length);
test(/** @&#8203;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 =/**
 * @&#8203;type {{
 *   width: number,
 * }}
*/({
  width,
});

// Output (Prettier 1.17.0)
const style =/**
 * @&#8203;type {{
 *   width: number,
 * }}
*/ {
  width,
};

// Output (Prettier 1.17.1)
const style =/**
 * @&#8203;type {{
 *   width: number,
 * }}
*/({
  width,
});

`v1.17.0`

`v1.16.4`

API: Fix prettier.getSupportInfo() reporting babel parser for older versions of Prettier. (#5826 by @azz)

In version 1.16.0 of Prettier, the babylon parser was renamed to babel. Unfortunately this lead to a minor breaking change: prettier.getSupportInfo('1.15.0') would report that it supported babel, not babylon, which breaks text-editor integrations. This has now been fixed.

`v1.16.3`

TypeScript: Revert "Update typescript-estree to new package name" (#5818 by @ikatyang)

There's an internal change introduced in Prettier 1.16.2,
which updated typescript-estree to its new package name,
but unfortunately it broke the output
so we reverted it as a temporary workaround for now.

// Input
export default {
  load<K, T>(k: K, t: T) {
    return {k, t};
  }
}

// Output (Prettier 1.16.2)
export default {
  load(k: K, t: T) {
    return { k, t };
  }
};

// Output (Prettier 1.16.3)
export default {
  load<K, T>(k: K, t: T) {
    return { k, t };
  }
};

`v1.16.2`

CLI: Fix CI detection to avoid unwanted TTY behavior (#5804 by @kachkaev)

In Prettier 1.16.0 and 1.16.1, --list-different and --check logged every file in some CI environments, instead of just unformatted files.
This unwanted behavior is now fixed.
HTML: Do not format non-normal whitespace as normal whitespace (#5797 by @ikatyang)

Previously, only non-breaking whitespaces (U+00A0) are marked as non-normal whitespace,
which means other non-normal whitespaces such as non-breaking narrow whitespaces (U+202F)
could be formatted as normal whitespaces, which breaks the output. We now follow the spec to
exclude all non-ASCII whitespace from whitespace normalization.

(· represents a non-breaking narrow whitespace)
```

Prix·:·32·€


Prix : 32 €


Prix·:·32·€
```

JavaScript: Fix record type cast comment detection (#5793 by @yangsu)

Previously, type cast comments with record types were ignored and prettier
stripped the subsequent parens. Prettier 1.16.2 handles these cases correctly.

// Input
const v = /** @&#8203;type {{key: number}} */ (value);

// Output (Prettier 1.16.1)
const v = /** @&#8203;type {{key: number}} */ value;

// Output (Prettier 1.16.2)
const v = /** @&#8203;type {{key: number}} */ (value);

`v1.16.1`

JavaScript: Do not format functions with arguments as react hooks (#5778 by @SimenB)

The formatting added in Prettier 1.16 would format any function receiving an
arrow function and an array literal to match React Hook's documentation.
Prettier will now format this the same as before that change if the arrow
function receives any arguments.

// Input
["red", "white", "blue", "black", "hotpink", "rebeccapurple"].reduce(
  (allColors, color) => {
    return allColors.concat(color);
  },
  []
);

// Output (Prettier 1.16.0)
["red", "white", "blue", "black", "hotpink", "rebeccapurple"].reduce((
  allColors,
  color
) => {
  return allColors.concat(color);
}, []);

// Output (Prettier 1.16.1)
["red", "white", "blue", "black", "hotpink", "rebeccapurple"].reduce(
  (allColors, color) => {
    return allColors.concat(color);
  },
  []
);

JavaScript: Add necessary parentheses for decorators (#5785 by @ikatyang)

Parentheses for decorators with nested call expressions are optional for legacy decorators
but they're required for decorators in the current proposal.

// Input
class X {
  @&#8203;(computed().volatile())
  prop
}

// Output (Prettier 1.16.0)
class X {
  @&#8203;computed().volatile()
  prop
}

// Output (Prettier 1.16.1)
class X {
  @&#8203;(computed().volatile())
  prop
}

TypeScript: Stable parentheses for function type in the return type of arrow function (#5790 by @ikatyang)

There's a regression introduced in 1.16 that
parentheses for function type in the return type of arrow function were kept adding/removing.
Their parentheses are always printed now.

// Input
const foo = (): (() => void) => (): void => null;
const bar = (): () => void => (): void => null;

// First Output (Prettier 1.16.0)
const foo = (): () => void => (): void => null;
const bar = (): (() => void) => (): void => null;

// Second Output (Prettier 1.16.0)
const foo = (): (() => void) => (): void => null;
const bar = (): () => void => (): void => null;

// Output (Prettier 1.16.1)
const foo = (): (() => void) => (): void => null;
const bar = (): (() => void) => (): void => null;

MDX: Correctly recognize inline JSX (#5783 by @ikatyang)

Previously, some inline JSXs are wrongly recognized as block HTML/JSX,
which causes unexpected behaviors. This issue is now fixed.
```

_foo <InlineJSX /> bar_


_foo

<InlineJSX /> bar_


_foo <InlineJSX /> bar_
```

`v1.16.0`

mrdoob/three.js

palantir/tslint

`v6.1.2`

[bugfix] restore typings compatibility with TS < 3.8 (#4933)

`v6.1.1`

[bugfix] upgrade mkdirp dependency to ^0.5.3 (#4918)

prettier/tslint-config-prettier

`v1.18.0`

Features

rules: add tslint/type-literal-delimiter (17f0120)

prettier/tslint-plugin-prettier

`v2.3.0`

Features

support prettier@2 (#361) (be9ed18)

`v2.2.0`

Features

support tslint@6 (#355) (e979ae1)

`v2.1.0`

Features

respect .prettierignore (#317) (0420071)

2.0.1 (2018-10-28)

Bug Fixes

report syntax error instead of throw (#272) (8b62595)

Microsoft/TypeScript

`v3.9.3`

This release contains bug fixes in type-checking, APIs, emit, and editor scenarios.

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

npm

`v3.9.2`

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.8.3`

For release notes, check out the release announcement.

For new features, check out the What's new in TypeScript v3.8.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.8.2`

For release notes, check out the release announcement.

For new features, check out the What's new in TypeScript v3.8.2.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.7.5`

For the complete list of fixed issues, check out the

`v3.7.4`

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.7.3`

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.7.2`

For release notes, check out the release announcement.

For new features, check out the What's new in TypeScript v3.7.2.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.6.5`

This patch fixes an issue where TypeScript would erroneously report the following error under noImplicitAny when encountering a private get accessor in a .d.ts file.

Property 'myGetter' implicitly has type 'any', because its get accessor lacks a return type annotation.

This is an issue when using packages published from TypeScript 3.7 and newer. Users can upgrade to 3.6.5 to fix the issue.

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.6.4`

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.6.3`

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.6.2`

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.5.3`

This update fixes an issue with declaration emit when exported entities have function properties assigned to them.

Downloads are available on:

npm

`v3.5.2`

For new features, check out the What's new in TypeScript v3.5.2.

For the complete list of fixed issues, check out the

fixed issues query for Typescript v3.5.2.

Downloads are available on:

Changes:

7f47a08 Update LKG
fbe2f2f Update version to '3.5.2'
857873b Merge pull request #31877 from uniqueiniquity/port31685 [ #31685 ]
a2cd10b Merge pull request #31685 from uniqueiniquity/stopInvalidatingOnOpenFileSave
a1a2bd6 Merge pull request #31866 from amcasey/FunctionHintSpan35
caa66f6 Add regression test
fdacf7f Correct outline hint spans for functions
cf7b19a 🤖 Cherry-pick PR #31688 into release-3.5 (#31707)

This list of changes was auto generated.

`v3.5.1`

For release notes, check out the release announcement.

For new features, check out the What's new in TypeScript v3.5.1.

For breaking changes, check out the Breaking changes in TypeScript 3.5 page.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.4.5`

This release fixes an issue when running on node installations without npm.

For the complete list of fixed issues, check out the

Downloads are available on:

`v3.4.4`