How devtools map minified JS code back to your TypeScript source code
1–10 of 18 posts
Re: How devtools map minified JS code back to your TypeScript source code
#2> Notice how the decoded values give relative positions, each value represents the difference from the previous position, not absolute coordinates. This is crucial: instead of encoding large column numbers like 27698 in minified files, source maps only store small deltas like +7 or +15, making the encoded strings much more compact.
Wouldn't "offset" be a more apt term?
Re: How devtools map minified JS code back to your TypeScript source code
#3> Notice how the decoded values give relative positions, each value represents the difference from the previous position, not absolute coordinates. This is crucial: instead of encoding large column numbers like 27698 in minified files, source maps only store small deltas like +7 or +15, making the encoded strings much more compact. Wouldn't "offset" be a more apt term?
To me, “offset” sounds more like the distance from the start, whereas here the values are relative to the previous segment.
Not a native english speaker, so I could be wrong.
Re: How devtools map minified JS code back to your TypeScript source code
#4> Notice how the decoded values give relative positions, each value represents the difference from the previous position, not absolute coordinates. This is crucial: instead of encoding large column numbers like 27698 in minified files, source maps only store small deltas like +7 or +15, making the encoded strings much more compact. Wouldn't "offset" be a more apt term?
To me, “offset” sounds more like the distance from the start, whereas here the values are relative to the previous segment. Not a native english speaker, so I could be wrong.
Offset is difference from a starting point or a previous position
Re: How devtools map minified JS code back to your TypeScript source code
#5> Notice how the decoded values give relative positions, each value represents the difference from the previous position, not absolute coordinates. This is crucial: instead of encoding large column numbers like 27698 in minified files, source maps only store small deltas like +7 or +15, making the encoded strings much more compact. Wouldn't "offset" be a more apt term?
It sounds equally apt to my ear. I've used both words for this concept in the past.
Re: How devtools map minified JS code back to your TypeScript source code
#6> Notice how the decoded values give relative positions, each value represents the difference from the previous position, not absolute coordinates. This is crucial: instead of encoding large column numbers like 27698 in minified files, source maps only store small deltas like +7 or +15, making the encoded strings much more compact. Wouldn't "offset" be a more apt term?
[deleted]
Re: How devtools map minified JS code back to your TypeScript source code
#7Tangentially related, but last year I've made a tool to recover original sources from web apps which expose source maps (with the sourcesContent value present), including enumerating all lazily loaded chunks:
Re: How devtools map minified JS code back to your TypeScript source code
#8Earlier quoted context omitted.
To me, “offset” sounds more like the distance from the start, whereas here the values are relative to the previous segment. Not a native english speaker, so I could be wrong.
Offset is difference from a starting point or a previous position
“Offset” is not enough on its own. Offset from what? Start of file? Absolute offset. Previous offset? Relative offset.
Re: How devtools map minified JS code back to your TypeScript source code
#9> Notice how the decoded values give relative positions, each value represents the difference from the previous position, not absolute coordinates. This is crucial: instead of encoding large column numbers like 27698 in minified files, source maps only store small deltas like +7 or +15, making the encoded strings much more compact. Wouldn't "offset" be a more apt term?
Delta Encoding is the common term
Re: How devtools map minified JS code back to your TypeScript source code
#10> Notice how the decoded values give relative positions, each value represents the difference from the previous position, not absolute coordinates. This is crucial: instead of encoding large column numbers like 27698 in minified files, source maps only store small deltas like +7 or +15, making the encoded strings much more compact. Wouldn't "offset" be a more apt term?
In this case I feel it's like six of one and a half-dozen of the other.
Delta definition 4: (mathematics, physics, engineering) The symbol Δ; A change in a quantity, likely from "d" for "difference"
Offset definition 7: The distance by which one thing is out of alignment with another.
Got these from Wiktionary: