But at this point, there stil is a problem in that preLaunchTask does wait for the task to finish, but the usual deno: dev / deno run dev task which binds to vite dev is long-lived (meaning it should stay alive during the debugging session).
See my feature request to make it allowed to be a background task instead : https://github.com/microsoft/vscode/issues/232200
A workaround for this second issue is to make a custom user task of the deno provided deno: dev task :
Workaround
I did succeed to make a custom
launch.json
to launch a chrome dev window and attach the vscode debugger to itlaunch.json
But at this point, there stil is a problem in that
preLaunchTask
does wait for the task to finish, but the usualdeno: dev
/deno run dev
task which binds tovite dev
is long-lived (meaning it should stay alive during the debugging session). See my feature request to make it allowed to be a background task instead : https://github.com/microsoft/vscode/issues/232200A workaround for this second issue is to make a custom user task of the deno provided
deno: dev
task :tasks.json
Now, it should work reliably, but it is far from working out of the box nor auto attaching automatically