CoffeeScript source maps

#1

Post by v33ra » Sat, Sep 08, 2012, 12:50 AM UTC

CoffeeScript source maps
ryanflorence.com

Re: CoffeeScript source maps

#2

Post by cedrichurst » Sat, Sep 08, 2012, 5:00 AM UTC

This is possibly the most important thing to happen to my frontend development workflow all year. Amazing contribution. Thank you.

Re: CoffeeScript source maps

#3

Post by mnemonik » Sat, Sep 08, 2012, 6:22 AM UTC

I just want to note that the new CoffeeScript compiler is using ESCodeGen as a backend, which is doing the source map heavy lifting. Anyone writing a compiler which targets JS can use ESCodeGen as a backend and get source maps pretty much for free. Awesome news all around!

https://github.com/Constellation/escodegen

Note: I do not want it to seem like I want to take anything away from Michael Ficarra and the new CoffeeScript compiler. He also wrote the code to integrate source maps with ESCodeGen, but it is something that many projects will be able to take advantage of, not just CoffeeScript.

In other source map news, if anyone hasn't seen it yet, UglifyJS v2 now supports source maps: http://lisperator.net/blog/uglifyjs-v2-news/

Source map support is on the way for Firefox's debugger as well: https://bugzilla.mozilla.org/show_bug.cgi?id=771597

Re: CoffeeScript source maps

#4

Post by danmaz74 » Sat, Sep 08, 2012, 7:35 AM UTC

I would LOVE to see source maps implemented into Rails CS compilation. Any idea how to do it/when will this be added to rails?

Re: CoffeeScript source maps

#5

Post by calibraxis » Sat, Sep 08, 2012, 10:55 AM UTC

Will this affect debugging under node.js, or just browsers? (Googling doesn't seem to make this clear.)

Re: CoffeeScript source maps

#6

Post by pwpwp » Sat, Sep 08, 2012, 11:02 AM UTC

As the article mentions, the next big step will be access to the debug console.

Re: CoffeeScript source maps

#7

Post by jeremiep » Sat, Sep 08, 2012, 1:12 PM UTC

calibraxis wrote: post #5

Will this affect debugging under node.js, or just browsers? (Googling doesn't seem to make this clear.)

I would assume both, if you use node-inspector to debug your programs you are using the browser's debugger.

Re: CoffeeScript source maps

#8

Post by calibraxis » Sat, Sep 08, 2012, 5:09 PM UTC

jeremiep wrote: post #7

calibraxis wrote: post #5

Will this affect debugging under node.js, or just browsers? (Googling doesn't seem to make this clear.)

I would assume both, if you use node-inspector to debug your programs you are using the browser's debugger.

Ah, I was just asking about stacktraces, if the line-numbers will then correspond to the CoffeeScript line-numbers.

It's no issue for me personally, but it helps smooth over resistance to CoffeeScript.

Re: CoffeeScript source maps

#9

Post by jarek-foksa » Sat, Sep 08, 2012, 6:54 PM UTC

Is CoffeeScriptRedux actually ready for production use? From my read of https://github.com/michaelficarra/CoffeeScriptRedux/wiki/Pro... there are many features missing.

Re: CoffeeScript source maps

#10

Post by michaelficarra » Sat, Sep 08, 2012, 9:35 PM UTC

jarek-foksa wrote: post #9

Is CoffeeScriptRedux actually ready for production use? From my read of https://github.com/michaelficarra/CoffeeScriptRedux/wiki/Pro... there are many features missing.

I would not recommend you use it in production just yet, but from my reading of that wiki page, there are only 3 or 4 fairly uncommon features that are unsupported. Most of them could still use more tests, though, and that's why they are missing that last checkmark.