[Snyk] Upgrade babel-eslint from 7.2.3 to 10.0.3 #4

snyk-bot · 2019-11-06T00:44:42Z

Snyk has created this PR to upgrade babel-eslint from 7.2.3 to 10.0.3.

Warning: This is a major version upgrade, and may be a breaking change.

The recommended version is 27 versions ahead of your current version.
The recommended version was released 2 months ago, on 2019-08-25.

Release notes

Package name: babel-eslint
- 10.0.3 - 2019-08-25
  Fixes #791, also eslint/eslint#12117
  
  Some context: #793 (comment)
  
  We ended up going with @JLHwung's PR #794 which uses ESLint's deps instead of going with peerDeps since it really depends on the version being used and we don't want users to have to install it directly on their own.
  
  babel-eslint is patching patches of the dependencies of ESLint itself so these kinds of issues have happened in the past. We'll need to look into figuring out how to have a more solid way of modifying behavior instead of this monkeypatching type of thing for future releases.
- 10.0.2 - 2019-06-17
  
  Fixes #772
- 10.0.1 - 2018-09-27
  v10.0.1
  - Reverting #584
  The TypeAlias "conversion" to a function has issues. Sounds like we need to rethink the change, most likely we can just actually change the scoping rather than hardcode an AST change.
- 10.0.0 - 2018-09-25
  v10.0.0
  
  Small breaking change: add a peerDependency starting from the ESLint version that added a parser feature that we were monkeypatching before (and drop that code). If already using ESLint 5 shouldn't be any different.
  - Bugfix for TypeAlias: #584
```
/* @flow */
type Node<T> = { head: T; tail: Node<T> }
// or 
type File = {chunks: Array<Chunk>}

type Chunk = {file: File}
```
  - Update to test against ESLint 5, add a peerDependency: #689
  - Drop monkeypatching behavior: #690
- 9.0.0 - 2018-08-27
  v9.0.0
  
  We've released v7: https://twitter.com/left_pad/status/1034204330352500736, so this just updates babel-eslint to use those versions internally. That in itself doesn't break anything but:
  - Babel now supports the new decorators proposal by default, so we need to switch between the new and the old proposal. This is a breaking change.
  To enable the legacy decorators proposal users should add a specific parser option:
```
{
  parserOptions: {
    ecmaFeatures: {
      legacyDecorators: true
    }
  }
}
```
  - Babel removed the support for Node 4 , so I propagated that here.
- 9.0.0-beta.3 - 2018-07-12
  9.0.0-beta.3
- 9.0.0-beta.2 - 2018-07-06
  9.0.0-beta.2
- 9.0.0-beta.1 - 2018-06-29
  9.0.0-beta.1
- 8.2.6 - 2018-07-12
  8.2.6
- 8.2.5 - 2018-06-23
- 8.2.4 - 2018-06-22
- 8.2.3 - 2018-04-13
- 8.2.2 - 2018-02-20
- 8.2.1 - 2018-01-09
- 8.2.0 - 2018-01-08
- 8.1.2 - 2017-12-26
- 8.1.1 - 2017-12-25
- 8.1.0 - 2017-12-24
- 8.0.3 - 2017-12-01
- 8.0.2 - 2017-11-06
- 8.0.1 - 2017-09-26
- 8.0.0 - 2017-09-12
- 8.0.0-alpha.17 - 2017-07-26
- 8.0.0-alpha.15 - 2017-07-13
- 8.0.0-alpha.13 - 2017-06-18
- 8.0.0-alpha.12 - 2017-06-16
- 7.2.3 - 2017-04-21