An in-range update of detect-node is breaking the build 🚨

[greenkeeper]

Version 2.0.4 of detect-node was just published.

Branch	Build failing 🚨
Dependency	detect-node
Current Version	2.0.3
Type	dependency

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

detect-node 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 is in progress (Details).
• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Commits

The new version differs by 12 commits.

• 563e0b8 Merge pull request #10 from honzajavorek/honzajavorek/cut-version-2.0.4
• 33ae967 2.0.4
• adeee71 Merge pull request #8 from OmgImAlexis/master
• 6eab0ec fix header
• c82e90d Create LICENSE
• 802d448 Merge pull request #5 from gusuni/patch-1
• 897f35e Update index.js
• 4e7a588 Merge pull request #2 from pornel/master
• 313cae8 Simpler version for browserify
• 6807a6f Check if process exists
• b6037f1 Merge pull request #1 from shuvalov-anton/patch-1
• 78c08d1 Update Readme.md

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 2.0.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.