An in-range update of require-inject is breaking the build 🚨

[Greenkeeper]

The devDependency require-inject was updated from 1.4.3 to 1.4.4.

🚨 View failing branch.

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

require-inject 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
• ❌ coverage/coveralls: First build on greenkeeper/require-inject-1.4.4 at 87.651% (Details).

---

Commits

The new version differs by 11 commits.

• b1cc122 chore(release): 1.4.4
• 195690c chore(test): Fix test calls
• 1085553 docs(contributing): updated CONTRIBUTING.md
• f01c056 docs(coc): updated CODE_OF_CONDUCT.md
• bd43f7e docs(github): Add pull request template
• 9c5650f chore: Add package-lock
• 86a34f7 chore: Run tests in parallel
• 9ae3a77 tap@12.1.1
• c41968b chore: Add my standard boilerplate
• 25cac11 fix(loaded): Ensure mocked module’s loaded state is set. (#17)
• 4d6f0f5 docs(readme): Fix object syntax in README (#15)

See the full diff

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 1.4.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.