This project is read-only.

Debugger Support

Topics: General
Oct 1, 2012 at 11:27 PM

Having used CoffeeScript a lot, JavaScript pre-processed languages can be challenging.  It would be great if you could add native debug support in VisualStudio and WebMatrix.

Oct 2, 2012 at 4:07 PM

+1. I think it's insane that in 2012, modern web development is stuck with second class debuggers; worse, with CoffeeScript (or TypeScript) we're not even debugging our source language.

Being able to debug TypeScript inside the powerful Visual Studio debugger would be a huge boon and a compelling argument towards language adoption.

Oct 2, 2012 at 4:37 PM

+1. I agree that it is not intuitive to have to set your breakpoints inside the generated javascript file(s) in order to get debugging to work from VS.

NodeJS and CoffeeScript have similar difficulties with setting breakpoints easily, and as everyone in this thread has already mentioned, this feature would go a long way toward separating TypeScript from the rest and driving adoption.

Oct 2, 2012 at 8:15 PM
Edited Oct 2, 2012 at 8:43 PM

+1. I would even accept "ugly" generated js code if debugging TypeScript is possible, because then I just don't have to look at the js code (like I don't want to see the IL code when writing/debugging c# applications). Just give me comfort and I'll trust you ms ;)

Oct 5, 2012 at 4:42 PM

I hear you.  We're actively working to improve the Visual Studio plugin (including with better debugging).  Thanks for the feedback!

Oct 5, 2012 at 7:26 PM

See this:

Guessing the blocker is that IE10 doesn't support source maps. Hope they get with the program.

Oct 18, 2012 at 9:20 AM

SourceMaps are the way to go and chrome devtools supports them very well. Generated JS code should be as clean and human readable as possible. Additionally you CAN set breakpoint in your TS code using the debugger statement.

Oct 18, 2012 at 3:04 PM

SourceMaps are indeed the way to go -- they're essentially .pdb for JS -- however, debugging in Chrome is not an ideal experience. Ideally, we could leverage the powerful debugging tools built into Visual Studio.