fix renderer process debugger regression after Angular 19 branch #849
+3
−6
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.
Description
Fixes a configuration regression introduced after the Angular 19 branch that prevented VS Code from properly debugging the renderer process.
This change updates
.vscode/launch.json,.vscode/tasks.json,angular.json, andpackage.jsonto restore correct debugger behavior and ensure breakpoints are hit.Fixes #848
Type of change
Please delete options that are not relevant.
Checklist:
Details
.vscode/launch.json: removed"sourceMapPathOverrides"because Webpack is no longer used..vscode/tasks.json: updated prelaunch and background tasks to match Angular 21 build output."endsPattern"changed from"^.*Compiled successfully.*"to"Application bundle generation complete"to correctly detect when the Angular dev server has finished building.angular.json: added missing comma in environment configurationpackage.json: update "ng:serve" script to include dev configuration (-c dev)