You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i noticed that when i make configuration changes, the results are not reflected when i use either nyc check-coverage or nyc report. the only way (that i can find) to force it to refresh, is by running nyc mocha
it happens regardless of if configuration options are set from package,json or the command line
it still happens when cache is set to to false
it happens with any configuration option is changed
it even happens with a new shell session
although it happens with any option, the most visually obvious option i was using test with was all. here are steps to reproduce...
### initial report
nyc report --reporter text
# no files reported (correct)
nyc report --reporter text --all
# no files reported (incorrect)
nyc mocha -all
# all files reported (correct)
nyc report --reporter text --all
# all files reported (correct)### works in reverse too
nyc report --reporter text
# no files reported (incorrect)
nyc mocha
# no files reported (correct)
nyc report --reporter text
# no files reported (correct)
The text was updated successfully, but these errors were encountered:
Both nyc report and nyc merge operate on existing results. They do not perform instrumentation, they only operate on existing files. Also note that these sub-commands do not support the --all option.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
i noticed that when i make configuration changes, the results are not reflected when i use either
nyc check-coverage
ornyc report
. the only way (that i can find) to force it to refresh, is by runningnyc mocha
package,json
or the command linecache
is set to tofalse
although it happens with any option, the most visually obvious option i was using test with was
all
. here are steps to reproduce...The text was updated successfully, but these errors were encountered: