Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency babel-eslint to v10 #49

Merged
merged 1 commit into from
Sep 26, 2018

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 25, 2018

This PR contains the following updates:

Package Type Update Change References
babel-eslint devDependencies major 9.0.0 -> 10.0.0 source

Release Notes

babel/babel-eslint

v10.0.0

Compare Source

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.

/* @​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

Renovate configuration

📅 Schedule: No schedule defined.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Renovate will regenerate this PR any time it develops a merge conflict.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


This PR has been generated by Renovate Bot. View repository job log here.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 70.466% when pulling 15b4c35 on renovate/babel-eslint-10.x into e9f8303 on master.

@srtucker22 srtucker22 merged commit d242a75 into master Sep 26, 2018
@renovate renovate bot deleted the renovate/babel-eslint-10.x branch September 26, 2018 00:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants