An in-range update of lodash is breaking the build 🚨
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
## The dependency [lodash](https://github.com/lodash/lodash) was updated from `4.17.11` to `4.17.12`.
🚨 [View failing branch](https://github.com/konsumer/grpcnode/compare/master...konsumer:greenkeeper%2Flodash-4.17.12).
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
lodash is a direct dependency of this project, and **it is very likely causing it to break**. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/konsumer/grpcnode/builds/556532725?utm_source=github_status&utm_medium=notification)).
---
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:
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the linked failing branch and the Travis CI build details for the lodash 4.17.12 update. Trace the build failure in the project, then verify that the dependency change no longer breaks the build and that CI passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100