Closed
Description
Is 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: microsoft/vscode#40293
Metadata
Metadata
Assignees
Labels
No labels