An in-range update of @types/node is breaking the build 🚨

[greenkeeper[bot]]

Version 8.0.57 of @types/node was just published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	8.0.56
Type	devDependency

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

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ✅ **continuous-integration/codeship** Build succeeded [Details](https://app.codeship.com/projects/221684/builds/30632603) - ✅ **ci/circleci: build** Your tests passed on CircleCI! [Details](https://circleci.com/gh/dbmedialab/reader-critics/212?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - ❌ **ci/circleci: deploy_test** Your tests failed on CircleCI [Details](https://circleci.com/gh/dbmedialab/reader-critics/213?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)

---

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[phgroe]

CircleCI again. This thing turns out to be as equally stable as Wercker 🤔