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

## The dependency [resolve](https://github.com/browserify/resolve) was updated from `1.11.0` to `1.11.1`.

🚨 [View failing branch](https://github.com/aethant/merino/compare/master...aethant:greenkeeper%2Fresolve-1.11.1).

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

resolve 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 failed ([Details](https://travis-ci.org/aethant/merino/builds/540906317?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 4 commits.

• b234492 v1.11.1


• 3adb367 [Fix] revert inadvertent mode change from 7c86d8f1675ce24cf86fc866ccbd258b677f3b1b


• 7c86d8f [Fix] node-modules-paths: correctly resolve paths that are on Windows networked drives


• 4c9b260 [Fix] Make behavior consistent with require.resolve() for "shadowed" core modules

See the full diff

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: