From 77075df2d7c63d4dcdf3989d1b80bb90a09cd7c4 Mon Sep 17 00:00:00 2001 From: Tim van der Lippe Date: Tue, 19 May 2020 12:11:29 +0100 Subject: [PATCH] Fix debug command for Node debugging If you would run with `--inspect=true`, the following error would be thrown: [12:08:13] > node --inspect-brk=true TypeScript/node_modules/mocha/bin/_mocha -R scripts/failed-tests -O "reporter=mocha-fivemat-progress-reporter" -g "implementsJSDocReferencesDeclarationEmit" --colors -t 0 built/local/run.js Unable to resolve "true": unknown node or service --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d6ecd1d66a..80f8f4b2fd 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -152,10 +152,10 @@ You can specify which browser to use for debugging. Currently, Chrome and IE are gulp runtests-browser --tests=2dArrays --browser=chrome ``` -You can debug with VS Code or Node instead with `gulp runtests --inspect=true`: +You can debug with VS Code or Node instead with `gulp runtests --inspect`: ```Shell -gulp runtests --tests=2dArrays --inspect=true +gulp runtests --tests=2dArrays --inspect ``` You can also use the [provided VS Code launch configuration](./.vscode/launch.template.json) to launch a debug session for an open test file. Rename the file 'launch.json', open the test file of interest, and launch the debugger from the debug panel (or press F5).