eslint@3.14.0 breaks build 🚨 #35
Closed
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
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.
Hello lovely humans,
eslint just published its new version 3.14.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
no-vardoes not fix if causes ReferenceError (fixes #7950) (#7953) (Toru Nagashima)prefer-promise-reject-errorsrule (fixes #7685) (#7689) (Teddy Katz)__proto__(#7934) (Teddy Katz)The new version differs by 444 commits .
67ac93c3.14.02cf5810Build: package.json and changelog update for 3.14.0506324aFix:no-vardoes not fix if causes ReferenceError (fixes #7950) (#7953)05e7432New: no-chained-assignments rule (fixes #6424) (#7904)243e47dUpdate: Add fixer for no-else-return (fixes #7863) (#7864)f091d95New:prefer-promise-reject-errorsrule (fixes #7685) (#7689)ca01e00Fix: recognize all line terminators in func-call-spacing (fixes #7923) (#7924)a664e8aUpdate: add ignoreJSX option to no-extra-parens (Fixes #7444) (#7926)8ac3518Fix: no-useless-computed-key false positive with__proto__(#7934)c835e19Docs: remove reference to deleted rule (#7942)3c1e63bDocs: Improve examples for no-case-declarations (fixes #6716) (#7920)7e04b33Fix: Ignore inline plugin rule config in autoconfig (fixes #7860) (#7919)6448ba0Fix: add parentheses in no-extra-boolean-cast autofixer (fixes #7912) (#7914)b3f2094Fix: brace-style crash with lone block statements (fixes #7908) (#7909)5eb2e88Docs: Correct typos in configuring.md (#7916)There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.