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.
...
27
contributors
Commits on Jun 5, 2018
-
fix: source was being instrumented twice, due to upstream fix in ista… (
#853) BREAKING CHANGE: --hook-run-in-context, and --hook-run-in-this-context are no longer true by default (they should be enabled if you're using a library like requirejs).
Commits on Jun 6, 2018
Commits on Jun 8, 2018
Commits on Jun 29, 2018
-
fix: Update caching-transform options. (#873)
When updating caching--transform it was missed that the `hash` option has been refactored. This means that two files with identical contents would be treated as identical.
Commits on Jul 4, 2018
Commits on Jul 5, 2018
Commits on Jul 23, 2018
-
fix: Enable es-modules by default. (#889)
A previous fix for #796 added an es-modules option and set it false by default. This default was a change of behavior in NYC as previously all sources were parsed as ES modules by the instrumenter. I believe the old behavior is the correct default because it allows NYC to work with modern code. Code which uses certain features which violate strict mode will have to disable es-modules. This will not effect ES5 which follows the rules of 'use strict'.
Commits on Jul 24, 2018
Commits on Aug 27, 2018
-
feat: Rename --temp-directory option to --temp-dir (#897)
* Rename --temp-directory option to --temp-dir * Add -t alias Deprecates the option name --temp-directory in favour of --temp-dir --temp-directory has been demoted to a yargs alias of --temp-dir This change makes the option naming consistent using the form --*-dir
-
chore: Update language of ISSUE_TEMPLATE. (#901)
Ask for link to repository first, add text explaining the importance of linking a repository that demonstrates the bug.
Commits on Sep 6, 2018
-
feat: Bump dependencies. (#915)
This causes nyc to use final release of babel 7.
-
Commits on Oct 14, 2018
-
docs: Reference @babel/preset-env instead of @babel/env (#925)
Using the full module name may help avoid potential confusion as `npm install @babel/env` is not valid.
Commits on Nov 19, 2018
-
chore: Update dependencies. (#926)
This causes an update to mem to resolve a potential DoS vulnerability in command-line processing. The vulnerable version of mem is still included by development dependencies. Fixes #918
Commits on Jan 5, 2019
Commits on Jan 6, 2019
-
fix: missing command temp-directory (#928)
* Fix missing command temp-directory After changing tempDirectory to tempDir, with a fallback for tempDirectory, the default values set in the 'temp-dir' yargs option were being used rather than falling back to tempDirectory and then the default temp dir. This change removes the yargs default value for the option 'temp-dir'. This means the statement that assigns '_tempDirectory' in 'index.js' attempts to use temp-dir, then temp-directory, then the default value. This is now under test with some new test cases that show: - tempDir is preferred to tempDirectory - tempDirectory is used if tempDir isn't set - that we fall back to the '.nyc_output' dir if neither tempDir or tempDirectory are set. * Alternate implementation Maintains notice of default temp-dir in help output. Removed tests as I'm not confident with these right now, will take another look when I get some time. Fixes #927.
-
-
Commits on Jan 8, 2019
Commits on Jan 12, 2019
-
tests: coverage for temp-dir changes (#964)
Covers default value, legacy temp-directory option and new temp-dir option
Commits on Jan 13, 2019
Commits on Jan 15, 2019
-
feat: avoid hardcoded HOME for spawn-wrap working dir (#957)
By default, spawn-wrap writes temporary files to HOME. It used to be /tmp, but it changed that to HOME to support environments that have 'noexec' flags set on their tmpfs mount. Ref istanbuljs/spawn-wrap#3. The problem with this is that nyc now no longer works in environments without a (writable) home directory (e.g. the 'nobody' user on Linux). While it is fine to fallback to HOME, it should write elsewhere if that is unavailable, and ideally in a way that doesn't require every sysadmin or end-user to hardcode some environment variable in their package.json specifically for nyc or spawn-wrap. A common way to communicate this intent is with the XDG_CACHE_HOME environment variable. Fixes #951.
Commits on Jan 19, 2019
Commits on Jan 26, 2019
Commits on Jan 27, 2019
-
chore: Update dependencies. (#978)
* Update dependencies. * Replace legacy debug-log ponyfill with util.debuglog.
-
Commits on Feb 3, 2019
Commits on Feb 5, 2019
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
There are no files selected for viewing
This file was deleted.
This file was deleted.