Debug CRA Tests stopped working on VSCode v1.19
See original GitHub issueIs this a bug report?
Yes
Can you also reproduce the problem with npm 4.x?
Yes
Which terms did you search for in User Guide?
Debug CRA Tests in VS Code https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#debugging-tests-in-visual-studio-code
Environment
node -v
:v8.9.1
npm -v
:4.1.2
yarn --version
(if you use Yarn): No yarnnpm ls react-scripts
(if you haven’t ejected):-- (empty)
Then, specify:
- Operating system: Windows 10
- Browser and version (if relevant): not relevant
Steps to Reproduce
- Open VS Code 1.19
- Setup a launch configuration as described here: https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#debugging-tests-in-visual-studio-code
- Fire the debugger with F5 or play on the debugging panel
- The debugger doesn’t start the test scripts and eventually fires a timeout
- Rollback to VSCode version 1.18
- Follow steps 1-2
- The debugger starts the test scripts and properly attaches to the debugger
Expected Behavior
Debug CRA Test launch configuration works on VSCode 1.19 (similar to VSCode 1.18).
No changes between VSCode versions, or an updated version of the documentation to setup the launch configuration.
Actual Behavior
- The launch configuration doesn’t start the test scripts
- The debugger doesn’t attach to the test process
- Timeout error is thrown on VS Code
References
The changelog for VSCode 1.19 mentions new additions on the debugging experience: https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#debugging-tests-in-visual-studio-code
Issue created on VSCode: https://github.com/Microsoft/vscode/issues/40293
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Debug CRA Tests stopped working on v1.19 #40293 - GitHub
Fire the debugger with F5 or play on the debugging panel; The debugger doesn't start the test scripts and eventually fires a timeout;...
Read more >Debugging in Visual Studio Code
VS Code maintains a debug session while the program is running, and pressing the Stop button terminates the program. Tip: The Run action...
Read more >Debugging jest unit tests with create-react-app doesn't hit ...
When I run debug "Debug CRA Tests" everything kind of working and test passes but it doesn't hit breakpoint in VSCode. Have I...
Read more >Troubleshooting - Jest
There are multiple ways to debug Jest tests with Visual Studio Code's built-in debugger. ... More information on Node debugging can be found...
Read more >How to Debug Jest Tests in VS Code for React - YouTube
In this video we learn how to debug jest tests in visual studio code for a react project. We also learn how to...
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 FreeTop 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
Top GitHub Comments
Turned out I needed Node@v8+ Older project, so I had to bump my .nvmrc file
The VSCode team provided the correct configuration for
launch.json
. Apparently, the configuration documented on Create React App was working accidentaly due to a VS Code bug that was addressed on the latest version 1.19.Here’s the verified working code since VSCode 1.19, in case someone runs onto this. Let me know if you would like me to update the documentation (or if someone on the CRA team can do that).