How devtools map minified JS code back to your TypeScript source code

1 day ago (polarsignals.com)

I love it when things are displayed so nicely on mobile. This could've been a pain to read and get through but it was actually quite pleasant.

> 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.

  • It sounds equally apt to my ear. I've used both words for this concept in the past.

  • Delta and offset mean the same thing — the difference between two amounts.

    Delta is perhaps slightly more obscure outside of a math setting. Perhaps.

    • I feel like choosing the synonym that happens to be one letter shorter when the operation is literally intended to track things in a way that's more conscise is about as "apt" as it could be!

Tangentially 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:

https://github.com/zb3/getfrontend