Closed mawildoer closed 5 months ago
I've worked this one out! It was because the preLaunchTask
or npm: watch
was failing to start, but that was kinda obscured behind everything.
For me, the solution was to add the following snippet to the definition of it in tasks.json
:
"options": {
"cwd": "${workspaceFolder}/src/vscode-atopile"
}
Leaving this here for anyone in the future
Hey folks, thanks for the great template!
I've had a fair bit of trouble trying to debug the extension.
When I run it, or both the extension and Python, it starts a new instance of VSCode and has the extension seemingly present; however, I cannot add breakpoints, and I don't believe changing the source of the extension is having any impact.
I may be misunderstanding the scope of the TX/extension debugging features. Alternatively, some cache of the production extension is stuck somewhere, and I'm still running that.
I would appreciate any ideas to debug!