You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
Following up on #70 and #46, I'm looking for an ideal vscode setup to debug the application on the back as well as the front end. The "Debug Tests" configuration (shown below) works fine for me, but I'm not really happy with the "Launch Chrome" configuration, because:
Although it works, it requires I first run the npm start task, which opens its own browser window.
I then have to run "Launch Chrome" manually after the fact, leaving me with now 2 open browser windows, only the last of which is attached.
Any way to do this with just one launch configuration?
Note: "preLaunchTask": "start" just hangs and times out.
Following up on #70 and #46, I'm looking for an ideal vscode setup to debug the application on the back as well as the front end. The "Debug Tests" configuration (shown below) works fine for me, but I'm not really happy with the "Launch Chrome" configuration, because:
npm start
task, which opens its own browser window.Any way to do this with just one launch configuration?
Note: "preLaunchTask": "start" just hangs and times out.
launch.json
tasks.json
The text was updated successfully, but these errors were encountered: