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

[Greenkeeper]

Version 0.11.7 of reify just got published.

Branch	Build failing 🚨
Dependency	reify
Current Version	0.11.6
Type	devDependency

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

As reify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 12 commits.

• 15afe05 Bump NPM version to 0.11.7 in preparation for publishing.
• 96c5fb2 Use more direct module paths in repl-hook.
• 62d89a5 Use const in getReifyRange.
• 28649f0 Minor compile-hook cleanup.
• 1735229 Use existing path apis in fast-path replace.
• bdd307f Use getStackAt helper for fast-path getValue.
• 59dcf91 Move more helpers to lib/utils.
• 0409404 Minor live test cleanup.
• bb41a30 Cleanup webpack conditionals.
• 1f10bc6 Make the repl hook a bit more attachable.
• e4f709b Add getRootModule to node/utils.
• 43c563f Fix bundle for repl-hook.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴