This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of nyc.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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)
Coverage remained the same at 100.0% when pulling 8ddbc765d55f08d4e48a4c43546de6ec2ff34255 on greenkeeper-nyc-10.1.2 into eb491d312d2b0653fcfd76af7c582208b36eab4c on master.
Hello lovely humans,
nyc just published its new version 10.1.2.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of nyc. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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 51 commits .
e46335f
chore(release): 10.1.2
25aec77
fix: revert defaulting to empty file-coverage report, this caused too many issues
e03cd48
chore(release): 10.1.1
81229a0
fix: fix bug related to merging coverage reports see #482
8f7af3a
chore(release): 10.1.0
8c58d68
fix: address edge-cases related to --all when instrumentation is disabled (#482)
8b58c05
feat: allow eager instantiation of instrumenter (#490)
d8d2de0
feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)
7708235
chore: add test and docs for high and low watermarks (#493)
0a1d72a
feat: reporting watermarks can now be set in nyc config stanza (#469)
1022b16
fix: pass configuration options to --check-coverage (#483)
7b4c090
chore(package): update tap to version 9.0.3 (#488)
093963b
chore(release): 10.0.2
e01ec8c
fix: upgrade to newer istanbul-lib-instrument, with fixes for inferred function names (#479)
2e39e00
chore(release): 10.0.1
There are 51 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade