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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ nyc (^14.0.0 → ^15.0.0) · Repo · Changelog
Release Notes
15.0.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 55 commits:
chore(release): 15.0.0
chore: Update to final releases of dependencies (#1245)
chore: Update node-preload and use process-on-spawn (#1243)
feat: Filenames relative to project cwd in coverage reports (#1212)
chore: Unpin test-exclude, update to latest pre-releases (#1240)
chore: Temporarily pin test-exclude (#1239)
chore: Lazy load modules that are rarely/never needed in test processes. (#1232)
chore: Remove cp-file module (#1230)
fix: Better error handling for main execution, reporting (#1229)
chore: Update dependencies, pin find-cache-dir (#1228)
chore: Update yargs (#1224)
chore: Fix 404 in README.md. (#1220)
chore: Add enterprise language (#1217)
chore: Remove unused functions (#1218)
docs: `npm home nyc` goes to github master branch README (#1201)
chore: Update dependencies
fix: Correct handling of source-maps for pre-instrumented files (#1216)
docs: Fix URL to default excludes in README.md (#1214)
chore: Update to async version of istanbul-lib-source-maps (#1199)
chore: Tweak arguments for async coverage data readers (#1198)
chore: Add `use strict` to all except fixtures (#1197)
chore: Update dependencies (#1196)
chore: 100% coverage (#1195)
feat: Use @istanbuljs/schema for yargs setup (#1194)
chore: Fix merge error (#1193)
feat: Add `--use-spawn-wrap=true` option (#1169)
chore: Use @istanbuljs/load-nyc-config (#1192)
chore: Use async functions where reasonable (#1184)
fix: Avoid `source-map` module during `signal-exit` handler (#1191)
chore: Coverage for signal-exit handler. (#1190)
chore: Configure tap to not use `esm` (#1189)
chore: fix minor typo (#1188)
chore: Update dependencies (#1187)
chore: Add a couple tsc tests (#1183)
fix: Honor eager setting (false by default) (#1179)
chore: Create npm-run-clean.js script (#1177)
chore: Modernize lib/source-maps.js (#1175)
chore: Remove mocha compatibility layer and chai (#1178)
chore: Remove direct use of lodash by testing. (#1176)
chore: Update dependencies (#1174)
chore: Longer delay for stale bot (#1171)
feat: Use source base name to prefix cache files (#1144)
fix: Drop coverage produced by `nyc --all` for files that were tested (#1155)
feat: Allow `nyc instrument` to instrument code in place (#1149)
chore: Upgrade lodash to ^4.17.15 to eliminate CI vulnerability (#1152)
chore: Use published version for istanbul-lib-processinfo dependency
chore: Suppress coverage for onExit callback (#1147)
feat: Use istanbul-lib-processinfo (#1145)
feat: Drop node.js 6, upgrade dependencies (#1134)
chore: Remove test artefacts that ensure failure on subsequent tests (#1138)
chore: Use snapshots for spawn output testing (#1133)
feat: Add `.cjs`, `.mjs`, `.ts`, `.tsx`, `.jsx` to default extensions (#1110)
docs: fix typo in ISSUE_TEMPLATE.md (#1116)
docs: Update README.md [skip ci] (#1114)
fix: Remove vestigial environment variables (#1078)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands