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

[greenkeeper]

Version 6.22.1 of babel-cli just got published.

Branch	Build failing 🚨
Dependency	babel-cli
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-cli 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 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 6.22.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[loganfsmyth]

This is because of babel/babel#5026. Maybe better to parse the JS and compare the ASTs? Tough call, we don't really guarantee identical output formatting.

[greenkeeper]

Version 6.22.2 just got published.

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

[ljharb]

That's fine, we can just update the tests.

[greenkeeper]

Version 6.24.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀