BT

Mozilla, WebKit To Support Debugging Minified JS As Well As CoffeeScript and other JS Languages

by Werner Schuster on Aug 08, 2011 |

Modern Web and Javascript debuggers are powerful and well integrated into the browsers - but only if the code in the debugger is plain, hand written Javascript. Nowadays, a lot of executed and deployed Javascript is generated by software, not developers. The most common case is minified or otherwise compressed code. Setting a breakpoint in one of those files is tricky or impossible as they tend to be single lines - even if the original source was well formatted.

Another problem: Javascript is gaining popularity as compiler target for languages, mainly due to the ubiquity of Javascript VMs. CoffeeScript is just one example of a new language, the recently introduced ClojureScript is an example of an established language, compiling to Javascript. Debugging code written in these languages means using the generated Javascript code, not the input language for setting breakpoints, console.log() messages and other source related functionality.

The problem's not new; JVM languages had the problem too, which led to JSR-045 - Debugging Support for Other Languages, which is used for various languages compiling to the JVM, like JRuby.

Source Maps (SMAPs) are the solution, ie. files that map between the source language and the target representation. Google's Closure compiler can generate SMAP files for it's minified Javascript files, although currently the only tool that can read the SMAP files is the Closure Inspector, a Firebug extension.

Both the Mozilla and the WebKit projects have started work on supporting SMAPs in their debugging features.

Mozilla has an in-depth planning document for the SMAP and debugging functionality. The document also mentions yet another potential area for source mapping: CSS, which is also used as compilation target by supersets of CSS such as SASS or LESS.
The Mozilla ticket tracking the work is Bug 618650 - Map JS source coordinates to source language that was translated to JS; the planning document lists Firefox 9 as target release.

WebKit is also planning SMAP support, and the actual SMAP format might be an evolved version of the Closure Inspector format, which is considered by Mozilla as well. Bug 63940 - Web Inspector: draft implementation of compiler source mappings support in debugger tracks the development of the feature.

Hello stranger!

You need to Register an InfoQ account or to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

"Firefox 9"??? by Jeffrey 'jf' Lim

hi, where is your source for the supposed "Firefox 9" target release? could u link to it? (oh, and uh... get rid of the spam here?)

Re: Firefox 9 by Kevin Dangoor

The Firefox 9 reference is in the planning document linked to in the text. Firefox 9 is due to go to Aurora at the end of September and be released in December.

Re: Firefox 9 by Jeffrey 'jf' Lim

thanks, Kevin! I guess i missed that among the plethora of links in there...

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

3 Discuss

Educational Content

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2013 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT