@istanbuljs/nyc-config-typescript
Advanced tools
Comparing version 1.0.1 to 1.0.2
@@ -6,2 +6,9 @@ # Change Log | ||
### [1.0.2](https://github.com/istanbuljs/istanbuljs/compare/nyc-config-typescript-v1.0.1...nyc-config-typescript-v1.0.2) (2021-12-01) | ||
### Bug Fixes | ||
* remove unnecessary peer dependencies ([8a18fa1](https://github.com/istanbuljs/istanbuljs/commit/8a18fa1049071267dd4cd7bd2478728c99ae9a08)) | ||
## [1.0.1](https://github.com/istanbuljs/istanbuljs/compare/@istanbuljs/nyc-config-typescript@1.0.0...@istanbuljs/nyc-config-typescript@1.0.1) (2019-12-30) | ||
@@ -8,0 +15,0 @@ |
{ | ||
"name": "@istanbuljs/nyc-config-typescript", | ||
"version": "1.0.1", | ||
"version": "1.0.2", | ||
"description": "nyc configuration that works with typescript", | ||
@@ -40,7 +40,4 @@ "main": "index.js", | ||
"peerDependencies": { | ||
"nyc": ">=15", | ||
"source-map-support": "*", | ||
"ts-node": "*" | ||
}, | ||
"gitHead": "96efed94d488a1a8041a76b62014923282101880" | ||
"nyc": ">=15" | ||
} | ||
} |
@@ -27,8 +27,9 @@ # nyc-config-typescript | ||
This package specifies the `cache`, `exclude`, and `extension` options for you - only override those if you absolutely must. | ||
If you are going to modify `include` or `exclude` and you have specified a separate `outDir` in `tsconfig.json`, make sure that it remains included so that source mapping is possible. | ||
## Running Tests | ||
If you're using `mocha`: | ||
### If you're using `mocha` | ||
### test/mocha.opts | ||
In `test/mocha.opts`: | ||
@@ -42,3 +43,3 @@ ``` | ||
Now setup the test scripts in your package.json like so (with the equivalent for your test runner): | ||
Now setup the test scripts in your `package.json` like so (with the equivalent for your test runner): | ||
@@ -51,4 +52,13 @@ ```json | ||
### If you're using Jasmine | ||
In `package.json`: | ||
```json | ||
{ | ||
"test": "tsc && nyc --require ts-node/register jasmine" | ||
} | ||
``` | ||
## License | ||
ISC |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
6094
2
323363
62
2