4 ms·

Another pain is (was?) debugging. This might have changed since but back when I tried and rejected using it. But back then, if you had an error at line X it wou

Another pain is (was?) debugging. This might have changed since but back when I tried and rejected using it. But back then, if you had an error at line X it would report the (compiled) JavaScript line rather than the CoffeeScript line - meaning you'd need to figure out which CS code generated what line of JS code in order to hunt down and fix issues.

teh_klev 9y ago
Would source maps not help in this case? http://gunnariauvinen.com/using-source-maps-with-coffeescript/ http://gunnariauvinen.com/using-source-maps-with-coffeescrip...
- jononor 9y ago
  Yup sourcemaps works fine for this, at least in browsers
  - DiThi 9y ago
    It works with node --inspect as well.
    - partycoder 9y ago
      Most likely you will like to set a breakpoint at the entrypoint. You can do this with --inspect-brk rather than --inspect. Then you can see all debugging sessions in Chrome using chrome://inspect