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

[greenkeeper[bot]]

Version 6.26.0 of babel-register just got published.

Branch	Build failing 🚨
Dependency	babel-register
Current Version	6.24.1
Type	dependency

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

babel-register is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:

Status Details

- ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/DBCDK/tanterne/66012d8306776dc48c03267f02fed1d8ee39775d/dependencies/npm?status=passing) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/DBCDK/tanterne/66012d8306776dc48c03267f02fed1d8ee39775d/files?status=passing) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/DBCDK/tanterne/builds/265308591?utm_source=github_status&utm_medium=notification)

---

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]]

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

[fvsdbc]

Fixed