NeilClack
cc4aa8717e
Disable Vite's ANSI output (NO_COLOR/FORCE_COLOR) so the background-task problem matcher's endsPattern reliably matches, fixing the 'Error exists after running preLaunchTask' failure. Add a 'Launch Debuggable Chrome' task (:9222, persistent ~/.chrome-rw-debug profile) and an attach compound so you can debug the frontend in a Chrome you control and stay logged in. Update DEBUGGING.md.
64 lines
2.2 KiB
JSON
64 lines
2.2 KiB
JSON
{
|
|
"version": "2.0.0",
|
|
"tasks": [
|
|
{
|
|
"label": "Start Dev Server",
|
|
"detail": "Vite dev server, no inspector (use with the Frontend launch configs).",
|
|
"type": "shell",
|
|
"command": "NO_COLOR=1 FORCE_COLOR=0 NODE_EXTRA_CA_CERTS=./digital-ocean.crt ./node_modules/.bin/vite dev --port 5173 --strictPort",
|
|
"isBackground": true,
|
|
"presentation": {
|
|
"reveal": "always",
|
|
"panel": "dedicated",
|
|
"clear": true
|
|
},
|
|
"problemMatcher": [
|
|
{
|
|
"owner": "vite",
|
|
"pattern": [{ "regexp": "^.*$", "file": 0, "location": 0, "message": 0 }],
|
|
"background": {
|
|
"activeOnStart": true,
|
|
"beginsPattern": "^\\s*VITE .*ready",
|
|
"endsPattern": "^\\s*.*Local:.*http"
|
|
}
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"label": "Start Dev Server (Node Inspector)",
|
|
"detail": "Vite dev server with the Node inspector on :9229. Run Vite directly (not via npm) so the inspector owns the process that actually executes the SSR code.",
|
|
"type": "shell",
|
|
"command": "NO_COLOR=1 FORCE_COLOR=0 NODE_OPTIONS='--inspect=9229 --enable-source-maps' NODE_EXTRA_CA_CERTS=./digital-ocean.crt ./node_modules/.bin/vite dev --port 5173 --strictPort",
|
|
"isBackground": true,
|
|
"presentation": {
|
|
"reveal": "always",
|
|
"panel": "dedicated",
|
|
"clear": true
|
|
},
|
|
"problemMatcher": [
|
|
{
|
|
"owner": "vite",
|
|
"pattern": [{ "regexp": "^.*$", "file": 0, "location": 0, "message": 0 }],
|
|
"background": {
|
|
"activeOnStart": true,
|
|
"beginsPattern": "^\\s*VITE .*ready",
|
|
"endsPattern": "^\\s*.*Local:.*http"
|
|
}
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"label": "Launch Debuggable Chrome",
|
|
"detail": "Opens Google Chrome with the remote-debugging port on :9222, using a separate profile so it can run alongside your normal Chrome. Log in once; then use the 'Frontend: Chrome (attach)' launch profile. Leaves Chrome open (not a background task).",
|
|
"type": "shell",
|
|
"command": "\"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome\" --remote-debugging-port=9222 --user-data-dir=\"${userHome}/.chrome-rw-debug\" http://localhost:5173",
|
|
"isBackground": false,
|
|
"presentation": {
|
|
"reveal": "always",
|
|
"panel": "dedicated"
|
|
},
|
|
"problemMatcher": []
|
|
}
|
|
]
|
|
}
|