quisi.do

+1 to @jourdanrodrigues I was debugging this for ages and ended up forking this repo and throwing errors every-which-way to find out why it wasn't working. I eventually found that...

I'm experiencing this same problem. My coverage results look like so: `cypress/coverage-final.json`: ```json { "path/to/file.ts": { "path": "path/to/file.ts", "statementMap": { "0": { "start": { "line": 4, "column": 35 }, "end":...

My issue ended up simply being that the version of Jest needed to be downgraded to 26. No idea why 27 is broken. The instrumentation of Jest 27 is simply...

I spent a long time trying to fix it, and was not able to solve it with Jest 27. A downgrade to 26 resolved it like magic. This may need...

Hi @mjackson. Thanks for your great work! While I encourage people to use the first-party hooks, I don't want to deprecate this for users who are unable or unwilling to...

I was able to resolve this by just updating `babel-plugin-istanbul` with `yarn up -R babel-plugin-istanbul`. Cypress's code coverage package hard locks us to `[email protected]`, but the fact that the other...

@elylucas , sorry to ping directly, but as the last contributor to this repo, can you validate this? I'm still getting this warning on every install, and I'd like to...

@admah @elylucas I know y'all are in the process of migrating to the main `cypress` repository. Any chance this can get resolved for that merge?

I get this as well on my workstation using Docker for Windows. Using a mirror did not help.

`forceUpdate` uses React state, so it can only exist from the context of a React component (passed as props to other component children), or else it has to be stored...