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

[greenkeeper[bot]]

Version 0.9.11 of nightwatch just got published.

Branch	Build failing 🚨
Dependency	nightwatch
Current Version	0.9.9
Type	devDependency

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

As nightwatch 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 :muscle:

---

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/greenpioneersolutions/meanstackjs/builds/183921534)

Commits

The new version differs by 12 commits .

• 387726e 0.9.11
• d0ee441 Fixed #1289 RangeError: "Maximum call stack size exceeded", occuring when a test setting value is set to null
• f3bc41c Updated unit tests for request timeout and slight refactoring
• 1ed15e1 allow timeout + retry on selenium sessions timeout
• b2457b1 fixed unit tests
• 7802a2c improved error output when test file cannot be loaded with using tags
• 20357db Merge branch 'error-silent' of git://github.com/soundstep/nightwatch into releases/v0.9
• 4a8f2ec fixed unit tests
• fa84877 0.9.10
• d1f0377 fixed jshint warning
• 87d4bed Remove test output files.
• 0c245ae Remove try catch that load user files.

See the full diff.

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 0.9.9 your tests are passing again. Downgrade this dependency 📌.