470486104/Server
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

VSCode Launch Fixes

Browse Source 
- 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.
This commit is contained in:
Refringe 2023-10-30 17:34:05 -04:00
parent aa512e93ef
commit 7bd8b9e994
No known key found for this signature in database
GPG Key ID: 64E03E5F892C6F9E
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
project/.vscode/launch.json vendored
View File

@ -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"
}
]
}