I have found few tricks that makes writing CoffeeScript more efficient and fun, especially when learning it and I’d like to share it with you.
These tricks are for Vim, but the ideas can be carried out to other editors as well. I know that at least the TextMate CoffeeScript Bundle can do some of these.
Let’s get the basics out of way. Get syntax hilighting from vim-coffee-script plugin and automatic syntax checking from Syntastic. These will take you a long way, but with CoffeeScript we can do more.
Reading compiled code
Especially when starting out with CoffeeScript you are not always sure what the
snippet you are reading or even the code you just wrote does. Chances are that
vim-coffee-script makes that incredibly easy.
Lets take following snippet that might be confusing to CoffeeScript newbies:
vim-coffee-script you can just select the snippet in Visual Mode and type
:CoffeeCompile which will open up a new scratch buffer with a compiled
version of the snippet which will clearly tell what this syntax in CoffeeScript
means. You can use this to verify that you understood the CoffeeScript syntax
I recommend creating a shortcut for this. It’s so useful. Put this to your
This allows you to invoke the compiler with
Leader-key + c. The leader key is
backslash by default, but usually it is redefined to comma.
I don’t like manually compiling CoffeeScript files for my Node.js apps. Instead
I use the
coffee command directly or use plain js wrapper app that starts my
CoffeeScript apps. This is clean and simple, but can be painful when you get an
exception. There is a stack trace, but it refers to the compiled Javacript file
which does not exist! You could look up the original CoffeeScript file and try
to guess what line the stack trace means by looking variable names or manually
compile the file when exception occurs. Not so fun.
vim-coffee-script to the rescue!
When you execute the
CoffeeCompile Vim command in Command Mode you will get
the whole file compiled into the scratch buffer. In that you can scroll the
line referred by the stack trace and see what code exactly rose it. This is
bit clumsy since normally you can jump to a certain line by typing
We can do better! Put this to
And then try typing
:C<number>. Whoah! This takes you to the given line
Using it is just one character longer than normally jumping lines!