Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"Debug Jest" suddenly stopped working
See original GitHub issueMy Jest Runner extension was running fine for months, but today it suddenly stopped. The “Debug Jest” and “Run Jest” items are still present in the context menu, but when I run them in my test file, nothing happens. There is no output in the console, and no debug session gets started.
This happens on all my test files, which all end in *.test.ts. However, I just noted that on the other files, those that do not contain any tests, the Jest Runner runs perfectly. I click on Debug Jest, and it starts a debug session which tries to run the tests of that file - except that file does not contain any test.
I tried uninstalling and reinstalling the extension, restarting VSCode. No luck, nothing happens on Debug Jest or Run Jest.
Version: 0.4.34
UPDATE: Oh wow, I just noticed that in version 0.4.33, everything still works! As soon as I install 0.4.34, the tests don’t run anymore.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:18 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
0.4.33 works for me. 0.4.34, the “Run Jest File” option is missing and neither the “Debug Jest” or “Run Jest” options do anything when clicked.
The “Run” and “Debug” inline options are also missing in 0.4.34.
please check if this is working again with v0.4.35, if not please re-open this issue,
if you have another issue which is not connected to this topic, please open a new issue.
thx for your feedback guys, pull-requests are always welcome,
best regards Tristan