Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
10
contributors
Commits on Feb 14, 2019
-
chore: Update package-lock.json for security audit.
Update so `tap` pulls nyc@13.3.0 to avoid the vulnerable handlebars provided by nyc@13.2.0. This causes the security audit to be clean for development installs.
Commits on Feb 20, 2019
Commits on Feb 22, 2019
-
fix: Exclude negated not working with '--all' switch (#977)
* Add tests for nyc --all negated excludes * Update file walker to allow negated excludes Previously the call to glob.sync was knocking out all files in the exclude patterns, this would also knock out any files that were intended to be restored by the exclude negated patterns. This would prevent node_modules exclude negated files from being covered when run with --all.
-
chore(test): consolidate on tap test runner, stop running build step (#…
…997) * remove build step from tests * address standard nits * remove forking-tap dependency * increase tap timeout now that we have bigger test files
Commits on Feb 27, 2019
Commits on Mar 4, 2019
Commits on Mar 5, 2019
Commits on Mar 7, 2019
-
feat: Enable
es-modulesoption for nyc instrument command (#1006)BREAKING CHANGE: `nyc instrument` now enables the `--es-module` option by default.
-
feat: Fix excludeAfterRemap functionality.
Previously excludeAfterRemap caused filtering to happen before remapping to original source filenames. This caused the filtering to be completely ineffective. Fix the order, add a test to verify functionality.
Commits on Mar 9, 2019
Commits on Mar 11, 2019
Commits on Mar 12, 2019
Commits on Mar 13, 2019
Commits on Mar 17, 2019
-
feat: add
--build-process-treefeature (#1028)This allows a user to build the processinfo temp files, without actually dumping the process tree to stdout. The goal is to use this in node-tap to see which processes covered which files, so we know which tests to re-run on changes to the source files.
Commits on Mar 18, 2019
-
feat: Pass
extensionto test-exclude, use TestExclude.globSync. (#1026 -
feat: Rename
pluginsoption toparser-plugins. (#1031)The original option name created confusion about what was expected. This helps identify that babel parser plugins are expected, not babel transform plugins. BREAKING CHANGE: The `plugins` option has been renamed to `parser-plugins`. Fixes #986
-
Commits on Mar 19, 2019
Commits on Mar 28, 2019
-
test(instrument): should return unmodified source if no transform fou…
…nd (#1036) * Test that the instrument command returns unmodified source if there is no transform found for a file extension. Currently this behaviour can only be reached when trying to instrument a single file. In the case of instrumenting a directory, files with an extension with no matching transform are filtered out before they can be instrumented. * Cleanup instrumentation code again with a focus on paths The main aim of this has been to clarify whether we're working with relative or absolute file paths, and removing unnecessary transformations. Although I've made a few other 'small' changes here and there. Key changes: * Created a new private method `NYC._transform`, common to `_maybeInstrumentSource` and `instrumentAllFiles`. * Renamed the param in `walkAllFiles` forEach handler to `relFile` to explicitly state the file representation being used. * Let the `addAllFiles` visitor function rely on `testExclude` to determine which files to instrument
Commits on Apr 1, 2019
Commits on Apr 2, 2019
Commits on Apr 3, 2019
-
fix: make --all work for transpiled code (#1047)
* cache source maps globally
-
Commits on Apr 5, 2019
-
-
fix: Use a single instance of nyc for all actions of main command. (#…
…1059) This shares the same instance of nyc for execution, checking coverage and reporting.
-
Commits on Apr 6, 2019
-
fix: set processinfo pid/ppid to actual numbers (#1057)
As of Node.js v6, process.ppid is available, and a number. So, there's no need to pass the parent PID through the environment, which casts it to a string. BREAKING CHANGE: this changes the data type of the pid/ppid fields in processinfo files
-
feat: add processinfo index, add externalId (#1055)
If a NYC_PROCESSINFO_EXTERNAL_ID environment variable is set, then it is saved in the processinfo as `externalId`. Furthermore, when this file is generated, some additional helpful metadata is memoized to the processinfo json files, to minimize the cost of repeated generation. (This isn't necessarily a breaking change, but it is an update to the de facto schema for those files.) As soon as possible, index generation and process tree display should be migrated out to a new 'istanbul-lib-processinfo' library. This opens the door to add features in the v14 release family to improve support for partial/resumed test runs and file watching. - When a process is run with --clean=false and a previously seen externalId, clear away all the coverage files in the set for that externalId. - When a file is changed, a test runner can use the index to determine which tests (by externalId) ought to be re-run. - Adds a NYC_PROCESS_ID to environment - Adds `parent` to processInfo object, a uuid referring to parent. - Rebase onto processinfo-numeric-pids branch - Avoid re-writing the processinfo/{uuid}.json files - Update process tree output to rely on process index instead of duplicating effort. BREAKING CHANGE: This adds a file named 'index.json' to the .nyc_output/processinfo directory, which has a different format from the other files in this dir. -
feat: Add support for --exclude-node-modules to subcommands. (#1053)
This adds support for the `--exclude-node-modules` option/setting to instrument, check-coverage and report sub-commands. Add testing to verify that `--exclude-node-modules=false` is honored for all commands.
Commits on Apr 9, 2019
-
feat: always build the processinfo temp dir (#1061)
Always build the processinfo data directory (with index) in ${tmpdir}/processinfo. This more easily supports cases where the processinfo index may be useful for later analysis, or generating the process tree post hoc. -
-
feat: instrument
--complete-copyimplementation (#1056)With a few caveats: * This will dereference symlinks as it copies them, in some cases this could be a problem i.e. `node_modules/.bin` * This will not copy across empty directories
-
-
There are no files selected for viewing