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

[greenkeeper]

The dependency colors was updated from 1.3.3 to 1.4.0.

🚨 View failing branch.

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

colors 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 passed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/colors-1.4.0 at 93.322% (Details).
• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 8 commits.

• baa0e1c update roadmap
• 56de9f0 Add bright/light colors, closes #128
• b4d964b Make stylize() work for non-ASCI styles (#155)
• a1407ae Document colors.enable() and .disable() (#255)
• acb7f66 Merge branch 'develop' of github.com:Marak/colors.js into develop
• 9bfb136 more node versions
• 5d9eb90 Fixed: throws non-intuitive error on color.red(null) but not on colors.red(undefined) (#261)
• aa012aa Redo weak equality check so we can colorize null in safe mode (#257)

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 1.3.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.