Post

I'm glad the definitions of "column" and "line" are spelled out now. The vagueness of the original was frustrating. Ideally, there'd be some way, from the source map itself to determine how to count by code unit, and it'd be spelled out for other languages using this format. But much improved.

Yes, there were so many little details that were incredibly vague and needed to be clarified. I think that there is still room for improvement in different parts of the spec, but what we have now is already much better than how it was before :)

I use source maps as ancillary outputs from complex code generators so that I have a representation of changes to make in downstream debug symbol tables. Your work will have a lot of good knock-on effects on toolchain integration.

Source maps are already widely implemented, and compatibility was mostly ensured by checking what everybody else was doing. Over the past year, TC39-TG4 has been working hard to ensure alignment between implementations, to align the draft spec with them and to have a shared test suite.

With the solid basis provided by our new spec, we also started working on _new_ source map features to make debugging even more pleasant: stay tuned for what will come next! 😄

Please point me to blessed implementation(s) that I can look at to adopt and ensure they're not vulnerable by contributing to them if necessary :)