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 babel-preset-es2015-loose.
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 e5005d9a73065b4a52ae70fa2f733c2b3f5e286e on greenkeeper-babel-preset-es2015-loose-8.0.0 into 9480a63226d035b7035bf24969f8a00c08a3495c on master.
Coverage remained the same at 100.0% when pulling f79f5871ff7fb0a58bd3204ec9bc9e9ef690bd71 on greenkeeper-babel-preset-es2015-loose-8.0.0 into 650e5070188bb95ccee6147968d39c122378a1f2 on master.
Coverage remained the same at 100.0% when pulling c8f7776f988fbcef00f0a49244d5e5e287882d1b on greenkeeper-babel-preset-es2015-loose-8.0.0 into de978fc6c5731a01ff2782108c7fc6bbfba21df0 on master.
Hello lovely humans,
babel-preset-es2015-loose just published its new version 8.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 babel-preset-es2015-loose. 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
Updates
modify-babel-preset
to v3.1.0, resolving some outstanding bugs.Note: This project is deprecated for users of Babel v6.13 and above, since the 'loose' option can now be set directly in the
babel-preset-2015
config.The new version differs by 14 commits .
77de3dd
Promote the RC to final release, since the modify-babel-preset bug has been resolved
4496ea2
Update version numbers
48f1613
Clarify the deprecation warning
b006ac5
Deprecation notice
45081a2
Bump to an RC version
c83b3cc
7.0.1-0
9244bc1
Upgrade to the latest modify-babel-preset
44a2cfe
Explain the peerDependency a bit more
bbfd9f0
Explain the peerDependency a bit more
0020187
Update README.md
8da4470
Update CHANGELOG.md
50fe6e7
Create CHANGELOG.md
c6ecf38
Merge pull request #6 from balupton/patch-1
aabacda
Added reference to loose mode so people can learn
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade