Debug through source files in Chrome DevTools

Thanks for the initiative in creating this CLI tool for Chrome extensions with Angular. What I thing it’s missing is not having the option to analyze and debug the angular app implementation with source code. After creating a new project and starting it I get the fallowing warnings when inspecting the Angular popup:

DevTools failed to parse SourceMap: chrome-extension://jchfjdadafmbllfnkkmnoopppgkpdboj/runtime.js.map
DevTools failed to parse SourceMap: chrome-extension://jchfjdadafmbllfnkkmnoopppgkpdboj/polyfills.js.map
DevTools failed to parse SourceMap: chrome-extension://jchfjdadafmbllfnkkmnoopppgkpdboj/styles.js.map
DevTools failed to parse SourceMap: chrome-extension://jchfjdadafmbllfnkkmnoopppgkpdboj/vendor.js.map
DevTools failed to parse SourceMap: chrome-extension://jchfjdadafmbllfnkkmnoopppgkpdboj/main.js.map
DevTools failed to parse SourceMap: chrome-extension://jchfjdadafmbllfnkkmnoopppgkpdboj/modules-popup-popup-module.js.map

This is surely related. Don’t know if there is an issue with the generated source maps. For some reason source maps for SCSS seem OK and e.g. styles.scss can be open fine with Chrome DevTools.

[larscom]

Ill keep this issue open to see if it needs a fix from our side later on.

[Dashiing]

I’ve been digging into this issue to see if I could find a solution, but it seems to be a bug on Chrome. A fix might come around on Chrome v82: https://bugs.chromium.org/p/chromium/issues/detail?id=1052872#c14 So nothing we can do at the moment I guess.