New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 704120 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit 29 days ago
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Follow source maps for multiple steps

Reported by phip1611@gmail.com, Mar 22 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. compile typescript to javascript with embeded source map and embeded original source (compiler-options: inlineSourceMap, inlineSources
2. bundle your application with systemjs-builder with activated source map flag (so that the bundle-map points to the javascript files that are part of the bundle)
3. see the developer console: "source"-tab

What is the expected behavior?
I'd expect that Chrome first follows the individually sources of the SystemJS-bundle and then follow the source-reference in these javascript files.

What went wrong?
Chrome follows the individually sources of the SystemJS-bundle but ignores the source-references in these javascript files to the original typescript files.

Did this work before? No 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
Unbenannt.PNG
92.0 KB View Download
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: dgozman@chromium.org
This is something which will be covered by Dmitrii's UI-to-UI mappings idea.
Status: WontFix (was: Assigned)
We have no certain plans to implement UI-to-UI mappings yet - its a big effort.

There's currently a tooling in place that creates a sourcemap based on a previous sourcemap. I'd recommend using it for now.

Sign in to add a comment