VSCode: unbound breakpoints on ng serve - angular 14

[prabh-62]

🐞 Bug report

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• extract-i18n
• run
• config
• help
• version
• doc

Is this a regression?

Yes

Description

When debugging a newly generated application within an angular 14 workspace, breakpoints are unbound(set but ignored by VSCode)

🔬 Minimal Reproduction

• > npx @angular/cli@14 new web-apps --create-application false --strict
• > cd web-apps
• > yarn ng generate app admin-console --routing --style css
• Open this angular workspace in VSCode and set breakpoint on Line 9 of projects/admin-console/src/app/app.component.ts (any valid line)
• Start debugging

🔥 Exception or Error

🌍 Your Environment

Angular CLI: 14.1.0-next.1
Node: 18.3.0 (Unsupported)
Package Manager: npm 8.11.0 
OS: darwin arm64

Angular: 14.0.2
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1401.0-next.1
@angular-devkit/build-angular   14.1.0-next.1
@angular-devkit/core            14.1.0-next.1
@angular-devkit/schematics      14.1.0-next.1
@angular/cli                    14.1.0-next.1
@schematics/angular             14.1.0-next.1
rxjs                            7.5.5
typescript                      4.7.3

❯ code --version
1.68.1
30d9c6cd9483b2cc586687151bcbcd635f373630
arm64

Anything else relevant?

[alan-agius4]

Unfortunately I am unable to replicate this locally.

One thing I noticed is that you are using an unsupported version of Node.js can you please try using an LTS version of Node.js (14 or 16).

[prabh-62]

Thank you for the suggestion. I downgraded node to 16.15.1 and VS Code can hit the breakpoints now.

[alan-agius4]

Closing since Node.js 18 is not yet supported.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}