Gathering detailed insights and metrics for typescript-coverage-report
Gathering detailed insights and metrics for typescript-coverage-report
Gathering detailed insights and metrics for typescript-coverage-report
Gathering detailed insights and metrics for typescript-coverage-report
@zooshdigital/bitbucket-v8-coverage-report
Command-line tool to upload coverage reports to Bitbucket
kl-test-typescript-coverage-report
Node command tool to generate TypeScript coverage report.
@penovicp/typescript-coverage-report
Node command tool to generate TypeScript coverage report.
@zooshdigital/bitbucket-code-insights
Function to upload reports to Bitbucket
Node command tool to generate TypeScript coverage report
npm install typescript-coverage-report
Typescript
Module System
Node Version
NPM Version
TypeScript (70.8%)
JavaScript (26.86%)
CSS (2.34%)
Total Downloads
7,261,087
Last Day
6,029
Last Week
42,560
Last Month
215,563
Last Year
2,279,434
MIT License
503 Stars
243 Commits
33 Forks
4 Watchers
8 Branches
15 Contributors
Updated on May 03, 2025
Minified
Minified + Gzipped
Latest Version
1.1.1
Package Id
typescript-coverage-report@1.1.1
Unpacked Size
1.17 MB
Size
971.10 kB
File Count
46
NPM Version
10.2.4
Node Version
21.4.0
Published on
Feb 28, 2025
Cumulative downloads
Total Downloads
Last Day
-17.7%
6,029
Compared to previous day
Last Week
-19.8%
42,560
Compared to previous week
Last Month
13.2%
215,563
Compared to previous month
Last Year
-0.1%
2,279,434
Compared to previous year
6
1
25
Node command line tool for generating TypeScript coverage reports ✨
This package fills the gap of a missing type coverage reporting tool which is present in the Flow ecosystem, strongly inspired by the amazing work done by flow-coverage-report
and using data generated by type-coverage
.
See an example of the coverage report.
To learn more about the reasoning behind this project and its roadmap, please refer to the following article: How I built a TS coverage report tool
typescript-coverage-report
can be installed locally or globally.
Users are advised to install it as a project (dev) dependency and create a script in package.json
.
1$ yarn add --dev typescript-coverage-report 2 3# OR 4 5$ npm install --save-dev typescript-coverage-report
If installed locally, add the following to the scripts section of package.json
.
1"scripts": { 2 "ts-coverage": "typescript-coverage-report" 3}
Then run:
1$ yarn ts-coverage 2 3# OR 4 5$ npm run ts-coverage
To set the minimum threshold (80% by default), use the --threshold
option.
1$ yarn ts-coverage --threshold=99
As an alternative, options may be provided through the type-coverage
configuration, specified in package.json
.
1"typeCoverage": { 2 "atLeast": 90 3}
The CLI accepts a list of arguments:
Option | Description | Default value |
---|---|---|
-t, --threshold [number] | The minimum percentage of coverage required. | 80 |
-o, --outputDir [string] | The output directory where to generate the report. | coverage-ts |
-s, --strict [boolean] | Run the check in strict mode. | false |
-d, --debug [boolean] | Show debug information. | false |
-c, --cache [boolean] | Save and reuse type check result from cache. | false |
-p, --project [string] | File path to tsconfig file, eg: --project "./app/tsconfig.app.json" | . |
-i, --ignore-files [boolean] | Ignore specified files, eg: --ignore-files "demo1/*.ts" --ignore-files "demo2/foo.ts" | false |
-u, --ignore-unread [boolean] | Allow writes to variables with implicit any types | false |
Feel free to dive in! Open an issue or submit PRs.
On this project we follow the Contributor Covenant Code of Conduct.
Thanks for contributing!
Remember to run the following commands to link your version of this package and build the TypeScript files.
1# Link the package globally, so you'll be able to test it in other projects. 2$ yarn link 3# Builds the TypeScript files and watches for changes 4$ yarn build --watch
This project follows the Angular commit messages, but it's very open to emojis 🤯.
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
MIT @ Alessandro Canessa
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
Found 2/9 approved changesets -- score normalized to 2
Reason
1 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 1
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
21 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-05-05
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More