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)
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 100.0% when pulling e2725e9c2ba24ab17f213d24a1112b8bbb44c060 on greenkeeper-nyc-10.2.0 into a73f00e6ac119869267951e41b8d46d97feeb849 on master.
Hello lovely humans,
nyc just published its new version 10.2.0.
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 49 commits .
455619f
chore(release): 10.2.0
95cc09a
feat: upgrade to version of yargs with extend support (#541)
43535f9
chore: explicit update of istanbuljs dependencies (#535)
98ebdff
feat: allow babel cache to be enabled (#517)
50adde4
feat: exclude the coverage/ folder by default 🚀 (#502)
6a59834
chore(package): update tap to version 10.0.0 (#507)
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)
There are 49 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.