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

## The dependency [mout](https://github.com/mout/mout) was updated from `1.1.0` to `1.2.0`.

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

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

mout 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/609049226?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 15 commits.

• 8bc8a78 Merge pull request #213 from fourcube/master


• 0cd1ad2 Merge pull request #256 from martin-dimitrov13/master


• 75c3b86 Merge pull request #260 from mout/dependabot/npm_and_yarn/js-yaml-3.13.1


• 9c1dbf6 Merge pull request #259 from mout/dependabot/npm_and_yarn/handlebars-4.1.2


• e6f9d98 Bump js-yaml from 3.10.0 to 3.13.1


• 4c32505 Bump handlebars from 4.0.11 to 4.1.2


• 98f98ce Updated CHANGELOG.md with the correct change date


• 32e52a1 Merge branch 'master' into master


• b06287a Changes as per git comments


• a7ecd36 update dependencies


• 4a5d9fe Moved the null check up


• 5a6b434 Fixed object/get throwing exception for null or undefined input objects


• 7644d06 update node versions for testing


• 19a30bf fixes build script with rimraf change


• aa1b248 Add string/stripMargin

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:

Start with the failing Greenkeeper branch and the Travis CI build linked in the issue, then inspect where the mout dependency is declared and used. Compare mout 1.1.0 with 1.2.0 and identify the source of the build failure. Done means the project builds successfully with the in-range update and its checks pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.