From a5667449c498b9856228fcbeb7c3d912d92a0948 Mon Sep 17 00:00:00 2001 From: shanelanan <44124270+shanelanan@users.noreply.github.com> Date: Mon, 13 Jul 2020 16:46:05 -0400 Subject: [PATCH] Feature minor updates (#297) Co-authored-by: Shane Lanan --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 8498a7f..fadccd1 100644 --- a/README.md +++ b/README.md @@ -420,6 +420,7 @@ This project comes pre-configured with everything you need to get started. When you hit `F5` in VS Code, it looks for a top level `.vscode` folder with a `launch.json` file. You can debug in the following ways: +* **Launch Program** - transpile typescript to javascript via npm build, then launch the app with the debugger attached on startup * **Attach by Process ID** - run the project in debug mode. This is mostly identical to the "Node.js: Attach by Process ID" template with one minor change. We added `"protocol": "inspector"` which tells VS Code that we're using the latest version of Node which uses a new debug protocol. * **Jest Current File** - have a Jest test file open and active in VSCode, then debug this specific file by setting break point. All tests are not run. @@ -428,6 +429,13 @@ We added `"protocol": "inspector"` which tells VS Code that we're using the late In this file, you can tell VS Code exactly what you want to do: ```json [ + { + "name": "Launch Program", + "type": "node", + "program": "${workspaceFolder}/dist/server.js", + "request": "launch", + "preLaunchTask": "npm: build" + }, { "type": "node", "request": "attach",