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
I've been investigating the end-to-end sourcemap story for TypeScript through plugins like gulp-typescript and gulp-tsb. One thing that I've noticed is that gulp-sourcemaps seems to ignore and overwrite any existing "sourceRoot" property set on the sourceMap object. Is this by design, or is there a possibility of gulp-sourcemaps being able to leverage this information to better align source map output when write() is called?
The text was updated successfully, but these errors were encountered:
rbuckton
changed the title
Existing "sourceRoot" on source maps is ignored.
Existing "sourceRoot" on source maps is ignored.
Jul 10, 2016
I've been investigating the end-to-end sourcemap story for TypeScript through plugins like
gulp-typescript
andgulp-tsb
. One thing that I've noticed is thatgulp-sourcemaps
seems to ignore and overwrite any existing"sourceRoot"
property set on the sourceMap object. Is this by design, or is there a possibility ofgulp-sourcemaps
being able to leverage this information to better align source map output whenwrite()
is called?The text was updated successfully, but these errors were encountered: