-
-
Notifications
You must be signed in to change notification settings - Fork 360
Issues: istanbuljs/nyc
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Branch coverage underreported when merging Jest shards
#1581
opened Sep 12, 2024 by
mgoetz-nerdery
1 task done
[BUG]: Concurrency issue on some devices with insufficient CPU access
#1579
opened Aug 22, 2024 by
mitsuki31
1 task done
nyc report returns instrumented files instead of raw code
#1576
opened Jul 25, 2024 by
1dukky
4 tasks done
Issue with Instrumentation of Code Coverage for my Angular V17 Project
#1560
opened May 9, 2024 by
AndrewTran03
1 task done
Is there a way to filter files in the stage
nyc report
?
#1551
opened Mar 12, 2024 by
xuzhaocheng
1 task done
Code coverage is not instrumenting React components (React Native)
#1542
opened Jan 2, 2024 by
z7edge
1 task
nyc test coverage on branches is not accurate - Seems to be happening with nyc@v15, [email protected] and [email protected]
#1540
opened Dec 21, 2023 by
varunrajasekhar
1 task done
NYC checkCoverage doesn't have a way to throw error when insufficient coverage met
#1539
opened Dec 15, 2023 by
sh977218
1 task done
fix: merging two coverage reports for same source file causes crash
#1538
opened Nov 8, 2023 by
steoj
1 task done
nyc should use nodejs module customization hooks rather than monkey patching
#1534
opened Oct 17, 2023 by
jeremymeng
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.