Follow source maps for multiple steps
Reported by
phip1611@gmail.com,
Mar 22 2017
|
|||
Issue descriptionUserAgent: 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:
,
Apr 10 2017
This is something which will be covered by Dmitrii's UI-to-UI mappings idea.
,
Dec 6 2017
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 |
|||
Comment 1 by einbinder@chromium.org
, Mar 22 2017Status: Assigned (was: Unconfirmed)