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

[greenkeeper]

The devDependency @types/node was updated from 12.12.6 to 12.12.7.

🚨 View failing branch.

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

• ❌ Test on node 12.x and macOS-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 12.x and windows-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 12.x and ubuntu-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 10.x and macOS-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 10.x and windows-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 10.x and ubuntu-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 8.12.x and macOS-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 8.12.x and windows-latest: There are 1 failures, 0 warnings, and 0 notices.
• ❌ Test on node 8.12.x and ubuntu-latest: There are 2 failures, 0 warnings, and 0 notices.

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[greenkeeper]

• The devDependency @types/node was updated from 12.12.7 to 12.12.8.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/node was updated from 12.12.8 to 12.12.9.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/node was updated from 12.12.9 to 12.12.10.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/node was updated from 12.12.10 to 12.12.11.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/node was updated from 12.12.11 to 12.12.12.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/node was updated from 12.12.12 to 12.12.13.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/node was updated from 12.12.13 to 12.12.14.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/node was updated from 12.12.14 to 12.12.15.

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

[greenkeeper]

• The devDependency @types/node was updated from 12.12.15 to 12.12.16.

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

[greenkeeper]

• The devDependency @types/node was updated from 12.12.16 to 12.12.17.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/node was updated from 12.12.18 to 12.12.19.

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

[greenkeeper]

• The devDependency @types/node was updated from 12.12.19 to 12.12.20.

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

[greenkeeper]

• The devDependency @types/node was updated from 12.12.20 to 12.12.21.

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

[greenkeeper]

• The devDependency @types/node was updated from 13.1.0 to 13.1.1.

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

[greenkeeper]

• The devDependency @types/node was updated from 13.1.5 to 13.1.6.

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

[agilgur5]

This was probably failing due to the intermittent persistent CI errors that #504 fixed.