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

## The devDependency [lodash](https://github.com/lodash/lodash) was updated from `4.17.10` to `4.17.11`.

🚨 [View failing branch](https://github.com/jdxcode/rwlockfile/compare/master...jdxcode:greenkeeper%2Flodash-4.17.11).

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

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

- ❌ **ci/circleci: node-8:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/jdxcode/rwlockfile/606?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).
- ✅ **ci/circleci: node-latest:** Your tests passed on CircleCI! ([Details](https://circleci.com/gh/jdxcode/rwlockfile/607?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).
- ✅ **continuous-integration/appveyor/branch:** AppVeyor build succeeded ([Details](https://ci.appveyor.com/project/heroku/rwlockfile/build/1.0.292)).

---

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](https://greenkeeper.io) Bot :palm_tree:

Start with the failing CircleCI node-8 build linked in the issue and compare it with the passing node-latest and AppVeyor results. Investigate the lodash 4.17.10-to-4.17.11 update; done means the project’s build and tests pass on the affected CI configuration.

Written by the indexing model from the issue text.