This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
Update nyc to the latest version 馃殌 #194
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 11.3.0 of nyc was just published.
The version 11.3.0 is not covered by your current version range.
If you don鈥檛 accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of nyc.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don鈥檛 have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 12 commits.
d85118cchore(release): 11.3.07792733chore: explicitly update istanbul dependencies (#698)222a3d0chore: slight difference in pinning logic, based on @ljharb's advicef04b7a9feat: add option to hook vm.runInContext (#680)cdfdff3feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)a413f6achore: upgrade to yargs 10 (#694)10125aadocs: fix reporters linkf5089cadocs: added examples of coverage reports (#656)af281e7chore: update spawn-wrap to 1.4.0 (#692)a685f7cdocs: missing options prefix -- in front of check-coverage (#695)f31d7a6feat: allow instrument-only to produce sourcemaps (#674)425c0fdchore: ignore package-lock.json (#683)See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 馃尨