ESLint 0.7.1 released

We just pushed ESLint 0.7.1, which is the minor release upgrade from 0.6.2. Unfortunately, due to an error in the publishing process of 0.6.2, 0.6.2 was initially pushed to npm as 0.7.0. We unpublished 0.7.0 and republished as 0.6.2. Due to npm’s security restrictions, we aren’t allowed to push a new 0.7.0 to the npm registry, which is why this version is 0.7.1.


This is a summary of the major changes you need to know about for this version of ESLint.

.eslintignore Change

As we announced previously, the JSON format for .eslintignore files has been removed. Make sure to update your .eslintignore files appropriately.

Configuration Changes

0.7.1 formalizes how configuration works when there are multiple .eslintrc files. We have implemented configuration cascading, meaning that a .eslintrc file automatically inherits the settings from the .eslintrc file in its ancestor directories. This is how configuration was always envisioned to work in ESLint, but there were several bugs in the functionality. Because these bugs have been fixed, you may notice some different behavior with your current configuration settings. For more information on the configuration hierarchy, see the Configuration documentation.

no-yoda is now yoda

In an effort to embrace different coding preferences, we’ve changed the no-yoda rule (which disallowed yoda conditions) to [yoda]( This allows you to either enforce or disallow yoda conditions.

CLI changes

The CLI has gone through an update, now allowing you to pass --color and --no-color to turn on or off color in the output. You can also use -o to specify a file to output the results into rather than outputting to the console.

Breaking Changes


Bug Fixes