[Webkit-unassigned] [Bug 110493] Web Inspector: Segment built files by module boundaries as alternative to sourceURL

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 21 13:02:26 PST 2013


https://bugs.webkit.org/show_bug.cgi?id=110493





--- Comment #2 from James Burke <jrburke at gmail.com>  2013-02-21 13:04:49 PST ---
(In reply to comment #1)
> It would be helpful to explain why the combined files are hard to debug. That would help clarify what solution would really help. 

* associating line numbers back to the unbundled files. This is mainly useful for any errors that are generated. Although, for longer modules, matching up line numbers to the unbundled code in the debugger would informative.

* easier access in the debugger to select segments of the bundled file. So, if I know I want to do debugging in "some/thing", being able to select that module as an item in the script list.

> Just to note, the bigger problem with debugging performance code is compression. I'm not sure this feature would be worth the cost/benefit given that ES modules will have native support for the names.

I am not sure I follow this. If you mean debugging minified code, I expect source maps to be used for that.

On treating module names like function names: that would likely allow the separate selection via the debugger interface, but would not have the line numbers relative to the module container, so not as useful for correlation back to the source files.

> Parsing every source for these strings just in case they may be present is a significant overhead.  //@ sourceURL is always at the end. Maybe we could have a //@ amdSource tag at the end to engage parsing for names.

An opt-in comment to get the behavior and incur the extra parsing cost seems reasonable.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list