From 7bd8b9e99496df1e9ffa704f0c49e3878af2e684 Mon Sep 17 00:00:00 2001
From: Refringe <brownelltyler@gmail.com>
Date: Mon, 30 Oct 2023 17:34:05 -0400
Subject: [PATCH] VSCode Launch Fixes - Resolved an issue that caused the debug
 env from starting up. My bad--Doh! - Updated the testing VSCode launch option
 to use Vitest instead of Jest.

---
 project/.vscode/launch.json | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/project/.vscode/launch.json b/project/.vscode/launch.json
index e9a7190b..9c23469f 100644
--- a/project/.vscode/launch.json
+++ b/project/.vscode/launch.json
@@ -8,7 +8,7 @@
             "name": "Debug",
             "type": "node",
             "runtimeVersion": "18.15.0",
-            "runtimeExecutable": "node",
+            "runtimeExecutable": "npm",
             "request": "launch",
             "sourceMaps": true,
             "runtimeArgs": [
@@ -22,21 +22,17 @@
             "outputCapture": "std"
         },
         {
-            "name": "Run Jest UnitTests",
+            "name": "Run Vitest Tests",
             "type": "node",
             "runtimeVersion": "18.15.0",
             "runtimeExecutable": "node",
             "request": "launch",
-            "program": "${workspaceFolder}/node_modules/.bin/jest",
+            "program": "${workspaceFolder}/node_modules/.bin/vitest",
             "args": [
-                "--runInBand"
+                "run"
             ],
             "console": "integratedTerminal",
-            "internalConsoleOptions": "neverOpen",
-            "disableOptimisticBPs": true,
-            "windows": {
-                "program": "${workspaceFolder}/node_modules/jest/bin/jest",
-            }
+            "internalConsoleOptions": "neverOpen"
         }
     ]
 }