13

I've set up the coffeescript file watcher like in this video

http://www.youtube.com/watch?v=Sl1Uk3zT5Fg

Which seems to work fine for an html project debugging with google chrome. However, when I start debugging and set a breakpoint in the coffeescript file in a node.js project, it doesn't hit the breakpoint. Setting a breakpoint in the generated js file does however get hit.

What do I need to do for the debugger to use the generated source maps and step through the coffeescript with node.js in webstorm 6?

Improve this question
4
  • Good question! I am looking for this as well.
    – sky-dev
    Commented Mar 16, 2013 at 16:52
  • Follow this issue.
    – CrazyCoder
    Commented Mar 17, 2013 at 18:55
  • Hmm looks like the current workaround of moving the generated SourceMapping comment to the bottom of the file is cumbersome and unweildly
    – MonkeyBonkey
    Commented Mar 17, 2013 at 19:04
  • I have a similar question. stackoverflow.com/questions/14533885/…
    – sky-dev
    Commented Mar 18, 2013 at 0:33

2 Answers 2

Reset to default
4

The just released CoffeeScript 1.6.2 now has the annotation for the source map at the bottom as WebStorm expects so it now works as expected.

Improve this answer
2
+25

According to the issue that CrazyCoder mentioned, it looks like it is an issue with WebStorm expecting the //@ sourceMappingURL=print.map statement at the bottom of a generated JavaScript file rather than at the top which is where the coffeescript compiler currently puts it.

Manaually copying that line to the bottom of the generated script file on every save seems not a viable workaround so I think we'll have to watch that Webstorm issue until it is resolved.

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.