From a3905bb36e8335c3afb5a786ccaf2ec778def607 Mon Sep 17 00:00:00 2001 From: Brian Yang <brianyang@users.noreply.github.com> Date: Sun, 4 Aug 2019 13:09:30 -0400 Subject: [PATCH] Update debugging-tests.md for users coming to these docs, when this doesn't work, they may come across this issue: https://github.com/facebook/create-react-app/issues/5846 and be left scratching their head why it works sometimes and not other times. discovering that v2.1.8 broke by v3.0.1 worked took some time and this should be shared with the community. --- docusaurus/docs/debugging-tests.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docusaurus/docs/debugging-tests.md b/docusaurus/docs/debugging-tests.md index d3d1aa4cb..645a07578 100644 --- a/docusaurus/docs/debugging-tests.md +++ b/docusaurus/docs/debugging-tests.md @@ -36,6 +36,13 @@ After opening that link, the Chrome Developer Tools will be displayed. Select `i > Note: the --runInBand cli option makes sure Jest runs test in the same process rather than spawning processes for individual tests. Normally Jest parallelizes test runs across processes but it is hard to debug many processes at the same time. +## Troubleshooting + +*Setting a debugger statement in my code doesn't work!* + +In older versions of `react-scripts` following these instructions *may not work*. In these cases one work-around is to update the version of `react-scripts`. Using v.3.0.1 worked. + + ## Debugging Tests in Visual Studio Code Debugging Jest tests is supported out of the box for [Visual Studio Code](https://code.visualstudio.com). -- GitLab