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
(using version 1.6.0-dev.20150825, with --declaration --module CommonJS --target ES5)
For some typescript code inputs, the compiler creates invalid mapping entry, mapping characters from the compiled code to the line break character at the end of the source line.
Sometimes, the mapped character from the compiled code is itself non-existent in the compiled file, like the last character in the last line.
for example, this code:
Amir Arad (@amir-arad). while investigating this here are the mapping entries(note I converted them into 1 based while printing) for visualization as shown here
Represent name Product correctly in source and emitted file.
I am looking into fixing the encoded mappings of kind 1:16, 2:23 in source as you mentioned because theoretically It should instead be next line column 0 in source instead.
signifies the one-after-last character in destination code (just before //# sourceMappingURL) , mapped to the one-after-last character in source. any thoughts on that?
Activity
mhegazy commentedon Sep 1, 2015
Sheetal Nandi (@sheetalkamat) can you take a look.
sheetalkamat commentedon Sep 8, 2015
Amir Arad (@amir-arad). while investigating this here are the mapping entries(note I converted them into 1 based while printing) for visualization as shown here
Note that
Represent name Product correctly in source and emitted file.
I am looking into fixing the encoded mappings of kind 1:16, 2:23 in source as you mentioned because theoretically It should instead be next line column 0 in source instead.
amir-arad commentedon Sep 24, 2015
Thank you.
What about the last mapping? in your entries, this line:
signifies the one-after-last character in destination code (just before //# sourceMappingURL) , mapped to the one-after-last character in source. any thoughts on that?
Add test for #4591
mhegazy commentedon Sep 29, 2016
This should be working as expected in latest.