Update dependency eslint to version 3.14.1

[keylocation-bot]

This Pull Request updates dependency eslint from version 3.13.1 to 3.14.1

Changelog

3.14.1 / 2017-01-25
===================

• 3.14.1
• Build: package.json and changelog update for 3.14.1
• Fix: brace-style false positive for keyword method names (fixes #7974) (#7980)
• Docs: Add ESLint tutorial embed to getting started (#7971)
  I recently published a Pluralsight course on ESLint:
  https://www.pluralsight.com/courses/eslint-better-code-quality. Adding a
  youtube embed and link to the getting-started page.
  Prior context here: Share ESLint Pluralsight course snippet on eslint.org? eslint/archive-website#324
• Fix: no-var autofix syntax error in single-line statements (fixes #7961) (#7962)
• Fix: indent rule crash on sparse array with object (fixes #7959) (#7960)
• Chore: Adding assign/redeclare tests to no-undefined (refs #7964) (#7965)
• Docs: typo in prefer-promise-reject-errors (#7958)

3.14.0 / 2017-01-20
===================

• 3.14.0
• Build: package.json and changelog update for 3.14.0
• Fix: `no-var` does not fix if causes ReferenceError (fixes #7950) (#7953)
• New: no-chained-assignments rule (fixes #6424) (#7904)
• Update: Add fixer for no-else-return (fixes #7863) (#7864)
• New: `prefer-promise-reject-errors` rule (fixes #7685) (#7689)
• Fix: recognize all line terminators in func-call-spacing (fixes #7923) (#7924)
• Update: add ignoreJSX option to no-extra-parens (Fixes #7444) (#7926)
• Fix: no-useless-computed-key false positive with `proto` (#7934)
• Docs: remove reference to deleted rule (#7942)
  `space-after-keywords` appears as deleted in the docs and it's confusing to reference it.
• Docs: Improve examples for no-case-declarations (fixes #6716) (#7920)
• Fix: Ignore inline plugin rule config in autoconfig (fixes #7860) (#7919)
• Fix: add parentheses in no-extra-boolean-cast autofixer (fixes #7912) (#7914)
• Fix: brace-style crash with lone block statements (fixes #7908) (#7909)
• Docs: Correct typos in configuring.md (#7916)
  In the eqeqeq example, the word `warning` was used
  instead of `warn`
• Update: ensure brace-style validates class bodies (fixes #7608) (#7871)
• Fix: catastrophic backtracking in astUtils linebreak regex (fixes #7893) (#7898)
  • Fix: catastrophic backtracking in astUtils linebreak regex (fixes #7893)
    This fixes an issue where `astUtils.getLocationFromRangeIndex` and `astUtils.getRangeIndexFromLocation` were using a regular expression susceptible to catastrophic backtracking. The match would take quadratic time in the length of the last line of the file. Since the file in no-multiple-empty-lines performance issue (hang?) eslint/eslint#7893 contains a 1.5 million character source map URL on the last line, rules like `no-multiple-empty-lines` would hang when using ast-utils to split the file into lines.
    This issue only applies to files without trailing newlines, and is only noticable when the last line of the file contains more than 30000 characters or so. Since only a few rules use these `astUtils` functions, this would only appear when either `no-useless-escape` or `no-multiple-empty-lines` reports an error for the file.
    Simplified example: Node 7.4.0 hangs when evaluating this expression.
    ```js
    /[^\n]*\n/.test('A'.repeat(1000000))
    ```
  • Add explanatory comments
• Fix: Correct typos in no-alert.md and lib/ast-utils.js (#7905)
• Chore: Enable comma-dangle on ESLint codebase (fixes #7725) (#7906)
• Chore: update to use ES6 classes (refs #7849) (#7891)
  • Chore: update to ES6 classes (refs #7849)
  • Chore: refactor ruleFixer to be plain object (refs #7849)
  • Chore: make suggested changes (refs #7849)
• Update: refactor brace-style and fix inconsistencies (fixes #7869) (#7870)