From 24c173eedcffd61a72aa4d69902dadea95690e5a Mon Sep 17 00:00:00 2001 From: Nick Iaconis Date: Thu, 30 Aug 2018 22:56:32 -0700 Subject: [PATCH] Update Troubleshooting.md (#6927) ## Summary With the existing launch configuration, VS Code automatically appends `--inspect-brk=` resulting in a command like `node --inspect-brk ${workspaceRoot}/node_modules/.bin/jest --runInBand --inspect-brk=35370`. This does not work because the debugger starts listening on port 9229, but Code attempts to attach to it on port 35370 (or whatever random port number it has selected). Adding the port parameter prevents Code from automatically appending the `--inspect-brk` flag and instructs Code attach to the debugger on port 9229. I don't think I'll need to update CHANGELOG.md for this, will I? ## Test plan This change does not include code per se, but I have run the launch configuration in my project and observed that it works properly. --- docs/Troubleshooting.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/Troubleshooting.md b/docs/Troubleshooting.md index e22d209dc0b7..72caef20636f 100644 --- a/docs/Troubleshooting.md +++ b/docs/Troubleshooting.md @@ -69,7 +69,8 @@ To automatically launch and attach to a process running your tests, use the foll "--runInBand" ], "console": "integratedTerminal", - "internalConsoleOptions": "neverOpen" + "internalConsoleOptions": "neverOpen", + "port": 9229 } ] } @@ -91,7 +92,8 @@ or the following for Windows: "--runInBand" ], "console": "integratedTerminal", - "internalConsoleOptions": "neverOpen" + "internalConsoleOptions": "neverOpen", + "port": 9229 } ] }