You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running my Angular CLI project (Angular 4.1.3, CLI 1.0.3) on Chrome 58, stacktrace.js gets confused about the locations of the relevant source map files.
Instead of requesting the correct paths (/main.js.map, /vendor.js.map, etc.), it sends out a handful of failed requests for what appear to be the names of my original TypeScript source files with the extension changes to .js.map, before giving up and returning a non-source-mapped stack trace.
The text was updated successfully, but these errors were encountered:
Running my Angular CLI project (Angular 4.1.3, CLI 1.0.3) on Chrome 58, stacktrace.js gets confused about the locations of the relevant source map files.
Instead of requesting the correct paths (/main.js.map, /vendor.js.map, etc.), it sends out a handful of failed requests for what appear to be the names of my original TypeScript source files with the extension changes to .js.map, before giving up and returning a non-source-mapped stack trace.
The text was updated successfully, but these errors were encountered: