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.
This commit is contained in:
parent
aa512e93ef
commit
7bd8b9e994
14
project/.vscode/launch.json
vendored
14
project/.vscode/launch.json
vendored
@ -8,7 +8,7 @@
|
|||||||
"name": "Debug",
|
"name": "Debug",
|
||||||
"type": "node",
|
"type": "node",
|
||||||
"runtimeVersion": "18.15.0",
|
"runtimeVersion": "18.15.0",
|
||||||
"runtimeExecutable": "node",
|
"runtimeExecutable": "npm",
|
||||||
"request": "launch",
|
"request": "launch",
|
||||||
"sourceMaps": true,
|
"sourceMaps": true,
|
||||||
"runtimeArgs": [
|
"runtimeArgs": [
|
||||||
@ -22,21 +22,17 @@
|
|||||||
"outputCapture": "std"
|
"outputCapture": "std"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"name": "Run Jest UnitTests",
|
"name": "Run Vitest Tests",
|
||||||
"type": "node",
|
"type": "node",
|
||||||
"runtimeVersion": "18.15.0",
|
"runtimeVersion": "18.15.0",
|
||||||
"runtimeExecutable": "node",
|
"runtimeExecutable": "node",
|
||||||
"request": "launch",
|
"request": "launch",
|
||||||
"program": "${workspaceFolder}/node_modules/.bin/jest",
|
"program": "${workspaceFolder}/node_modules/.bin/vitest",
|
||||||
"args": [
|
"args": [
|
||||||
"--runInBand"
|
"run"
|
||||||
],
|
],
|
||||||
"console": "integratedTerminal",
|
"console": "integratedTerminal",
|
||||||
"internalConsoleOptions": "neverOpen",
|
"internalConsoleOptions": "neverOpen"
|
||||||
"disableOptimisticBPs": true,
|
|
||||||
"windows": {
|
|
||||||
"program": "${workspaceFolder}/node_modules/jest/bin/jest",
|
|
||||||
}
|
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user