Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale.
Report from using the nyc project, but crashing inside this library (node.loc presumably).
Output:
$ yarn coverage:report
yarn run v1.22.0
$ nyc report --reporter=lcov --report-dir=./coverage
Cannot read property 'loc' of undefined
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
This may because multiple runs of the test suite generates slightly different files but doesn't manage old files in .nyc_output, as deleting the dotfolder seems to remove the error.
I also get this warning, that I have no idea what to do with;
[0] [0] WARN lifecycle The node binary used for scripts is /var/folders/cc/70yk9qg16hj0kx5_5r_vq_y40000gn/T/yarn--1584505686271-0.4068172798316103/node but npm is using /Users/h/.nvm/versions/node/v11.12.0/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
Report from using the nyc project, but crashing inside this library (
node.locpresumably).Output:
Comes from running this
No other contextual info available. I haven't found a way to bump logging levels.
There's this in package.config:
...but nyc seems to prefer taking its reporters from command line.
This may because multiple runs of the test suite generates slightly different files but doesn't manage old files in
.nyc_output, as deleting the dotfolder seems to remove the error.I also get this warning, that I have no idea what to do with;