babel/babel-eslint
### [`v10.1.0`](https://togithub.com/babel/babel-eslint/releases/tag/v10.1.0)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v10.0.3...v10.1.0)
- Added ability to parse Flow enums [#812](https://togithub.com/babel/babel-eslint/pull/812) ([@gkz](https://togithub.com/gkz))
### [`v10.0.3`](https://togithub.com/babel/babel-eslint/releases/tag/v10.0.3)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v10.0.2...v10.0.3)
Fixes [https://github.com/babel/babel-eslint/issues/791](https://togithub.com/babel/babel-eslint/issues/791), also [https://github.com/eslint/eslint/issues/12117](https://togithub.com/eslint/eslint/issues/12117)
Some context: [https://github.com/babel/babel-eslint/pull/793#issuecomment-524435971](https://togithub.com/babel/babel-eslint/pull/793#issuecomment-524435971)
We ended up going with [@JLHwung](https://togithub.com/JLHwung)'s PR [https://github.com/babel/babel-eslint/pull/794](https://togithub.com/babel/babel-eslint/pull/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.
### [`v10.0.2`](https://togithub.com/babel/babel-eslint/releases/tag/v10.0.2)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v10.0.1...v10.0.2)
> Fixes [https://github.com/babel/babel-eslint/issues/772](https://togithub.com/babel/babel-eslint/issues/772)
### [`v10.0.1`](https://togithub.com/babel/babel-eslint/releases/tag/v10.0.1)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v10.0.0...v10.0.1)
### v10.0.1
- Reverting [https://github.com/babel/babel-eslint/pull/584](https://togithub.com/babel/babel-eslint/pull/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.
### [`v10.0.0`](https://togithub.com/babel/babel-eslint/releases/tag/v10.0.0)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v9.0.0...v10.0.0)
### 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`: [https://github.com/babel/babel-eslint/pull/584](https://togithub.com/babel/babel-eslint/pull/584)
```js
/* @flow */
type Node = { head: T; tail: Node }
// or
type File = {chunks: Array}
type Chunk = {file: File}
```
- Update to test against ESLint 5, add a peerDependency: [https://github.com/babel/babel-eslint/pull/689](https://togithub.com/babel/babel-eslint/pull/689)
- Drop monkeypatching behavior: [https://github.com/babel/babel-eslint/pull/690](https://togithub.com/babel/babel-eslint/pull/690)
### [`v9.0.0`](https://togithub.com/babel/babel-eslint/releases/tag/v9.0.0)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v8.2.6...v9.0.0)
### 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:
```js
{
parserOptions: {
ecmaFeatures: {
legacyDecorators: true
}
}
}
```
- Babel removed the support for Node 4 , so I propagated that here.
### [`v8.2.6`](https://togithub.com/babel/babel-eslint/compare/v8.2.5...v8.2.6)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v8.2.5...v8.2.6)
### [`v8.2.5`](https://togithub.com/babel/babel-eslint/compare/v8.2.4...v8.2.5)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v8.2.4...v8.2.5)
### [`v8.2.4`](https://togithub.com/babel/babel-eslint/compare/v8.2.3...v8.2.4)
[Compare Source](https://togithub.com/babel/babel-eslint/compare/v8.2.3...v8.2.4)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
^8.2.3
->^10.0.0
Release Notes
babel/babel-eslint
### [`v10.1.0`](https://togithub.com/babel/babel-eslint/releases/tag/v10.1.0) [Compare Source](https://togithub.com/babel/babel-eslint/compare/v10.0.3...v10.1.0) - Added ability to parse Flow enums [#812](https://togithub.com/babel/babel-eslint/pull/812) ([@gkz](https://togithub.com/gkz)) ### [`v10.0.3`](https://togithub.com/babel/babel-eslint/releases/tag/v10.0.3) [Compare Source](https://togithub.com/babel/babel-eslint/compare/v10.0.2...v10.0.3) Fixes [https://github.com/babel/babel-eslint/issues/791](https://togithub.com/babel/babel-eslint/issues/791), also [https://github.com/eslint/eslint/issues/12117](https://togithub.com/eslint/eslint/issues/12117) Some context: [https://github.com/babel/babel-eslint/pull/793#issuecomment-524435971](https://togithub.com/babel/babel-eslint/pull/793#issuecomment-524435971) We ended up going with [@JLHwung](https://togithub.com/JLHwung)'s PR [https://github.com/babel/babel-eslint/pull/794](https://togithub.com/babel/babel-eslint/pull/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. ### [`v10.0.2`](https://togithub.com/babel/babel-eslint/releases/tag/v10.0.2) [Compare Source](https://togithub.com/babel/babel-eslint/compare/v10.0.1...v10.0.2) > Fixes [https://github.com/babel/babel-eslint/issues/772](https://togithub.com/babel/babel-eslint/issues/772) ### [`v10.0.1`](https://togithub.com/babel/babel-eslint/releases/tag/v10.0.1) [Compare Source](https://togithub.com/babel/babel-eslint/compare/v10.0.0...v10.0.1) ### v10.0.1 - Reverting [https://github.com/babel/babel-eslint/pull/584](https://togithub.com/babel/babel-eslint/pull/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. ### [`v10.0.0`](https://togithub.com/babel/babel-eslint/releases/tag/v10.0.0) [Compare Source](https://togithub.com/babel/babel-eslint/compare/v9.0.0...v10.0.0) ### 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`: [https://github.com/babel/babel-eslint/pull/584](https://togithub.com/babel/babel-eslint/pull/584) ```js /* @flow */ type NodeConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.