Update nyc to the latest version 🚀

[greenkeeper]

Version 11.3.0 of nyc was just published.

Dependency	nyc
Current Version	11.2.1
Type	devDependency

The version 11.3.0 is not covered by your current version range.

If you don’t 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’t 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.

• d85118c chore(release): 11.3.0
• 7792733 chore: explicitly update istanbul dependencies (#698)
• 222a3d0 chore: slight difference in pinning logic, based on @ljharb's advice
• f04b7a9 feat: add option to hook vm.runInContext (#680)
• cdfdff3 feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)
• a413f6a chore: upgrade to yargs 10 (#694)
• 10125aa docs: fix reporters link
• f5089ca docs: added examples of coverage reports (#656)
• af281e7 chore: update spawn-wrap to 1.4.0 (#692)
• a685f7c docs: missing options prefix -- in front of check-coverage (#695)
• f31d7a6 feat: allow instrument-only to produce sourcemaps (#674)
• 425c0fd chore: ignore package-lock.json (#683)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[coveralls]

Coverage remained the same at 100.0% when pulling 2737771 on greenkeeper/nyc-11.3.0 into fecdc44 on master.