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

[greenkeeper]

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency @types/lodash was updated from 4.14.149 to 4.14.150.

🚨 View failing branch.

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

@types/lodash 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

• ✅ Format files: null
• ❌ Test (Node 13): There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test (Node 12): There are 1 failures, 0 warnings, and 0 notices.
• ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
• ✅ Test (Node 8): null

---

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 4.14.149 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/lodash was updated from 4.14.150 to 4.14.151.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/lodash was updated from 4.14.151 to 4.14.152.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/lodash was updated from 4.14.152 to 4.14.153.

Your tests are still failing with this version. Compare changes

[greenkeeper]

• The devDependency @types/lodash was updated from 4.14.153 to 4.14.154.

Your tests are still failing with this version. Compare changes