jamak
jamak copied to clipboard
Update dependency prettier to v1.18.2
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
prettier (source) | devDependencies | minor | 1.15.3 -> 1.18.2 |
Release Notes
prettier/prettier
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
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(/** @​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, });
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, thebabylon
parser was renamed tobabel
. Unfortunately this lead to a minor breaking change:prettier.getSupportInfo('1.15.0')
would report that it supportedbabel
, notbabylon
, 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)<!-- Input --> Prix·:·32·€ <!-- Output (Prettier 1.16.1) --> Prix : 32 € <!-- Output (Prettier 1.16.2) --> 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 = /** @​type {{key: number}} */ (value); // Output (Prettier 1.16.1) const v = /** @​type {{key: number}} */ value; // Output (Prettier 1.16.2) const v = /** @​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 { @​(computed().volatile()) prop } // Output (Prettier 1.16.0) class X { @​computed().volatile() prop } // Output (Prettier 1.16.1) class X { @​(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.
<!-- Input --> _foo <InlineJSX /> bar_ <!-- Output (Prettier 1.16.0) --> _foo <InlineJSX /> bar_ <!-- Output (Prettier 1.16.1) --> _foo <InlineJSX /> bar_
v1.16.0
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!
".
:no_bell: 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 has been generated by Renovate Bot. View repository job log here.