Add config for debugging Oni in VSCode (#255)

* add config for debugging Oni in VSCode

* add statement about provided vscode launch configurations

.vscode/launch.json

@@ -0,0 +1,35 @@
+{
+    "version": "0.2.0",
+    "configurations": [
+        {
+            // Debug files that configure Electron (main.js, Menu.js, etc.)
+            "name": "Oni Main Process",
+            "type": "node",
+            "request": "launch",
+            "cwd": "${workspaceRoot}",
+            "program": "${workspaceRoot}/main.js",
+            "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron",
+            "runtimeArgs": [
+                "--enable-logging"
+            ],
+            "console": "internalConsole"
+        },
+        {
+            // Debug typescript files
+            // (must run `npm run build-debug` first to generate bundle.js.map)
+            "name": "Oni Application",
+            "type": "chrome", // <-- requires Extension "Debugger for Chrome"
+            "request": "launch",
+            "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron",
+            "runtimeArgs": [
+                "--enable-logging",
+                "${workspaceRoot}/main.js"
+            ],
+            "webRoot": "${workspaceRoot}",
+            "sourceMaps": true,
+            "sourceMapPathOverrides": {
+                "webpack:///./*": "${webRoot}/*"
+            }
+        }
+    ]
+}

CONTRIBUTING.md

@@ -15,6 +15,8 @@ In order to build a source-map enabled build, you can do the following:
 - `npm link` (only needed the first time)
 - `oni`
 
+Debugging in [VSCode](https://github.com/Microsoft/vscode)?  Default launch configurations are provided for debugging both the Electron main process and Oni application from VSCode.
+
 ## Production build
 
 A production build removes sourcemaps and applies minification, so it's worth testing in this config: