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

[greenkeeper]

Version 11.0.2 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.0.1
Type	devDependency

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

As nyc 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 💪

Status Details

• ✅ ci/circleci Your tests passed on CircleCI! Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
• ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details

---

Commits

The new version differs by 2 commits.

• e4eff12 chore(release): 11.0.2
• 0c2ef43 chore: upgrade to newer version of spawn-wrap (#592)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 11.0.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 4 commits.

• e9fad9f docs: add note about tap-nyc to README (#614)
• f86b0b1 chore(release): 11.0.3
• 923b062 fix: upgrade to spawn-wrap version that works with babel-register (#617)
• b1eb4d6 fix: update help link to list of reporters (#601)

See the full diff