Fixes for VSCode Debug in Windows #3692
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in multiple issues, debugging has not been working well in VSCode neither for for Main and Renderer processes.
This fixes these issues, thus closing: #3689 #3472
It proposes the following changes:
start
script inpackage.json
Electron: Pre
launches a new script calledstart:VSCode
witch is similar tostart
but does not includenpm run start:renderer
Electron: Renderer
start thestart:renderer:VSCode
scriptwebpack.config.renderer.dev.vscode.ts
), similar to previouswebpack.config.renderer.dev.ts
, which does not launchstart:main
as this seems to prevents debugging in VSCodeElectron: Main
start thestart:main
script, which enables debugging breakpoints for VSCodeElectron: Renderer Attach
starts as before attaching to port 9223main.ts
to enable remote debugging portATTENTION: This config has only been tested in VSCode running on Win11! More testing is definitely needed! And it should be tested in different environments before merging!