Can't get coffeescript working with WebStorm 4.0.3

I've downloaded the most recent update and coffeescript support appears to be broken.

See the screenshots:
Screen Shot 2012-07-09 at 8.24.01 PM.png

Screen Shot 2012-07-09 at 8.24.24 PM.png

Screen Shot 2012-07-09 at 8.24.43 PM.png

Either I'm missing something obvious or there is something fundamental broken.

Both Node and Coffeescript plugins are enabled.  I do have node and coffeescript installed on the machine.

It's OSX 10.7.4

The weird part is that after I configure it, it seems to lose the path to the coffee executable.

Any ideas?

8 comments
Comment actions Permalink

Hello Gary,

If you open Run Configuration again would you see field "path to coffee executable" filled correctly? Looks like WS loses path to coffee.


Thank you.

0
Comment actions Permalink

The path to coffeescript executable is as in the first screenshot above.

IE, yes it appears to be lost between invocations.

0
Comment actions Permalink

Try to reinstall plugin NodeJS.

In "Settings" windows open tab "Plugins", open context menu on "NodeJS" plugin and click Uninstall. Restart the IDE and install "NodeJS" plugin.

0
Comment actions Permalink

I don't get the option to 'uninstall' NodeJS

See screenshotCantUninstall.png

0
Comment actions Permalink

Hello Gary,

I've reproduced the problem. We are fixing it now.

And as workaround you could specify path to coffee in the default NodeJS run configuration.

0
Comment actions Permalink

That's great news, thank you.

If you have the time could you show me where to "specify path to coffee in the default NodeJS run configuration"

Thank you

Gary

0
Comment actions Permalink

Hello, you should open Run Configuration dialog, expand node "Defaults", select node "NodeJS" check "Run with CoffeeScript" checkbox and fill "Path to coffee executable" then uncheck "Run with CoffeeScript" checkbox and press "Ok".

Then each new created Run Configuration for CoffeeScript file would have got filled "path to Coffee executable" attribute.

0
Comment actions Permalink

That's great thank you :)

I'm from a .NET background so tweaking the tooling isn't something I'm familiar with...  You've been very helfpull :)

(If something doesn't work in VS you're generally screwed until a patch comes out from microsoft).

Gary

0

Please sign in to leave a comment.