-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add per-package coverage reporting [work-in-progress] #465
Conversation
🦋 Changeset detectedLatest commit: 4a45229 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
GeraldRequired Reviewers
Don't want to be involved in this pull request? Comment |
Size Change: 0 B Total Size: 652 kB ℹ️ View Unchanged
|
npm Snapshot: Published🎉 Good news!! We've packaged up the latest commit from this PR (c6e8014) and published it to npm. You Example: yarn add @khanacademy/perseus@PR465 |
This is superseded by #505. |
Summary:
Flow had a command to generate coverage reports for a whole project, but TS doesn't have this capability. There is a third party package called typescript-coverage-report that provides this capability. I added a npm script "type:coverage" that can be used to produce type coverage reports for an individual package. For some reason it doesn't work with the base tsconfig.json.
Issue: None
TODO:
Test plan:
$PKG=perseus yarn type:coverage