-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update babel-eslint to the latest version 🚀 #31
base: master
Are you sure you want to change the base?
Conversation
Version 8.0.1 just got published. |
Version 8.0.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 8 commits ahead by 8, behind by 1.
See the full diff |
Version 8.0.3 just got published. |
Version 8.1.0 just got published.Update to this version instead 🚀 Release Notesv8.1.0Use ESLint's API to customize scope analysis and avoid monkeypatching: #542 |
Version 8.1.1 just got published. |
Version 8.1.2 just got published. |
Version 8.2.0 just got published. |
Version 8.2.1 just got published. |
Version 8.2.2 just got published. |
Version 8.2.3 just got published. |
Version 8.2.4 just got published.Update to this version instead 🚀 CommitsThe new version differs by 11 commits.
See the full diff |
Version 8.2.5 just got published. |
Version 8.2.6 just got published. |
Version 9.0.0 just got published.Update to this version instead 🚀 Release Notesv9.0.0v9.0.0We'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:
To enable the legacy decorators proposal users should add a specific parser option: { parserOptions: { ecmaFeatures: { legacyDecorators: true } } }
CommitsThe new version differs by 15 commits ahead by 15, behind by 2.
See the full diff |
Update to this version instead 🚀 Release Notes for v10.0.0v10.0.0Small 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> } |
Update to this version instead 🚀 Release Notes for v10.0.1v10.0.1
The |
Update to this version instead 🚀 Release Notes for v10.0.2
|
|
|
Version 8.0.0 of babel-eslint just got published.
The version 8.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of babel-eslint.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v8.0.08.0.0
No major changes, just updating babel deps to v7
Commits
The new version differs by 22 commits.
905887c
8.0.0
49493e4
update to beta.0
42d0c5b
Remove already fixed workaround (#508)
25bd208
8.0.0-alpha.17
1468905
alpha.17
57c133e
8.0.0-alpha.15
1e41162
update (#504)
c31b577
Readme update usage section (#501) [skip ci]
c2626f9
Update eslint to the latest version 🚀 (#500)
3c6b2de
chore(package): update husky to version 0.14.0 (#498)
e052d5a
Update install instructions to use latest stable release (#497) [skip ci]
8e3e088
8.0.0-alpha.13
f757e22
Merge pull request #493 from danez/regression-test
5736be6
Update babylon
37f9242
Add Prettier (#491)
There are 22 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴