Update eslint to version 3 #13554
Merged
Update eslint to version 3 #13554
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates our eslint dependency from ^2.8.0 to ^3.7.1. The latest version of ESLint is 3.16.1 but 3.7.1 is the [version currently used by Hound](https://github.com/houndci/linters/blob/master/package.json#L11) and I'm hoping to enable that soon. To my great surprise, no code or configuration changes were necessary for this upgrade. You can see the ["Migrating to v3.0.0"](http://eslint.org/docs/user-guide/migrating-to-3.0.0) docs here - it turns out we already did everything we need to do to stay compatible.
davidsbailey
approved these changes
Mar 2, 2017
|
Sadly, it looks like Hound for JS is not happening yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates our eslint dependency from ^2.8.0 to ^3.7.1. The latest version of ESLint is 3.16.1 but 3.7.1 is the version currently used by Hound and I'm hoping to enable that soon.
To my great surprise, no code or configuration changes were necessary for this upgrade. You can see the "Migrating to v3.0.0" docs here - it turns out we already did everything we need to do to stay compatible.