Canmove, confirm, emeritus
1,093
edits
Changes
no edit summary
{| class="fullwidth-table"|-{FeatureStatus| style="font-weight: bold; background: #DDD;" | Feature| stylename="font-weight: bold; background: #DDD;" | StatusSourceMap| styleFeature stage="font-weight: bold; background: #DDD;" | ETAPlanning| styleFeature status="font-weight: bold; background: #DDD;" | OwnerIn progress|-<section beginFeature health="status" />OK| [[DevTools/Features/SourceMap|Source Map]]}}| {{StatusHealthyFeatureTeam|statusFeature product manager=planning}}| 2011-06-01Kevin Dangoor| Feature feature manager=Kevin Dangoor<section end|Feature lead engineer="status" />Nick Fitzgerald}}|-{{FeaturePageBody|}Feature overview=Nearly every web developer starts with JavaScript in one form during development and then produces JavaScript in another form for production use. Most often, this is a case of joining files together and minifying the output to reduce the number of requests the browser needs to make and how much data the browser needs to transfer. Another example of JavaScript starting in one form and ending up in the final form used by the browser is in PHP scripts which will sometimes generate bits of JavaScript as they generate their pages.
When JavaScript gets an error, being able to help the web developer out by showing them where the error occurred in the original source file (PHP script or unminified, still-separate JavaScript for example) would save the developer time every single time they hit an error. The Web Console log messages also include links to the line that generated the log message, so these messages could link back to the original source lines as well.
For a long time, there have been [http://altjs.org/ languages that have compiled] to JavaScript, and recently there has been a surge in support for these languages led by [http://coffeescript.com/ CoffeeScript]. CoffeeScript may seem like a fringe language today, but it will soon be shipping with Ruby on Rails 3.1, giving thousands of programmers a reason for developing with something other than JS.
When developing an application in CoffeeScript, any time an error is hit the browser tells the user the location of the problem ''in the JavaScript file'', not the source file that the user is working with. [http://weepy.github.com/kaffeine/ One new language] even went so far as to ensure that the lines numbers in the generated JS match up with the lines numbers in the original source file, which is an unfortunate thing to optimize for.
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.
}}
{{FeatureInfo
|Feature priority=P2
|Feature roadmap=Developer Tools
|Feature list=Desktop
|Feature engineering team=DevTools
}}
{{FeatureTeamStatus
|Feature products status=tbd
|Feature engineering status=tbd
|Feature security status=tbd
|Feature privacy status=tbd
|Feature localization status=tbd
|Feature accessibility status=tbd
|Feature qa status=tbd
|Feature ux status=tbd
}}
== Summary ==
