This version 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 eslint-plugin-babel.
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.
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.
Coverage remained the same at 100.0% when pulling af761117bc8ba34b3c957a888f8d684857af265f on greenkeeper-eslint-plugin-babel-4.0.0 into e85ffb53a0ae27aa868b55bc1721ee32480c9187 on master.
Coverage remained the same at 100.0% when pulling bd4924c47dd24c4a2fba4dfa857cb77c2611b8c9 on greenkeeper-eslint-plugin-babel-4.0.0 into c9a1b42ac992285afdafc420d4852625c3b97415 on master.
Coverage remained the same at 100.0% when pulling bd4924c47dd24c4a2fba4dfa857cb77c2611b8c9 on greenkeeper-eslint-plugin-babel-4.0.0 into c9a1b42ac992285afdafc420d4852625c3b97415 on master.
Hello lovely humans,
eslint-plugin-babel just published its new version 4.0.0.
This version 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 eslint-plugin-babel. 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.
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 :sparkles:
You rock!
:palm_tree:
GitHub Release
Breaking Change
New Feature
babel/no-invalid-this
: doesn't fail when inside class properties #101Deprecated Rules #115
babel/generator-star-spacing
: Usegenerator-star-spacing
.babel/object-shorthand
: Useobject-shorthand
.babel/arrow-parens
: Usearrow-parens
.babel/func-params-comma-dangle
: Usecomma-dangle
.babel/array-bracket-spacing
: Usearray-bracket-spacing
.babel/flow-object-type
: Useflowtype/object-type-delimiter
.The new version differs by 14 commits .
be8d95c
4.0.0
483586f
readme: drop node < 4 [skip ci]
8073c22
Breaking: Deprecate built-in rules (#115)
ac482de
chore(package): update dependencies (#109)
aa69a6f
Updated Node versions to test against in the Travis configuration. (#110)
fc11860
Drop support of Node < 4 (#113)
026eab8
Merge pull request #101 from mathieumg/no-invalid-this
7e00840
Added
babel/no-invalid-this
rule. (Closes #12)80d66bc
Imported and adapted
no-invalid-this
rule from ESLint.c0a49d2
chore(package): update mocha to version 3.0.0 (#79)
8cf55d4
chore(package): update eslint to version 3.0.0 (#70)
078258a
Update Dependencies (#67)
4995439
--save-dev
instead of-D
[skip ci]27a7360
Run Travis CI in same Node versions as babel-eslint (#68)
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade