maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[docs] Use inspect-brk instead of debug-brk (#118108)

Browse source 
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
This commit is contained in:
Tyler Smalley 2021-11-09 13:56:06 -08:00 committed by GitHub
parent 14f6d23922
commit 21ba17d801
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/developer/contributing/development-functional-tests.asciidoc
View file

@ -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.

2
docs/developer/contributing/development-unit-tests.asciidoc
View file

@ -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.