Getting tough to debug error:
See original GitHub issueHere’s a screenshot of the error I’m getting with cypress.

There’s not much info in the stack trace and searching for _jp.av0adc2("o"); isn’t helpful. Can someone offer some pointers for how to get a more understandable error? Thank you!
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:18 (15 by maintainers)
Top Results From Across the Web
What kinds of problems are the most difficult to debug? - Quora
Debugging your own code can be difficult because you have mentally solved the problem & created a design. When there is a 'bug'...
Read more >How to Debug Your Code - Codecademy
Another method of debugging your code is using error handling. Code that does not use error handling will often crash when it encounters...
Read more >Debugging - you're doing it wrong. 10 techniques to find a bug ...
Google error message; Console log everything; Use debugger; Problem localization; Create a few tests; Analyze logs; Ask a friend; Git bisect ...
Read more >Difficult Debugging: Learning From Utter Nonsense
Remember, the following steps are the key to solving difficult bugs without losing a lot of time and effort: Isolate the problem.
Read more >Debugging: Tips To Get Better At It - GeeksforGeeks
Try different solutions when you don't understand the cause and don't know how to fix the problem. If still, it's not working try...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I ran into this issue all of the sudden… Tests passed yesterday. Today rerunning CI on the same branch and they fail consistently with the webpack-dev-server error. While I don’t know why it’s happening I have a solution for anyone stumbling upon this. The solution above to swallow the xhr requests doesn’t work if the error happens outside of the test run (like in
beforeEachorafterEach) but there should really be a reason to be running hmr for tests which is what is causing the issue. The easiest way to fix this if you can is to use--inline falsewith the server https://webpack.js.org/configuration/dev-server/#devserverinlineIf you’re experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.