An in-range update of output-file is breaking the build 🚨

[greenkeeper[bot]]

The devDependency output-file was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

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

output-file is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **Travis CI - Branch:** The build **failed**.

---

Commits

The new version differs by 3 commits.

• 11df120 2.0.1
• 273caad use fs.promises.* instead of util.promisify()-ed functions
• da90a9f use if field to simplify Travis CI branch exclusion

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 Bot :palm_tree:

[greenkeeper[bot]]

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

[greenkeeper[bot]]

• The devDependency output-file was updated from 2.0.1 to 2.0.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 3bf496c 2.0.2
• 6b8906a update dependenies and devDependencies

See the full diff