Better defaults, a better CLI and better heuristics. Oh, and TypeScript 3.8.

After a long and careful consideration, we decided to change the default values for the trailingComma , arrowParens , and endOfLine options. We made the CLI more intuitive. And we've finally dropped support for Node versions older than 10, which had grown to become a huge maintenance hassle and an obstacle for contributors. Read below in details.

Highlights

JavaScript

Improved method chain breaking heuristic (#6685 by @mmkal)

Previously, any method call chain of length three or longer would be automatically broken into multiple lines. The new heuristic is based on the complexity of the call arguments in the chain, rather than simply on the chain's length. Now, if chained method calls have arguments which aren't easy to understand at a glance (e.g. functions or deeply-nested objects), the chain is broken. Otherwise, they're allowed to remain on one line. See prior issues #3197, #4765, #1565 and #4125 for context and examples.

To get best results, make sure your value for the printWidth option isn't too high.

if ( foo . one ( ) . two ( ) . three ( ) === bar . four ( ) . five ( ) . six ( ) ) { } if ( foo . one ( ) . two ( ) . three ( ) === bar . four ( ) . five ( ) . six ( ) ) { }

Ultimate fix for Closure-style type casts (#7791 by @thorn0, #7011 by @evilebottnawi)

Prettier has been trying not to corrupt these JSDoc type assertions since v1.6.0, with mixed results. As type checking based on JSDoc becomes increasingly common, we've been getting new bug reports about this syntax. The bugs were tricky because the required parentheses around the expression weren't part of the AST, so Prettier didn't have a good way to detect their presence.

Finally, we used the createParenthesizedExpressions option of the Babel parser to represent parentheses in the AST using non-standard nodes. This helped fix all the reported bugs.

Consequently, Prettier won't recognize JSDoc type casts if the flow or typescript parser is used, but this is reasonable as this syntax makes little sense in Flow and TypeScript files.

const nestedAssertions = ( ( x ) ) ; const nestedAssertions = x ; const nestedAssertions = ( ( x ) ) ;

Reference documentation for this syntax: Closure Compiler, TypeScript (with --checkJs ).

TypeScript

Prettier now supports the new syntax added in TypeScript 3.8:

CLI

Test whether passed globs are names of existing files before treating them as globs (#7587 by @fisker)

Since file names in Linux can contain almost any characters, strings like foo*.js and [bar].css are valid file names. Previously, if the user needed to format a file named [bar].css , a glob escaping syntax had to be used: prettier "\[bar].css" (this one doesn't work on Windows, where backslashes are treated as path separators) or prettier "[[]bar].css" . Because of this, important use cases were broken. E.g. lint-staged passes absolute paths and knows nothing about the escaping syntax. Now, when Prettier CLI gets a glob, it first tries to resolve it as a literal file name.

It's finally possible to run prettier --write . to format all supported files in the current directory and its subdirectories. Directory names can be mixed with file names and glob patterns (e.g. prettier src "test/*.spec.js" foo.js ).

Also, the order in which files are processed has changed. Previously, all the files were sorted alphabetically before formatting. Now, their order corresponds to the order of the specified paths. For each path, the list of resolved files is sorted, but the full sorting of the resulting combined list isn't done anymore.

There are also changes in how Prettier CLI reports errors if passed patterns don't match any files. Previously, Prettier CLI printed a "No matching files" error if it couldn't find any files at all—for all the patterns together, not for an individual pattern. In Prettier 2.0, the CLI also prints such errors for individual patterns.

Breaking changes

API

Fix config overrides pattern matching to include dot files (#5813 by @chrisblossom)

Previously, configuration overrides weren't applied to files whose name had a leading dot.

Drop support for Node versions older than 10 (#6908 by @fisker)

The minimal required Node version now is 10.13.0. For our contributors, this means there is no need anymore to jump through hoops to make tests pass on Node 4.

Change default value for trailingComma to es5 (#6963 by @fisker)

Before version 2.0, Prettier was avoiding trailing commas by default where possible. This made the resulting JavaScript compatible with now very old environments such as IE8, but implied some missed opportunities.

Prettier has included an option to configure trailing commas since its early days, and an initiative to change the default value has been out there for over three years. Finally, the default value becomes es5 instead of none in Prettier v2.0.

If the old behavior is still preferred, please configure Prettier with { "trailingComma": "none" } . There is a possibility that the default value will change to always (meaning even more trailing commas) in a future major version of Prettier as the JavaScript ecosystem further matures.

prettier.util.mapDoc has been removed.

Use prettier.doc.utils.mapDoc instead.

has been removed. Use instead. prettier.util.isNextLineEmpty has been updated.

Use isNextLineEmpty(text, node, locEnd) instead of isNextLineEmpty(text, node, options) .

has been updated. Use instead of . prettier.util.isPreviousLineEmpty has been updated.

Use isPreviousLineEmpty(text, node, locStart) instead of isPreviousLineEmpty(text, node, options) .

has been updated. Use instead of . prettier.util.getNextNonSpaceNonCommentCharacterIndex has been updated.

Use getNextNonSpaceNonCommentCharacterIndex(text, node, locEnd) instead of getNextNonSpaceNonCommentCharacterIndex(text, node, options) .

Change default value for arrowParens to always (#7430 by @kachkaev)

Since version 1.9, Prettier has had an option to always wrap arrow function arguments with parentheses. In version 2.0, this behavior has become the default.

const fn = ( x ) => y => x + y ; const fn = x => y => x + y ; const fn = ( x ) => ( y ) => x + y ;

At first glance, avoiding parentheses in the isolated example above may look like a better choice because it results in less visual noise. However, when Prettier removes parentheses, it becomes harder to add type annotations, extra arguments, default values, or a variety of other things. Consistent use of parentheses provides a better developer experience when editing real codebases, which justifies the change.

You are encouraged to use the new default value, but if the old behavior is still preferred, please configure Prettier with { "arrowParens": "avoid" } .

Change default value for endOfLine to lf (#7435 by @kachkaev)

Early versions of Prettier were formatting all files with the *nix flavor of line endings (

, also known as LF ). This behavior was changed in #472, which allowed preserving Windows line endings ( \r

, also known as CRLF ).

Since Prettier version 1.15, the flavor of line endings has been configurable via the endOfLine option. The default value was set to auto for backwards compatibility, which meant that Prettier preserved whichever flavor of line endings was already present in a given file.

That meant Prettier converted mixed line endings within one file to what was found at the end of the first line. However, line endings in separate files could still remain inconsistent. Besides, contributors on different operating systems could accidentally change line endings in previously committed files and this would be fine with Prettier. Doing so would produce a large git diff and thus make the line-by-line history for a file ( git blame ) harder to explore.

You are encouraged to use the new default value for endOfLine , which is now lf . It may be also worth checking the option docs to ensure your project repository is configured correctly. This will help you avoid a mix of line endings in the repo and a broken git blame . If the old behavior is still preferred, please configure Prettier with { "endOfLine": "auto" } .

If you use Travis CI, be aware of the autocrlf option in .travis.yml .

Cache plugin search results (#7485 by @fisker)

Previously, Prettier searched the file system for plugins on every prettier.format call. Now, search results are cached. The cache can be cleared by calling prettier.clearConfigCache() .

Options: useFlowParser ( --flow-parser in CLI) has been deprecated since v0.0.10 .

Option values: parser : babylon (renamed to babel in v1.16.0), postcss (renamed to css in v1.7.1), typescript-eslint (an old alias for typescript ) proseWrap : true (renamed to always in v1.9.0), false (renamed to never in v1.9.0) trailingComma : true (renamed to es5 in v0.19.0), false (renamed to none in v0.19.0)



Remove the version parameter of prettier.getSupportInfo (#7620 by @thorn0)

Since Prettier 1.8.0, it was possible to pass a version number to prettier.getSupportInfo to get information on the languages, options, etc. supported by previous versions. This interesting but apparently not very useful API kept causing maintenance problems and has been removed in Prettier 2.0.0.

Other changes

JavaScript

Always add a space after the function keyword (#3903 by @j-f1, @josephfrazier, @sosukesuzuki, @thorn0; #7516 by @bakkot)

Previously, a space would be added after the function keyword in function declarations, but not in function expressions. Now, for consistency, a space is always added after the function keyword. The only exception is generator declarations where function* is treated as a whole word.

const identity = function ( value ) { return value ; } ; function identity ( value ) { return value ; } const f = function < T > ( value : T ) { } ; const g = function * ( ) { } ; const identity = function ( value ) { return value ; } ; function identity ( value ) { return value ; } const f = function < T > ( value : T ) { } ; const g = function * ( ) { } ;

Fix unstable formatting of labeled statements with comments (#6984 by @clement26695)

loop1 : const i = 3 ; loop1 : const i = 3 ; loop1 : const i = 3 ; loop1 : const i = 3 ;

Fix formatting of logical, binary and sequence expressions in template literals (#7010 by @evilebottnawi)

` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ foo || bar } ` ; ` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ foo | bar } ` ; ` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ ( foo , bar ) } ` ; ` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ foo || bar } ` ; ` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ foo | bar } ` ; ` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ ( foo , bar ) } ` ; ` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ foo || bar } ` ; ` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ foo | bar } ` ; ` 111111111 222222222 333333333 444444444 555555555 666666666 777777777 ${ ( foo , bar ) } ` ;

Fix unstable formatting of logical expressions (#7026 by @thorn0)

const averredBathersBoxroomBuggyNurl = bifornCringerMoshedPerplexSawder === 1 || ( askTrovenaBeenaDependsRowans === 2 || glimseGlyphsHazardNoopsTieTie === 3 ) ; const averredBathersBoxroomBuggyNurl = bifornCringerMoshedPerplexSawder === 1 || askTrovenaBeenaDependsRowans === 2 || glimseGlyphsHazardNoopsTieTie === 3 ; const averredBathersBoxroomBuggyNurl = bifornCringerMoshedPerplexSawder === 1 || askTrovenaBeenaDependsRowans === 2 || glimseGlyphsHazardNoopsTieTie === 3 ; const averredBathersBoxroomBuggyNurl = bifornCringerMoshedPerplexSawder === 1 || askTrovenaBeenaDependsRowans === 2 || glimseGlyphsHazardNoopsTieTie === 3 ;

Format throw like return (#7070 by @sosukesuzuki)

function foo ( ) { throw this . hasPlugin ( "dynamicImports" ) && this . lookahead ( ) . type === tt . parenLeft . right ; } function foo ( ) { throw this . hasPlugin ( "dynamicImports" ) && this . lookahead ( ) . type === tt . parenLeft . right ; } function foo ( ) { throw ( this . hasPlugin ( "dynamicImports" ) && this . lookahead ( ) . type === tt . parenLeft . right ) ; }

Fix indentation in ternaries nested in conditions of other ternaries (#7087 by @thorn0)

const foo = ( number % 10 >= 2 && ( number % 100 < 10 || number % 100 >= 20 ) ? kochabCooieGameOnOboleUnweave : annularCooeedSplicesWalksWayWay ) ? anodyneCondosMalateOverateRetinol : averredBathersBoxroomBuggyNurl ; const foo = ( number % 10 >= 2 && ( number % 100 < 10 || number % 100 >= 20 ) ? kochabCooieGameOnOboleUnweave : annularCooeedSplicesWalksWayWay ) ? anodyneCondosMalateOverateRetinol : averredBathersBoxroomBuggyNurl ; const foo = ( number % 10 >= 2 && ( number % 100 < 10 || number % 100 >= 20 ) ? kochabCooieGameOnOboleUnweave : annularCooeedSplicesWalksWayWay ) ? anodyneCondosMalateOverateRetinol : averredBathersBoxroomBuggyNurl ;

Tweak function composition logic for decorators (#7138 by @brainkim)

Because decorators modify the line following, splitting a decorator call’s arguments onto multiple lines can obscure the relationship between the decorator and its intended target, producing less-readable code. Therefore, the function composition logic introduced in #6033 has been changed to exclude decorator calls.

export class Item { @ OneToOne ( ( ) => Thing , x => x . item ) thing ! : Thing ; } export class Item { @ OneToOne ( ( ) => Thing , x => x . item , ) thing ! : Thing ; } export class Item { @ OneToOne ( ( ) => Thing , x => x . item ) thing ! : Thing ; }

Correct semicolon placement in empty return statement with comment (#7140 by @sosukesuzuki)

return ; return return ;

Respect whitespace significance in HTML template literals (#7208 by @saschanaz)

Prettier had been adding newlines for every HTML template string, which could lead to unexpected whitespace in rendered HTML. This doesn't happen anymore unless --html-whitespace-sensitivity ignore option is given.

html ` <div> ` ; html ` <span>TEXT</span> ` ; html ` <div></div> ` ; html ` <span>TEXT</span> ` ; html ` <div></div> ` ; html ` <span>TEXT</span> ` ;

Remove unnecessary parens when yielding JSX (#7367 by @cola119)

function * f ( ) { yield < div > generator </ div > ; } function * f ( ) { yield ( < div > generator </ div > ) ; } function * f ( ) { yield < div > generator </ div > ; }

Keep parentheses around comma expressions in default export declarations (#7491 by @fisker)

Omitting these parentheses makes the code invalid.

export default ( 1 , 2 ) ; export default 1 , 2 ; export default ( 1 , 2 ) ;

Fix edge cases with parentheses around optional chaining (#7500 by @thorn0)

( foo ?. bar ) ( ) ; new ( foo ?. bar ) ( ) ; foo ?. bar ( ) ; new foo ?. bar ( ) ; ( foo ?. bar ) ( ) ; new ( foo ?. bar ) ( ) ;

Don't wrap undefined in parentheses in conditional expressions within JSX (#7504 by @fisker)

Previously, parentheses were added around any expression except null . Now, undefined is excluded too.

foo ? < span > loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong jsx </ span > : undefined foo ? < span > loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong jsx </ span > : null foo ? ( < span > loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong jsx </ span > ) : ( undefined ) ; foo ? ( < span > loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong jsx </ span > ) : null ; foo ? ( < span > loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong jsx </ span > ) : undefined ; foo ? ( < span > loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong jsx </ span > ) : null ;

Keep comments position for assignments/variables (#7709 by @sosukesuzuki)

const foo = bar ; const foo = bar ; const foo = bar ;

TypeScript

Babel as an alternative parser for TypeScript (#6400 by @JounQin & @thorn0)

A new value for the parser option has been added: babel-ts , which makes use of Babel’s TypeScript plugin. The babel-ts parser supports JavaScript features not yet supported by TypeScript (ECMAScript proposals, e.g. private methods and accessors), but it's less permissive when it comes to error recovery and less battle-tested than the typescript parser. While Babel’s TypeScript plugin is quite mature, ASTs produced by the two parsers aren't 100% compatible. We tried to take the discrepancies into account, but there are most likely still cases where code gets formatted differently or even incorrectly. We call upon you, our users, to help us find such cases. If you see them, please raise issues. In the long run, this will help with unifying the AST format in future versions of the parsers and thus contribute to a better, more solid JavaScript parser ecosystem.

Fix formatting of complex types in arrow function return type annotations (#6901 by @sosukesuzuki)

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

Print JSDoc-only types as is instead of throwing errors (#7020 by @thorn0)

Another fix related to error recovery. Should come in handy to those who migrate from Flow to TypeScript.

function fromFlow ( arg : ? Maybe ) { } Error : unknown type : "TSJSDocNullableType" function fromFlow ( arg : ? Maybe ) { }

Don't print trailing commas after rest elements in tuples (#7075 by @thorn0)

A rest element is always the last element of a tuple type. Nothing can be added after it.

While TS is okay with this comma, Babel doesn't parse it

In function parameters and array destructuring, such a comma is a syntax error. Keeping it in tuples is inconsistent.

type ValidateArgs = [ { [ key : string ] : any ; } , string , ... string [ ] , ] ; type ValidateArgs = [ { [ key : string ] : any ; } , string , ... string [ ] , ] ; type ValidateArgs = [ { [ key : string ] : any ; } , string , ... string [ ] ] ;

Fix indentation of arrow functions in variable declarations followed by comments (#7094 by @sosukesuzuki)

This could happen with code written in the no-semicolon style if the statement after the variable declaration was prefixed with a semicolon to avoid ASI issues.

const foo = ( ) => { return } ; [ 1 , 2 , 3 ] . forEach ( bar ) const foo = ( ) => { return ; } ; [ 1 , 2 , 3 ] . forEach ( bar ) ; const foo = ( ) => { return ; } ; [ 1 , 2 , 3 ] . forEach ( bar ) ;

Fix printing of comments in function types (#7104 by @thorn0)

type f1 = ( currentRequest : { a : number } , ) => number ; type f1 = ( currentRequest : { a : number ; } ) => number ; type f1 = ( currentRequest : { a : number } ) => number ;

Fix formatting of comments for function-like nodes (#7144 by @armano2)

interface foo1 { bar1 ( ) bar2 ? ( ) ; bar3 ( ) bar4 ? ( bar : string ) : string ; ( ) : string ; ( bar : string ) : string ; new ( a : string ) : string new ( ) : string } type foo7 = ( ) => void type foo8 = ( a : string ) => void let foo9 : new ( ) => string ; let foo10 : new ( a : string ) => string ; interface foo1 { bar1 ( ) ; bar2 ? ( ) ; bar3 ( ) ; bar4 ? ( bar : string ) : string ; ( ) : string ; ( bar : string ) : string ; new ( a : string ) : string ; new ( ) : string ; } type foo7 = ( ) => void ; type foo8 = ( a : string ) => void ; let foo9 : new ( ) => string ; let foo10 : new ( a : string ) => string ; interface foo1 { bar1 ( ) ; bar2 ? ( ) ; bar3 ( ) ; bar4 ? ( bar : string ) : string ; ( ) : string ; ( bar : string ) : string ; new ( a : string ) : string ; new ( ) : string ; } type foo7 = ( ) => void ; type foo8 = ( a : string ) => void ; let foo9 : new ( ) => string ; let foo10 : new ( a : string ) => string ;

abstract class Test { abstract foo12 ( a : string ) : void abstract foo13 ( ) } Error : Comment "foo" was not printed . Please report this error ! abstract class Test { abstract foo12 ( a : string ) : void ; abstract foo13 ( ) ; }

Fix printing of mapped types with the template type omitted (#7221 by @cola119)

type A = { [ key in B ] } ; type A = { [ key in B ] : } ; type A = { [ key in B ] } ;

Fix edge cases of printing index signatures (#7228 by @cola119)

Even though index signatures without type annotations or with multiple parameters aren't valid TypeScript, the TypeScript parser supports this syntax. In line with the previous error recovery efforts, Prettier now makes sure its output still can be parsed in these cases. Previous versions produced unparseable code.

type A = { [ key : string ] } ; type B = { [ a : string , b : string ] : string ; } ; type A = { [ key : string ] : } ; type B = { [ a : stringb : string ] : string } ; type A = { [ key : string ] } ; type B = { [ a : string , b : string ] : string } ;

Fix printing of comments in empty type parameters (#7729 by @sosukesuzuki)

const a : T < > = 1 ; Error : Comment "comment" was not printed . Please report this error ! const a : T < > = 1 ;

Flow

Add support for symbol (#7472 by @fisker)

A new AST node type was introduced in flow@0.114.0, now it's recognized.

const x : symbol = Symbol ( ) ; Error : unknown type : "SymbolTypeAnnotation" const x : symbol = Symbol ( ) ;

Add support for decorators (#7482 by @fisker)

@decorator4 class Foo { @decorator1 method1 ( ) { } @decorator2 @decorator3 method2 ( ) { } } SyntaxError : Unexpected token ` @ ` , expected the token ` class ` ( 2 : 1 ) @decorator4 class Foo { @decorator1 method1 ( ) { } @decorator2 @decorator3 method2 ( ) { } }

Fix private class field declarations (#7484 by @fisker)

class Foo { #privateProp : number ; } class Foo { privateProp : number ; } class Foo { #privateProp : number ; }

CSS

Don't lowercase element names in CSS selectors (#6947 by @ark120202)

Previously, Prettier already preserved casing of unknown element names, but it did lowercase names of HTML elements. This caused issues when CSS was applied to a case-sensitive document and there was an element with the same name as in HTML, which is the case in NativeScript. Prettier now always preserves original casing.

Label { } label { } Label { }

SCSS

Don't add extra comma after last comment in map (#6918 by @fisker)

Previously, when trailingComma set to es5 , an extra comma was added after last comment in an SCSS map.

$my-map : ( 'foo' : 1 , // Comment 'bar' : 2 , // Comment ); $my-map : ( "foo" : 1 , // Comment "bar" : 2 , // Comment, ); $my-map : ( "foo" : 1 , // Comment "bar" : 2 , // Comment );

Fix whitespace in SCSS concatenation (#7211 by @sasurau4)

a { background-image : url( $test-path + 'static/test.jpg' ); } a { background-image : url( $test-path + "static/test.jpg" ); } a { background-image : url( $test-path + "static/test.jpg" ); }

Less

each is supported now (#5653).

is supported now (#5653). !important was being moved out of mixin call parameters (#3544).

was being moved out of mixin call parameters (#3544). Comments in rulesets passed to mixin calls caused duplicate semicolons (#3096).

::before was broken in mixin call parameters (#5791).

HTML

Comments in pre tags caused bad formatting of following closing tag (#5959 by @selvazhagan)

< details > < pre > </ pre > </ details > < details > < pre > </ pre > </details </ details > < details > < pre > </ pre > </ details >

Don't treat colons as namespace prefix delimiters in tag names (#7273 by @fisker)

In HTML5, colons don't have any special meaning in tag names. Previously, Prettier treated them the XML way, as namespace prefix delimiters, but no more. In practice, this means that tags whose ancestors have colons in their names are now treated as usual HTML tags: if they're known standard tags, their names can be lowercased and assumptions can be made about their whitespace sensitivity; custom elements whose names are unknown to Prettier retain the casing of their names and, if --html-whitespace-sensitivity is set to css , are treated as inline.

< with: colon > < div > looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog block </ div > < DIV > block </ DIV > < DIV > block </ DIV > < DIV > block </ DIV > < div > block </ div > < div > block </ div > < pre > pre pr e </ pre > < textarea > pre-wrap pr e-wrap </ textarea > < span > looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog inline </ span > < span > inline </ span > < span > inline </ span > < span > inline </ span > < span > inline </ span > </ with: colon > < with: colon > < div > looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog block </ div > < DIV > block </ DIV > < DIV > block </ DIV > < DIV > block </ DIV > < div > block </ div > < div > block </ div > < pre > pre pr e </ pre > < textarea > pre-wrap pr e-wrap </ textarea > < span > looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog inline </ span > < span > inline </ span > < span > inline </ span > < span > inline </ span > < span > inline </ span > </ with: colon > < with: colon > < div > looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog block </ div > < div > block </ div > < div > block </ div > < div > block </ div > < div > block </ div > < div > block </ div > < pre > pre pr e </ pre > < textarea > pre-wrap pr e-wrap </ textarea > < span > looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog inline </ span > < span > inline </ span > < span > inline </ span > < span > inline </ span > < span > inline </ span > </ with: colon >

Do not throw on broken HTML (#7293 by @fisker)

< div > < span > < TypeError: Cannot read property 'start' of null < div > < span > < </ span > </ div >

Fix srcset parse error (#7295 by @fisker)

< img srcset = " /media/examples/surfer-240-200.jpg " > Error: Mixed descriptor in srcset is not supported < img srcset = " /media/examples/surfer-240-200.jpg " />

Fix error thrown on unclosed tag in pre tag (#7392 by @fisker)

< pre > < br > </ pre > < pre > < hr > </ pre > TypeError: Cannot read property 'start' of null < pre > < br /> </ pre > < pre > < hr /> </ pre >

Fix inconsistent formatting of self-closing tags (#7395 by @fisker)

< span > < input type = " checkbox " /> </ span > < span > < span > < input type = " checkbox " /> </ span > </ span > < span > < input type = " checkbox " /> </ span > < span > < input type = " checkbox " /> </ span > < span > < span > < input type = " checkbox " /> </ span > </ span > < span > < input type = " checkbox " /> </ span > < span > < input type = " checkbox " /> </ span > < span > < span > < input type = " checkbox " /> </ span > </ span > < span > < input type = " checkbox " /> </ span >

Fix empty lines unexpectedly added after table tags (#7461 by @ikatyang)

< table > < tr > </ tr > </ table > < div > Should not insert empty line before this div </ div > < table > < tr > </ tr > </ table > < div > Should not insert empty line before this div </ div > < table > < tr > </ tr > </ table > < div > Should not insert empty line before this div </ div >

Format value of HTML class attribute (#7555 by @fisker)

< div class = " foo bar baz " > </ div > < div class = " another element with so many classes even can not fit one line really a lot and lot of classes " > </ div > < div class = " foo bar baz " > </ div > < div class = " another element with so many classes even can not fit one line really a lot and lot of classes " > </ div > < div class = " foo bar baz " > </ div > < div class = " another element with so many classes even can not fit one line really a lot and lot of classes " > </ div >

Format value of HTML style attribute (#7556 by @fisker)

< div style =" color : red ; display : inline " > </ div > < div style =" color : red ; display : inline ; height : auto ; position : absolute ; top : 0 ; left : 0 ; right : 0 ; bottom : 0 ; " > </ div > < div style =" color : red ; display : inline " > </ div > < div style =" color : red ; display : inline ; height : auto ; position : absolute ; top : 0 ; left : 0 ; right : 0 ; bottom : 0 ; " > </ div > < div style =" color : red ; display : inline ; " > </ div > < div style =" color : red ; display : inline ; height : auto ; position : absolute ; top : 0 ; left : 0 ; right : 0 ; bottom : 0 ; " > </ div >

Support <!-- prettier ignore --> for text (#7654 by @graemeworthy)

Previously, it worked only for tags. Useful for protecting various macros and pre-processor commands from being corrupted by formatting.

A super long string that has been marked as ignore because it was probably generated by some script. A super long string that has been marked as ignore because it was probably generated by some script. A super long string that has been marked as ignore because it was probably generated by some script.

| Dogs | Cats | Weasels | Bats | Pigs | Mice | Hedgehogs | Capybaras | Rats | Tigers | | ---- | ---- | ------- | ---- | ---- | ---- | --------- | --------- | ---- | ------ | | 1 | 1 | 0 | 0 | 1 | 1 | 5 | 16 | 4 | 0 | | Dogs | Cats | Weasels | Bats | Pigs | Mice | Hedgehogs | Capybaras | Rats | Tigers | | ---- | ---- | ------- | ---- | ---- | ---- | --------- | --------- | ---- | ------ | | 1 | 1 | 0 | 0 | 1 | 1 | 5 | 16 | 4 | 0 | | Dogs | Cats | Weasels | Bats | Pigs | Mice | Hedgehogs | Capybaras | Rats | Tigers | | ---- | ---- | ------- | ---- | ---- | ---- | --------- | --------- | ---- | ------ | | 1 | 1 | 0 | 0 | 1 | 1 | 5 | 16 | 4 | 0 |

Vue

Format vue SFC containing JSX script (#7180 by @sosukesuzuki)

< script lang = " jsx " > export default { data : ( ) => ( { message : 'hello with jsx' } ) , render ( h ) { return < div > { this . message } < / div > } } </ script > < script lang = " jsx " > export default { data : ( ) => ( { message : 'hello with jsx' } ) , render ( h ) { return < div > { this . message } < / div > } } </ script > < script lang = " jsx " > export default { data : ( ) => ( { message : "hello with jsx" } ) , render ( h ) { return < div > { this . message } < / div > ; } } ; </ script >

Don't print sole string literals in attributes on a new line (#7479 by @fisker)

< template > < MyComponent :attr1 = "`loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong $ {template} literal value`" :attr2 = "'loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong string literal value'" /> </ template > < template > < MyComponent :attr1 = " `loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong $ {template} literal value` " :attr2 = " 'loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong string literal value' " /> </ template > < template > < MyComponent :attr1 = "`loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong $ {template} literal value`" :attr2 = "'loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong string literal value'" /> </ template >

Fix indentation of Vue expressions (#7781 by @fisker)

< template > < MyComponent v-if = " long_long_long_long_long_long_long_condition_1 && long_long_long_long_long_long_long_condition_2 && long_long_long_long_long_long_long_condition_3 && long_long_long_long_long_long_long_condition_4 " :attr = " `loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog string 1` + `loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog string 2` " /> </ template > < template > < MyComponent v-if = " long_long_long_long_long_long_long_condition_1 && long_long_long_long_long_long_long_condition_2 && long_long_long_long_long_long_long_condition_3 && long_long_long_long_long_long_long_condition_4 " :attr = " `loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog string 1` + `loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog string 2` " /> </ template > < template > < MyComponent v-if = " long_long_long_long_long_long_long_condition_1 && long_long_long_long_long_long_long_condition_2 && long_long_long_long_long_long_long_condition_3 && long_long_long_long_long_long_long_condition_4 " :attr = " `loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog string 1` + `loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooog string 2` " /> </ template >

Angular

Unofficial rudimentary support for some of the most used directives of AngularJS 1.x (#6869 by @thorn0)

While there are some syntax incompatibilities (one-time bindings and the precedence of | ) between the expression languages of the old AngularJS and the new Angular, overall the two languages are compatible enough for legacy and hybrid AngularJS-based projects to be able to benefit from using Prettier. Previously, when Prettier formatted AngularJS templates using the Angular parser, it formatted expressions only in interpolations. Now, some of the most used AngularJS directives are formatted too, namely: ng-if , ng-show , ng-hide , ng-class , ng-style .

< div ng-if = " $ctrl .shouldShowWarning&&!$ctrl.loading " > Warning! </ div > < div ng-if = " $ctrl .shouldShowWarning&&!$ctrl.loading " > Warning! </ div > < div ng-if = " $ctrl.shouldShowWarning && !$ctrl.loading " > Warning! </ div >

Fix formatting of i18n attributes (#7371 by @thorn0)

Prettier 1.19 added support for formatting i18n attributes, but putting the closing quote mark on a new line broke custom ids. This is fixed now.

< div i18n-prop = " Special-property|This is a special property with much important information@@MyTextId " prop = " My Text " > </ div > < div i18n-prop = " Special-property|This is a special property with much important information@@MyTextId " prop = " My Text " > </ div > < div i18n-prop = " Special-property|This is a special property with much important information@@MyTextId " prop = " My Text " > </ div >

Handlebars (alpha)

Fix superfluous line breaks in ConcatStatement (#7051 by @dcyriller)

< a href = "a-very-long-href-from-a-third-party-marketing-platform {{id}} longer-than-eighty-chars" > Link </ a > < a href = "a-very-long-href-from-a-third-party-marketing-platform {{id}} longer-than-eighty-chars" > Link </ a > < a href = "a-very-long-href-from-a-third-party-marketing-platform {{id}} longer-than-eighty-chars" > Link </ a >

and

< div class = "hello {{ if goodbye true}} {{ if goodbye false}} {{ if goodbye true}} {{ if goodbye false}} {{ if goodbye true}} " > Hello </ div > < div class = "hello {{ if goodbye true}} {{ if goodbye false}} {{ if goodbye true}} {{ if goodbye false}} {{ if goodbye true}} " > Hello </ div > < div class = "hello {{ if goodbye true}} {{ if goodbye false}} {{ if goodbye true}} {{ if goodbye false }} {{ if goodbye true}} " > Hello </ div >

Fix a falling mustache issue (#7052 by @dcyriller)

< GlimmerComponent @ progress = {{aPropertyEndingAfterEightiethColumnToHighlightAWeirdClosingParenIssue}} /> < GlimmerComponent @ progress = {{aPropertyEndingAfterEightiethColumnToHighlightAWeirdClosingParenIssue }} /> < GlimmerComponent @ progress = {{aPropertyEndingAfterEightiethColumnToHighlightAWeirdClosingParenIssue}} />

< p > Hi here is your name, as it will be displayed {{firstName}} {{lastName}} , welcome! </ p > < p > Hi here is your name, as it will be displayed {{firstName}} {{lastName }} , welcome! </ p > < p > Hi here is your name, as it will be displayed {{firstName}} {{ lastName }} , welcome! </ p >

< div > "hello! my parent was ignored" {{# my -crazy-component "shall" be="preserved"}} < This is = "preserved" /> {{/ my -crazy-component}} </ div > {{# a -normal-component isRestoredTo = "order" }} < ThisWillBeNormal backTo = "normal" /> {{/ a -normal-component}} < div > "hello! my parent was ignored" {{# my -crazy-component "shall" be="preserved"}} < This is = "preserved" /> {{/ my -crazy-component}} </ div > {{# a -normal-component isRestoredTo="order"}} < ThisWillBeNormal backTo = "normal" /> {{/ a -normal-component}} < div > "hello! my parent was ignored" {{# my -crazy-component "shall" be="preserved"}} < This is = "preserved" /> {{/ my -crazy-component}} </ div > {{# a -normal-component isRestoredTo='order'}} < ThisWillBeNormal backTo = 'normal' /> {{/ a -normal-component}}

Support printing inline Handlebars in HTML (#7306 by @dcyriller)

< script type = "text/x-handlebars-template" > {{component arg1= 'hey' arg2=(helper this .arg7 this .arg4) arg3=anotherone arg6= this .arg8}} </ script > < script type = "text/x-handlebars-template" > {{component arg1= 'hey' arg2=(helper this .arg7 this .arg4) arg3=anotherone arg6= this .arg8}} </ script > < script type = "text/x-handlebars-template" > {{component arg1= 'hey' arg2=(helper this .arg7 this .arg4) arg3=anotherone arg6= this .arg8 }} </ script >

Fix stripped value from AttrNode (#7552 by @bantic)

< ul class = "abc def" > </ ul > < ul class > </ ul > < ul class = "abc def" > </ ul >

Preserve whitespace control characters (#7575 by @mahirshah)

{{~# if bar}} if1 {{~ else ~}} else {{~/ if ~}} {{# if bar}} if1 {{ else }} else {{/ if }} {{~# if bar}} if1 {{~ else ~}} else {{~/ if ~}}

GraphQL

Improve detection of separator between interfaces (#7305 by @fisker)

Even though using a comma to separate multiple implemented interfaces is deprecated syntax, in order to support legacy use cases, Prettier keeps the original separator and doesn't wilfully replace commas with ampersands. Previously, however, this logic contained a bug, so the wrong separator could end up in the output. This is fixed now.

type Type1 implements A, B {a: a} type Type2 implements A, B & C{a: a} type Type1 implements A & B { # { & <-- Removing this comment changes the separator in 1.19 a: a } type Type2 implements A & B & C { a: a } type Type1 implements A, B { # { & <-- Removing this comment changes the separator in 1.19 a: a } type Type2 implements A, B & C { a: a }

Markdown

0. List 1. List 2. List 0. List 1. List 1. List 0. List 1. List 2. List

Fix HTML formatting broken if the beginning tag starts after a list item (#7181 and #7220 by @sasurau4)

Previously, when Prettier formatted an HTML tag placed just after a list item, it would insert indent and break the relationship of open and close tag. Now, Prettier no longer changes anything.

- A list item. < details > < summary > Summary </ summary > < p > - A list item. </ p > </ details > - A list item < blockquote > asdf </ blockquote > - A list item. < details > < summary > Summary </ summary > < p > - A list item. </ p > </ details > - A list item < blockquote > asdf </ blockquote > - A list item. < details > < summary > Summary </ summary > < p > - A list item. </ p > </ details > - A list item < blockquote > asdf </ blockquote >

Fix formatting of multi-line footnote (#7203 by @sasurau4)

Here's a statement[^footnote]. [ ^footnote ]: Here's a multi-line footnote walking back the above statement, and showing how it's all totally bollocks. Here's a statement[^footnote]. [ ^footnote ]: Here's a multi-line footnote walking back the above statement, and showing how it's all totally bollocks. Here's a statement[^footnote]. [ ^footnote ]: Here's a multi-line footnote walking back the above statement, and showing how it's all totally bollocks.

MDX

Add support for JSX fragments (#6398 by @JounQin)

<> test <World /> test </> 123 <> test < World /> test </> 123 <> test < World /> test </> 123

Fix JSX parsing bugs introduced in Prettier 1.19 (#6949 by @Tigge & @thorn0)

MDX parsing for JSX failed when encountering JSX elements that where not parsable as HTML, such as <Tag value={{a: 'b'}}>test</Tag>

< Tag value = { { a : ' b ' } }> test </ Tag > < Foo bg = { ' red ' } > < div style = {{ display: ' block '} }> <Bar >hi </Bar> { hello } { /* another comment */} </div> </ Foo > SyntaxError: Unexpected closing tag "Tag". It may happen when the tag has already been closed by another tag. For more info see https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags (1:35) > 1 | <Tag value={ {a : 'b' } }>test</ Tag> < Tag value = {{ a: " b " }}> test </ Tag > < Foo bg = { " red "}> < div style = {{ display: " block " }}> <Bar>hi </Bar> {hello} {/* another comment */} </ div > </ Foo >

CLI

Support file extensions .cjs and .yaml.sed (#7210 by @sosukesuzuki)

$ prettier test.cjs test.cjs[error] No parser could be inferred for file: test.cjs $ prettier test.cjs "use strict" ; console.log( "Hello, World!" );

Respect --ignore-path when prettier executes from a subdirectory (#7588 by @heylookltsme)

Changes the filename used when filtering ignored files to be relative to the --ignore-path , if present, rather than the current working directory.

This CLI flag, never properly documented, was supposed to make Prettier CLI read input from stdin, but Prettier CLI does so anyway when not given any file paths or glob patterns. So the flag was redundant. Now that it's been removed, if you use this flag in your commands, you'll see a warning: "Ignored unknown option". This warning is just information. It doesn't prevent the command from doing what it should do and doesn't affect the exit code.