• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/prettier-1.15.0 at 100.0% (Details).

🔗 Release Notes

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

The new version differs by 4 commits.

• e1e7d57 6.2.0
• 1eacd53 add support for preload configuration via env vars (#355)
• 1f84ba1 add TypeScript types (#345)
• 194c98e Fix appveyor repo badge url in readme (#347)

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/request-promise-native-1.0.6 at 100.0% (Details).

The new version differs by 10 commits.

• 7ad655a Version 1.0.6 (now really)
• 1240b80 fix: updated indirect lodash dependency to fix security vulnerability
• 80947a1 Version 1.0.6
• ad529a3 chore: fix ci build for node v8+
• c2c54c4 Merge pull request #33 from jasonmit/u/jasonmit/fix-node-6
• 67f7ed2 Merge branch 'master' into u/jasonmit/fix-node-6
• 4633d4c fix: breaking change in tough-cookie v3
• 14aa6ee chore: added node 8 and 10 to ci build
• 9cfcaaa Update package.json
• 049152b fix: target tough-cookie 2.x to preserve node 6 support

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/coveralls-3.0.3 at 100.0% (Details).

As suggested by NPM and Snyk.

The new version differs by 1 commits.

• aa2519c dependency security audit fixes from npm & snyk (#210)

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

There is a collection of frequently asked questions and of course you may always ask my humans.

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/webpack-4.41.5 at 100.0% (Details).

Bugfixes

• handle relative paths with webpack:// prefix in SourceMaps correctly
• fixes a non-determinism about providedExports with export * which caused changing module hashes and unnecessary HMR invalidation

The new version differs by 7 commits.

• 45ecebc 4.41.5
• 8a0dac1 Merge pull request #10185 from webpack/bugfix/non-deterministic-provided-exports
• 4e31587 Merge pull request #10183 from webpack/deps/update
• 3ec952f update dependencies in-range
• 8e4749e make order of exports in providedExports deterministic
• 0e5e8d9 Merge pull request #10181 from webpack/backport/webpack-source-map-prefix
• 6b9884e handle webpack:// prefix in SourceMap sources

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
• ✅ coverage/coveralls First build on greenkeeper/jest-21.1.0 at 100.0% Details

There is a collection of frequently asked questions and of course you may always ask my humans.

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

This release features some bugfixes and tweaks around JSX, TypeScript, CSS, and JavaScript formatting, as well as a couple new features.

Highlights

JSX Changes

We received a lot of community feedback about the changes we made to JSX formatting in the 1.6.0 release, and have made changes to bring formatting closer to community standards and expectations.

In 1.6.0, we added a second style for ternaries (conditional expressions, a ? b : c), based on a format popular in the community where parentheses are used to demarcate JSX content:

const DinnerOptions = ({ willEatMeat, willEatEggs, willEatVegetables }) => (
  <div>
    <div>Let's get some dinner...</div>
    {willEatMeat ? (
      <FullMenu />
    ) : willEatEggs ? (
      <VegetarianMenu />
    ) : willEatVegetables ? (
      <VeganMenu />
    ) : (
      <BackupMenu />
    )}
  </div>
);

Before this was added, prettier only formatted ternaries with one consistent style:

willEatMeat
  ? "Full Menu"
  : willEatEggs
    ? "Vegetarian Menu"
    : willEatVegetables ? "Vegan Menu" : "Backup Menu";

In 1.6.0, we used the following heuristic to decide when to use the new "JSX mode ternaries":

We should print a ternary using JSX mode if:
  * The ternary contains some JSX in it
  OR
  * The ternary appears inside of some JSX

However, this heuristic caused some unexpected formatting:

So, in 1.7.0, we have revised our heuristic to just be:

We should print a ternary using JSX mode if:
  * The ternary contains some JSX in it

We hope that this change will result in fewer surprising ternaries.

A big thanks goes out to @duailibe who implemented this change in addition to several other JSX-related formatting issues that were reported.

CSS Letter Case Consistency

We spent some time this release polishing our CSS formatting, and as part of that, @lydell did some work to normalize letter case.

So now, almost everything in CSS will print using lower case.

/* Before */
DIV.Foo {
  HEIGHT: 12PX;
}
/ After /

div.Foo {

height: 12px;

}

Don't worry, though – Prettier won't touch your $scss-variables, @less-variables, or FunctionNames(). Preprocess on!

Pragma Support

There is a new option called --require-pragma (requirePragma via the API) which will change prettier's behavior so that it only reformats a file if it has a special "pragma" comment at the top of it, that looks like this:

/**
 * @prettier
 */

or

/**
 * @format
 */

This was @ajhyndman's idea and it was implemented by @wbinnssmith.

Other Changes

TypeScript

There was a bug in Prettier 1.6.1 where an error would be thrown while parsing any TypeScript using the never type, for example:

Observable.empty<never>();

Also, Prettier 1.6.1 was incorrectly removing the declare keyword from enum declarations in *.d.ts files:

// In
declare const enum Foo {}
// Out

const enum Foo {}

Both of these issues have been fixed. Thanks to @JamesHenry and @existentialism for these fixes which support our TypeScript community!

Configuration

Configurable Config Precedence

There is a new CLI option --config-precedence which configures how prettier should prioritize config sources. Valid values are:

cli-override (default) - CLI options take precedence over config file

file-override - Config file take precedence over CLI options

prefer-file - If a config file is found will evaluate it and ignore other CLI options. If no config file is found CLI options will evaluate as normal.

This option adds support to editor integrations where users define their default configuration but want to respect project specific configuration.

prettier.resolveConfig.sync

Previously, there was no way via the API to resolve configuration for a source file synchronously. Thanks to some new additions to cosmiconfig by @sudo-suhas, @ikatyang was able to add support for this to the prettier API.

PRs merged in this release

• Update README.md by @ikatyang
• Fix config file finding when using stdin by @lydell
• docs(readme): add and sort cli options by @levithomason
• Add Transloadit as a user by @kvz
• Ensure parens around LogicalExpression inside ExperimentalSpreadProperty by @existentialism
• Fix printing declare modifier for TS enum by @existentialism
• Handle +/- before numbers in CSS by @xtian
• Add Tradeshift as a user by @sampi
• feat(resolve-config): add .sync() method by @ikatyang
• refactor(bin): use resolveConfigFile.sync() by @ikatyang
• refactor(cli): separate files and make it pure as possible by @ikatyang
• Fix cosmiconfig dependency branch by @josephfrazier
• Upgrade chalk to v2.1.0 by @josephfrazier
• Add CLI option '--config-precedence' by @mitermayer
• Normalize CSS case by @lydell
• Make run-external-typescript-tests.js cross-platform by @lydell
• test(integration): add more tests by @ikatyang
• chore(deps): remove devDependency cross-spawn by @ikatyang
• Ignore some things in coverage by @lydell
• Generalize run-external-typescript-tests.js by @lydell
• Improve lint-staged setup example by adding more filetypes by @MoOx
• fixes dynamic imports by @rkurbatov
• Refactor error handling by @azz
• chore(github): add issue template by @ikatyang
• Fix: TypeScript never keyword (fixes #2718) by @JamesHenry
• Group last argument if it's an empty object with a comment by @duailibe
• Use files: over types: in pre-commit configuration by @asottile
• refactor(runPrettier): reduce duplicate code by @ikatyang
• Change when to print ternaries in JSX mode by @duailibe
• Fix chained logical expressions with objects/array/etc inlined by @duailibe
• Add option to require @prettier or @format pragma by @wbinnssmith
• chore(build): update ISSUE_TEMPLATE.md before publish by @ikatyang
• Fix break on conditional expressions inside return by @duailibe
• Support graphql(schema, query) by @azz
• fix(prettierignore): support absolute filename by @ambar
• Keep conditional expressions in one line on method chains by @duailibe
• fix(build): update ISSUE_TEMPLATE using regex ?: instead of ?! by @ikatyang
• Break closing paren of ConditionalExpression in member chains by @duailibe
• fix webstorm integration guide by @xsburg

Issues resolved in this release

• Document missing CLI options reported by @levithomason
• Formatting of Spread Properties differs between Babylon and TypeScript reported by @mariusschulz
• Removal of the declare modifier from enum reported by @mariusschulz
• Decimal formatting doesn't get all decimals in a rule. reported by @itsgreggreg
• Use resolveConfigFile.sync in the CLI reported by @azz
• CSS: Normalize case (lower vs upper) on stuff reported by @lydell
• Dynamic import with webpackChunkName comment fails reported by @pbomb
• Typescript: never as type parameter causes error: unknown type: undefined reported by @hccampos
• commented object values reported by @sylvainbaronnet
• Configuring pre-commit for jsx, Typescript, tsx reported by @reywright
• JSX ternaries include parens reported by @jasonLaster
• Chained Short Circuit Conditionals in JSX reported by @brycehill
• Support @prettier pragma comment reported by @ajhyndman
• No indentation after breaking return statement reported by @jwbay
• Support graphql() fn and so make 2nd arg prettier reported by @brikou
• prettierignore: cannot use absolute filename reported by @ambar
• Weird Javascript format reported by @maxime1992

Thank you to everyone who contributed to this release, be it through issue creation, code contribution, code review, or general commenting and feedback. Prettier is a community-run project and is able to continue to exist thanks to people like you. Thank you!

There is a collection of frequently asked questions and of course you may always ask my humans.

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

The new version differs by 6 commits.

• 55fc4d8 Merge branch 'master' of https://github.com/nickmerwin/node-coveralls
• b94fd9a version bump
• 0c147a8 fix: vulnerabilities (#227)
• 2c73fc8 Bump lodash from 4.17.11 to 4.17.14 (#229)
• cf1921d Update configuration logic for Jenkins (#217)
• f0ddec5 Add support for Azure Pipelines (#221)

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/coveralls-3.0.7 at 100.0% (Details).

The new version differs by 1 commits.

• 2ed185c added support for GitLab Merge Request IID

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

The new version differs by 27 commits.

• 0ab5c36 2.82.0
• ffdf0d3 Updating deps.
• 4386836 Merge branch 'master' of github.com:request/request
• 1527407 Merge pull request #2703 from ryysud/add-nodejs-v8-to-travis
• 3afcbf8 Merge branch 'master' of github.com:request/request
• 479143d Update of hawk and qs to latest version (#2751)
• 169be11 Add Node.js v8 to Travis CI
• 643c43a Fixed some text in README.md (#2658)
• e8fca51 chore(package): update aws-sign2 to version 0.7.0 (#2635)
• e999203 Update README to simplify & update convenience methods (#2641)
• 6f286c8 lint fix, PR from pre-standard was merged with passing tests
• a765593 Add convenience method for HTTP OPTIONS (#2541)
• 52d6945 Add promise support section to README (#2605)
• b12a624 refactor(lint): replace eslint with standard (#2579)
• 29a0b17 Merge pull request #2598 from request/greenkeeper-codecov-2.0.2

There are 27 commits in total.

See the full diff

There is a collection of frequently asked questions and of course you may always ask my humans.

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

The new version differs by 3 commits.

• dd427d7 2.83.0
• 5b623b5 Updating tough-cookie due to security fix. (#2776)
• 6f1b51e 2.82.1

See the full diff

There is a collection of frequently asked questions and of course you may always ask my humans.

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/monorepo.babel7-20200114023911 at 100.0% (Details).

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

I want to give a special shout out to @azz who has been maintaining the repository and implementing a bunch of the changes in this release as I had less time to devote to prettier due to vacation and switching team :)

Highlights

Configuration

Implement cosmiconfig for workspace configuration (#2434) by @azz

Since the very first release of prettier, people have asked for a .prettierrc file. We've been trying to have as few options as possible and tried to avoid being one more .dotfile that you have to have when starting a new project.

But, the truth is, we need to have some way to configure prettier that can be kept in sync with all the integrations. By not having one, we pushed the problem to them and saw a bunch of incompatible ways of handling the problem. So now, it's handled by prettier itself.

// .prettierrc
{
  "trailingComma": "es5",
  "singleQuote": true
}

For more information on configuration file support, see the README.

Support .prettierignore files (#2412) by @evilebottnawi

Along with telling what configuration to use, you can write a file .prettierignore to tell which files not to convert.

# .prettierignore
dist/
package.json

JSX

Improve JSX Formatting (#2398) by @suchipi

The last big friction point from people trying to adopt prettier was around how JSX was being printed. We went through all the issues that were raised and made a bunch of changes:

• Arrow Function Expressions returning JSX will now add parens when the JSX breaks

// Before
const Component = props =>
  <div>
    Hello {props.name}!
  </div>;
// After

const Component = props => (

<div>

Hello {props.name}!

</div>

);

• Conditional expressions within (or containing) JSX are formatted in a different way using parenthesis

// Before
<div>
  {props.isVisible
    ? <BaseForm
        url="/auth/google"
        method="GET"
      />
    : <Placeholder />}
</div>;
// After

<div>

{props.isVisible ? (

<BaseForm

url="/auth/google"

method="GET"

/>

) : (

<Placeholder />

)}

</div>

• JSX in logical expressions (|| or &&) is always wrapped in parens when the JSX breaks

// Before
<div>
  {props.isVisible &&
    <BaseForm
      url="/auth/google"
      method="GET"
    />}
</div>;
// After

<div>

{props.isVisible && (

<BaseForm

url="/auth/google"

method="GET"

/>

)}

</div>

Hopefully this is going to be more in line with how the majority of the community is writing JSX and we can have prettier be used in more place ;)

Inline single expressions in JSX (#2442) by @karl

With JSX, we started by respecting a lot of line breaks that were in the original source. This had the advantage of doing fewer changes to your codebase but chipped away the value of a consistent pretty printer as the same semantic code could be written in two ways.

During each new release we've tightened this and made decisions around how to always print a piece of code. The latest of those is what happens if there's a single child in a JSX object, we're now always going to inline it.

// Before
return (
  <div>
    {this.props.test}
  </div>
);
return <div>{this.props.test}</div>;
// After

return <div>{this.props.test}</div>;

return <div>{this.props.test}</div>;

Ensure there is a line break after leading JSX white space (#2348) by @karl

Leading JSX empty spaces are now on their own line. It looked weird to have them before a tag as it "indented" it differently compared to the rest.

// Before
<span className="d1">
  {' '}<a
    href="https://github.schibsted.io/finn/troika"
    className="link"
  />
</span>
// After

<span className="d1">

{' '}

<a

href="https://github.schibsted.io/finn/troika"

className="link"

/>

</span>

Other Changes

JSON

Use babylon.parseExpression for JSON (#2476) by @josephfrazier

We used to use a strict JSON parser that would throw if there was a comment or a trailing comma. This was inconvenient as many JSON files in practice are parsed using JavaScript or json5 that are not as strict. Now, we have relaxed this and are using the JavaScript parser to parse and print JSON. This means that comments will be maintained if there were some.

Note that this is purely additive, if your original file was JSON compliant, it will keep printing a valid JSON.

// Before
Syntax error
// After

{ / some comment / "a": 1 }

JavaScript

Add more supervisory parens (#2423) by @azz

Parenthesis are a hot topic because they are not part of the AST, so prettier ignores all the ones you are putting and re-creating them from scratch. We went through all the things that people reported and came up with a few edge cases that were very confusing when comparisons were chained and % was mixed with * or /.

One thing that we are not changing is the fact that we remove extra parenthesis around combinations of basic arithmetic operators: +-*/.

// Before
x !== y === z;
x * y % z;
// After

(x !== y) === z;

(x * y) % z;

Implement prettier-ignore inside JSX (#2487) by @azz

It's useful to be able to ignore pieces of JSX, it's now possible to add a comment inside of a JSX expression to ignore the formatting of the next element.

// Before
<Component>
  {/*prettier-ignore*/}
  <span ugly format="" />
</Component>
// Before

<Component>

{/prettier-ignore/}

<span     ugly  format=''   />

</Component>

Do not swallow prettier-ignore comments (#2664)

In order to support some edge cases, in the internals, we have the ability to avoid printing comments in a generic way and print them in the call site instead. It turns out that when we used prettier-ignore, we didn't print the comments at all! This is now fixed.

// Before
push(
  <td> :)
  </td>,
);
// After

push(

// prettier-ignore

<td> :)

</td>,

);

Fix indentation of a do-while condition (#2359) by @jsnajdr

It took 6 months for someone to report that do-while were broken when the while condition is multi-line, it confirms my hunch that this construct is not widely used in practice.

// Before
do {} while (
  someVeryLongFunc(
  someVeryLongArgA,
  someVeryLongArgB,
  someVeryLongArgC
)
);
// After

do {} while (

someVeryLongFunc(

someVeryLongArgA,

someVeryLongArgB,

someVeryLongArgC

)

);

Break sequence expressions (#2388) by @bakkot

Another underused feature of JavaScript is sequence expressions. We used to do a bad job at printing them when they would go multi-line, this has been corrected :)

// Before
(a = b ? c : "lllllllllllllllllllllll"), (a = b
  ? c
  : "lllllllllllllllllllllll"), (a = b ? c : "lllllllllllllllllllllll"), (a = b
  ? c
  : "lllllllllllllllllllllll"), (a = b ? c : "lllllllllllllllllllllll");
// After

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll')

Trim trailing whitespace from comments (#2494) by @azz

We took the stance with prettier to remove all the trailing whitespaces. We used to not touch comments because it's user generated, but that doesn't mean that they should have whitespace :)

// Before
// There is some space here ->______________
// After

// There is some space here ->

Fix interleaved comments in class decorators (#2660, #2661)

Our handling for comments inside of the class declaration was very naive, we would just move all the comments to the top. We now are more precise and respect the comments that are interleaved inside of decorators and around extends.

// Before
// A
// B
// C
@Foo()
@Bar()
class Bar {}
// After

// A

@Foo()

// B

@Bar()

// C

class Bar {}

Improve bind expression formatting (#2493) by @azz

Bind expressions are being discussed at TC39 and we figured we could print it with prettier. We used to be very naive about it and just chain it. Now, we use the same logic as we have for method chaining with the . operator for it. We also fixed some edge cases where it would output invalid code.

// Before
observable::filter(data => data.someTest)::throttle(() =>
  interval(10)::take(1)::takeUntil(observable::filter(data => someOtherTest))
)::map(someFunction);
// After

observable

::filter(data => data.someTest)

::throttle(() =>

interval(10)::take(1)::takeUntil(observable::filter(data => someOtherTest))

)

::map(someFunction);

Add support for printing optional catch binding (#2570) by @existentialism

It's being discussed at TC39 to be able to make the argument of a catch(e) optional. Let's make sure we can support it in prettier if people use it.

// Before
Syntax error
// After

try {} catch {}

Add support for printing optional chaining syntax (#2572) by @azz

Another new proposal being discussed at TC39 is an optional chaining syntax. This is currently a stage 1 proposal, so the syntax may change at any time.

obj?.prop       // optional static property access
obj?.[expr]     // optional dynamic property access
func?.(...args) // optional function or method call

Handle Closure Compiler type cast syntax correctly (#2484) by @yangsu

Comments are tricky to get right, but especially when they have meaning based on where they are positioned. We're now special casing the way we deal with comments used as type cast for Closure Compiler such that they keep having the same semantics.

// Before
let assignment /** @type {string} */ = getValue();
// After

let assignment = /** @type {string} */ (getValue());

Inline first computed property lookup in member chain (#2670) by @azz

It looks kind of odd to have a computed property lookup on the next line, so we added a special case to inline it.

// Before
data
  [key]('foo')
  .then(() => console.log('bar'))
  .catch(() => console.log('baz'));
// After

data[key]('foo')

.then(() => console.log('bar'))

.catch(() => console.log('baz'));

Flow

Support opaque types and export star (#2543, #2542) by @existentialism

The flow team introduced two very exciting features under a new syntax. We now support them in prettier. I've personally been waiting for opaque types for a veerrryyyy long time!

// Before
Syntax error
// After

opaque type ID = string;

export type * from "module";

Strip away unnecessary quotes in keys in type objects and interfaces (#2643)

We've been doing this on JavaScript objects since the early days of prettier but forgot to apply the same thing to Flow and TypeScript types.

// Before
type A = {
  "string": "A";
}
// After

type A = {

string: "A";

}

Print TypeParameter even when unary function type (#2406) by @danwang

Oopsy, we were dropping the generic in this very specific case.

// Before
type myFunction = A => B;
// After

type myFunction = <T>(A) => B;

Keep parens around FunctionTypeAnnotation inside ArrayTypeAnnotation (#2561) by @azz

Parenthesis... someday we'll get all of them fixed :)

// Before
const actionArray: () => void[] = [];
// After

const actionArray: (() => void)[] = [];

TypeScript

Support TypeScript 2.5 RC (#2672) by @azz

TypeScript 2.5 RC was recently announced, allowing you to use the upcoming "optional catch binding" syntax in TypeScript, too. 🎉

Don't add namespace keyword to global declaration (#2329) by @azz

// Before
namespace global {
  export namespace JSX {  }
}
// After

global {

export namespace JSX {}

}

Fix <this.Component /> (#2472) by @backus

Thanks to the untyped and permissive nature of JavaScript, we've been able to concat undefined to a string and get some interesting code as a result. Now fixed for this case :)

// Before
<undefined.Author />
// After

<this.Author />

Allow type assertions to hug (#2439) by @azz

We want to make sure that all the special cases that we added for JavaScript and Flow also work for TypeScript constructs. In this case, objects should also hug if they are wrapped in a as operator.

// Before
const state = JSON.stringify(
  {
    next: window.location.href,
    nonce,
  } as State
);
// After

const state = JSON.stringify({

next: window.location.href,

nonce,

} as State);

Remove parens for type assertions in binary expressions (#2419) by @azz

Most of the time we add parenthesis for correctness but in this case, we added them for nothing, so we can just get rid of them and have a cleaner code :)

// Before
(<x>a) || {};
// After

<x>a || {};

Print parens around type assertion as LHS in assignment (#2525) by @azz

Yet another case of missing parenthesis. Thankfully we're getting very few of them nowadays and they are for extremely rare edge cases.

// Before
foo.bar as Baz = [bar];
// After

(foo.bar as Baz) = [bar];

Print declare for TSInterfaceDeclaration (#2574) by @existentialism

The declare keyword doesn't do anything for interface so we never put it there. However, it felt weird if you were in a declaration file and seeing everything have declare before it except for interfaces. So now we reprint declare if it was there in the first place.

// Before
interface Dictionary<T> {
  [index: string]: T
}
// After

declare interface Dictionary<T> {

[index: string]: T

}

CSS

Normalize quotes in CSS (#2624) by @lydell

In order to get a first version of CSS to ship, we kept string quotes as is. We are now respecting the singleQuote option of prettier. The difficulty here was to make sure that we output correct code for all the crazy escapes, unicode characters, emoji, special rules like charset which only work with double quotes...

// Before
div {
  content: "abc";
}
// After

div {

content: 'abc';

}

Normalize numbers in CSS (#2627) by @lydell

Another place where we can reuse the logic we've done for JavaScript to improve CSS printing.

// Before
border: 1px solid rgba(0., 0.0, .0, .3);
// After

border: 1px solid rgba(0, 0, 0, 0.3);

Quote unquoted CSS attribute values in selectors (#2644) by @lydell

I can never quite remember the rules behind quotes around attributes so we're now always putting quotes there.

// Before
a[id=test] {}
// After

a[id="test"] {}

Add support for css keyword (#2337) by @zanza00

// Before
const header = css`.top-bar {background: black;margin: 0;position: fixed;}`
// After

const header = css</span></span> <span class="pl-s">  .top-bar {</span> <span class="pl-s">    background: black;</span> <span class="pl-s">    margin: 0;</span> <span class="pl-s">    position: fixed;</span> <span class="pl-s">  }</span> <span class="pl-s"><span class="pl-pds">;

Support styled-components with existing component (#2552, #2619) by @azz

styled-components has a lot of different variants for tagging template literals as CSS. It's not ideal that we've got to encode all those ways inside of prettier but since we started, might as well do it for real.

styled(ExistingComponent)`
  css: property;
`;
styled.button.attr({})</span></span> <span class="pl-s">  border: rebeccapurple;</span> <span class="pl-s"><span class="pl-pds">;

Trim whitespace in descendant combinator (#2411) by @azz

The CSS parsers we use do not give us a 100% semantic tree: in many occasions they bail and just give us what is being entered. It's up to us to make sure we clean this up while maintaining correctness. In this case, we just printed spaces between selectors as is but we know it's correct to always replace it by a single space.

// Before
.hello
        .<span class="pl-smi">how</span><span class="pl-k">-</span>you<span class="pl-k">-</span>doin {

height: 42;

}
// After

.hello .how-you-doin {

height: 42;

}

Strip BOM before parsing (#2373) by @azz
I still have nightmares from dealing with BOM in a previous life. Thankfully, in 2017 it's no longer a big issue as most tooling is now aware of it. Thanks @azz for fixing an edge cases related to CSS parsing.
// Before
[BOM]/* Block comment *
html {
  content: "#{1}";  
}
// After
[BOM]/* Block comment */
html {
  content: "#{1}";  
}
GraphQL
Add support for range-formatting GraphQL (#2319) by @josephfrazier
If you tried to use the range formatting feature in a GraphQL file, it would throw an exception, now it properly worked again and only reformats the piece you selected.
Add .gql file extension to be parsed as GraphQL (#2357) by @rrdelaney
At Facebook, we use .graphql extension but it looks like it's common to have .gql as well, doesn't cost a lot to support it in the heuristic that figures out what parser to use.
CLI
Support multiple patterns with ignore pattern (#2356) by @evilebottnawi
It was already possible to have multiple glob patterns but they would be additive, with this change, you can add a glob pattern to ignore some files. It should be very handy to ignore folders that are deeply nested.
prettier --write '{**/*,*}.{js,jsx,json}' '!vendor/**'
Make --list-different to work with --stdin (#2393) by @josephfrazier
This is a handy way of knowing if prettier would print a piece of code in a different way. We already had all the concepts in place, we just needed to wire them up correctly.
$ echo 'call ( ) ;' | prettier --list-different
(stdin)
$ echo $?
1

There is a collection of frequently asked questions and of course you may always ask my humans.

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/prettier-1.14.3 at 100.0% (Details).

🔗 Changelog

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.