From 21ba17d8011f7e2e1fe17c265c3218b2757b8694 Mon Sep 17 00:00:00 2001 From: Tyler Smalley Date: Tue, 9 Nov 2021 13:56:06 -0800 Subject: [PATCH] [docs] Use inspect-brk instead of debug-brk (#118108) Signed-off-by: Tyler Smalley --- .../contributing/development-functional-tests.asciidoc | 2 +- docs/developer/contributing/development-unit-tests.asciidoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/developer/contributing/development-functional-tests.asciidoc b/docs/developer/contributing/development-functional-tests.asciidoc index cb614c5149f9..4695a499ca6b 100644 --- a/docs/developer/contributing/development-functional-tests.asciidoc +++ b/docs/developer/contributing/development-functional-tests.asciidoc @@ -490,7 +490,7 @@ From the command line run: ["source","shell"] ----------- -node --debug-brk --inspect scripts/functional_test_runner +node --inspect-brk scripts/functional_test_runner ----------- This prints out a URL that you can visit in Chrome and debug your functional tests in the browser. diff --git a/docs/developer/contributing/development-unit-tests.asciidoc b/docs/developer/contributing/development-unit-tests.asciidoc index 9f0896f8a673..0a21dbbb449c 100644 --- a/docs/developer/contributing/development-unit-tests.asciidoc +++ b/docs/developer/contributing/development-unit-tests.asciidoc @@ -75,7 +75,7 @@ In order to ease the pain specialized tasks provide alternate methods for running the tests. You could also add the `--debug` option so that `node` is run using -the `--debug-brk` flag. You’ll need to connect a remote debugger such +the `--inspect-brk` flag. You’ll need to connect a remote debugger such as https://github.com/node-inspector/node-inspector[`node-inspector`] to proceed in this mode.