DevTools/Features/SourceMap: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 20: Line 20:


The solution to this problem is a mapping from the generated JS to the original source files.
The solution to this problem is a mapping from the generated JS to the original source files.
|Feature users and use cases=Moderately sophisticated JavaScript developers.
|Feature users and use cases=Moderately sophisticated JavaScript developers.
}}
}}
Line 115: Line 114:
== Designs ==
== Designs ==


[https://docs.google.com/document/d/12E602BvlTN2j2MdAn2qk-ch4nWRhE9528tEa7_P-Gzc/ The source map file format spec originally proposed by Google]. I (fitzgen) have edit permissions and am working with them on making something we can all agree upon.
[https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit The source map file format spec originally proposed by Google]. I (fitzgen) have edit permissions and am working with them on making something we can all agree upon.


This feature is related to the [[Script_Origin_Tracking|Script Origin Tracking proposal]], because the mapping should be able to accommodate the many ways in which JavaScript can come into existence on a page.
This feature is related to the [[Script_Origin_Tracking|Script Origin Tracking proposal]], because the mapping should be able to accommodate the many ways in which JavaScript can come into existence on a page.
Confirmed users
125

edits