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

## The dependency [websocket](https://github.com/theturtle32/WebSocket-Node) was updated from `1.0.28` to `1.0.29`.

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

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

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

---

Commits

The new version differs by 6 commits.

• 6e62787 Bumping version and updating readme.


• 0335951 Updating dependencies and .ignore files


• 3cb29e1 Fix gulp dependency version (git URL no longer required as 4.0.2 is already published)


• e109ba6 Include .git/ into .npmignore (fix #353)


• 58f301a Merge pull request #325 from felixrieseberg/patch-1


• 4b593f8 docs: Add windows-build-tools for Windows users

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 by inspecting the websocket 1.0.29 dependency update and the linked failing branch, then reproduce the failure through the Travis CI build. Trace the build error to determine the required dependency or project change; done means the build passes with a resolved websocket dependency state.

Vom Indexierungsmodell aus dem Issue-Text verfasst.