Stop using Node --inspect option in the docs on debugging
#1998
Conversation
The technique described in the instructions does not pick up breakpoints set with `debugger` statements. This issue is being tracked by jestjs#1652, but it's unclear how long it will take to resolve as it's actually a Node issue. As a work-around, have updated docs to describe connecting an external debugger to the Node process.
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at [email protected]. Thanks! If you are contributing on behalf of someone else (eg your employer): the individual CLA is not sufficient - use https://developers.facebook.com/opensource/cla?type=company instead. Contact [email protected] if you have any questions. |
|
thanks |
) The technique described in the instructions does not pick up breakpoints set with `debugger` statements. This issue is being tracked by jestjs#1652, but it's unclear how long it will take to resolve as it's actually a Node issue. As a work-around, have updated docs to describe connecting an external debugger to the Node process.
) The technique described in the instructions does not pick up breakpoints set with `debugger` statements. This issue is being tracked by jestjs#1652, but it's unclear how long it will take to resolve as it's actually a Node issue. As a work-around, have updated docs to describe connecting an external debugger to the Node process.
) The technique described in the instructions does not pick up breakpoints set with `debugger` statements. This issue is being tracked by jestjs#1652, but it's unclear how long it will take to resolve as it's actually a Node issue. As a work-around, have updated docs to describe connecting an external debugger to the Node process.
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Stop using Node
--inspectoption in the docs on debuggingThe technique described in the instructions does not pick up
breakpoints set with
debuggerstatements. This issue is beingtracked by #1652, but
it's unclear how long it will take to resolve as it's actually
a Node issue.
As a work-around, have updated docs to describe connecting an
external debugger to the Node process.
Test plan
I have locally generated and previewed the updated documentation using the
npm startcommand in thewebsitedirectory.