News for hackers. Stuff that matters.

A comment on From 200K lines of CoffeeScript to zero: making decaffeinate super-stable. Parent comment

Re:From 200K lines of CoffeeScript to zero: making decaffein... by ddebernardy on Sunday January 07, 2018 @01:46AM (#16089649)
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.
[ Parent | on HN ]
Re:From 200K lines of CoffeeScript to zero: making decaffein... by teh_klev on Sunday January 07, 2018 @02:15AM (#16089723)
Would source maps not help in this case?

http://gunnariauvinen.com/using-source-maps-with-coffeescrip...

[ Parent | on HN ]
Re:From 200K lines of CoffeeScript to zero: making decaffein... by jononor on Sunday January 07, 2018 @07:15AM (#16090578)
Yup sourcemaps works fine for this, at least in browsers
[ Parent | on HN ]
Re:From 200K lines of CoffeeScript to zero: making decaffein... by DiThi on Sunday January 07, 2018 @10:04AM (#16091059)
It works with node --inspect as well.
[ Parent | on HN ]
Re:From 200K lines of CoffeeScript to zero: making decaffein... by partycoder on Sunday January 07, 2018 @09:54PM (#16094324)
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

[ Parent | on HN ]