This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
8c58d68fix: address edge-cases related to --all when instrumentation is disabled (#482)
8b58c05feat: allow eager instantiation of instrumenter (#490)
d8d2de0feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)
7708235chore: add test and docs for high and low watermarks (#493)
0a1d72afeat: reporting watermarks can now be set in nyc config stanza (#469)
1022b16fix: pass configuration options to --check-coverage (#483)
7b4c090chore(package): update tap to version 9.0.3 (#488)
Hello lovely humans,
nyc just published its new version 10.1.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 14 commits .
8f7af3achore(release): 10.1.08c58d68fix: address edge-cases related to --all when instrumentation is disabled (#482)8b58c05feat: allow eager instantiation of instrumenter (#490)d8d2de0feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)7708235chore: add test and docs for high and low watermarks (#493)0a1d72afeat: reporting watermarks can now be set in nyc config stanza (#469)1022b16fix: pass configuration options to --check-coverage (#483)7b4c090chore(package): update tap to version 9.0.3 (#488)093963bchore(release): 10.0.2e01ec8cfix: upgrade to newer istanbul-lib-instrument, with fixes for inferred function names (#479)2e39e00chore(release): 10.0.1e0ef1d5fix: upgrade spawn-wrap and istanbul-lib-instrument (#477)8603aa9chore(package): update is-windows to version 1.0.0 (#466)64ae4f3chore(package): update standard-version to version 4.0.0 (#461)See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade