#StackBounty: #angular #google-chrome #visual-studio-code #progressive-web-apps #vscode-debugger Unbound breakpoint – Angular, VS Code,…

Bounty: 50


Angular CLI: 11.2.11
Node: 14.16.0
VS Code: 1.59.0
Chrome: 92.0.4515.131 
Debugger for Chrome (Nightly): v2020.2.15300
JavaScript Debugger (Nightly): v2021.8.217
(No other VS Code extensions loaded)


Windows 10 – Running as limited user. Not able to install anything but approved software, meaning, I’m stuck with the version of Node above, I can upgrade VS Code, but not install a specific version, etc.


        "name": "Launch PWA-Chrome",
        "request": "launch",
        "type": "pwa-chrome",
        "url": "http://localhost:4200/",
        "webRoot": "${workspaceFolder}"
        "name": "Attach to Chrome",
        "port": 9222,
        "request": "attach",
        "type": "pwa-chrome",
        "webRoot": "${workspaceFolder}"


  • Occurs for a vanilla Angular app configured as a PWA. Set a
    breakpoint anywhere and get "unbound breakpoint".
  • Occurs when
    launching Chrome and when attaching to Chrome (in debug mode).
  • Does not occur for non-PWA vanilla angular app – I can debug non-PWA vanilla angular app.

Research and what I’ve tried:

  • My situation is different than this: Unbound breakpoint – VS Code | Chrome | Angular . Mine is a PWA and I always have an unbound breakpoint when starting with "ng serve".
  • Tried change in angular.json: "sourceMap": true – No effect
  • Tried "Run -> Disable All Breakpoints, then Enable All Breakpoints" – No effect
  • Tried downgrading VS Code to 1.52.1 (when debugging last worked) – No effect
  • Tried adding to webpack: devtoolModuleFilenameTemplate: ‘[absolute-resource-path]’ – No effect
  • Tried disabling all extensions, except for Chrome and JS debugger – No effect
  • Tried attaching to Chrome in debug mode – still won’t hit a breakpoint

Get this bounty!!!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.