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

## The dependency [formidable](https://github.com/node-formidable/formidable) was updated from `1.2.1` to `1.2.2`.

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

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

formidable 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/655914701?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:

Start with the Greenkeeper failing branch and the Travis CI build linked in the issue, then inspect how the direct formidable dependency is declared and updated. Reproduce the build failure and identify the dependency-compatible change; done means the project builds successfully with the updated formidable version.

Escrito por el modelo de indexación a partir del texto del issue.