Open tommyc38 opened 1 year ago
An alternative to a monkey-patch is to override the dependency
"overrides": {
"@cypress/code-coverage": {
"js-yaml": "<4.0"
}
},
looks like the bump was made by a bot and code-coverage still works fine without it https://github.com/cypress-io/code-coverage/pull/371
Logs and screenshots Please provide debug logs by running Cypress from the terminal with
DEBUG=code-coverage
environment variable set, see the Debugging section of the README file.Versions
I tried this locally (latest MacOS) as well as in my ci docker container with the same result: cypress/browsers:node16.16.0-chrome107-ff107-edge https://github.com/cypress-io/cypress-docker-images/tree/master/included - link to cypress/node images image: cypress/included:12.3.0
window.__coverage__
object? Can you paste a screenshot?.nyc_output
folder? Is there.nyc_output/out.json
file. Is it empty? Can you paste at least part of it so we can see the keys and file paths?package.json
(nyc
object) or in other NYC config files. Yes, I use a .nycrc.yaml file.Describe the bug My .nycrc.yaml file is blowing up cypress e2e tests. I have monkey patched test-utils.js to swap out
yaml.safeLoad
withyaml.load
and everything works.Link to the repo Bugs with a reproducible example, like an open source repo showing the bug, are the most likely to be resolved.
Example See #217 that is an excellent bug report example