An in-range update of babel-preset-es2015 is breaking the build 🚨

[greenkeeper[bot]]

Version 6.24.0 of babel-preset-es2015 just got published.

Branch	Build failing 🚨
Dependency	babel-preset-es2015
Current Version	6.22.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-es2015 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 :muscle:

---

Status Details

- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/borovin/router/builds/210433134) - ❌ **bitHound - Dependencies** Error analyzing branch. [Details](https://www.bithound.io/github/borovin/router/greenkeeper%2Fbabel-preset-es2015-6.24.0) - ❌ **bitHound - Code** Error analyzing branch. [Details](https://www.bithound.io/github/borovin/router/greenkeeper%2Fbabel-preset-es2015-6.24.0) - ✅ **codecov/patch** Coverage not affected when comparing 7389b41...d9b3964 [Details](https://codecov.io/gh/borovin/router/commit/d9b3964a7e9351af084decc489340feedbc9c778) - ✅ **codecov/project** 83.75% remains the same compared to 7389b41 [Details](https://codecov.io/gh/borovin/router/commit/d9b3964a7e9351af084decc489340feedbc9c778)

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

Version 6.24.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨