_☕ CoffeeScript

CoffeeScript is a little language that compiles into JavaScript. Think of it as JavaScript's less ostentatious kid brother — the same genes, roughly the same height, but a different sense of style. Apart from a handful of bonus goodies, statements in CoffeeScript correspond one-to-one with their equivalent in JavaScript, it's just another way of saying it.

Disclaimer: CoffeeScript is just for fun and seriously alpha. I'm sure that there are still plenty of holes in the walls and leaks in the roof. There are no guarantees that the syntax won't change between versions. That said, it compiles into clean JavaScript (the good parts) that can use existing JavaScript libraries seamlessly, and passes through JSLint without warnings. The compiled output is quite readable — pretty-printed, with comments preserved intact.

Latest Version: 0.3.2

Table of Contents

Mini Overview
Installation and Usage
Try CoffeeScript
Significant Whitespace
Functions and Invocation
Assignment
Objects and Arrays
Lexical Scoping and Variable Safety
Conditionals, Ternaries, and Conditional Assignment
Aliases
Splats...
Arguments are Arrays
While Loops
Comprehensions (Arrays, Objects, and Ranges)
Array Slicing and Splicing with Ranges
Everything is an Expression
The Existential Operator
Inheritance, and Calling Super from a Subclass
Pattern Matching
Function Binding
Embedded JavaScript
Switch/When/Else
Try/Catch/Finally
Chained Comparisons
Multiline Strings and Heredocs
Resources
Change Log

Mini Overview

CoffeeScript on the left, compiled JavaScript output on the right.

For a longer CoffeeScript example, check out Underscore.coffee, a port of the Underscore.js library of helper functions. Underscore.coffee can pass the entire Underscore.js test suite. The CoffeeScript version is faster than the original for a number of methods (in general, due to the speed of CoffeeScript's array comprehensions), and after being minified and gzipped, is only 241 bytes larger than the original JavaScript version. Additional examples are included in the source repository, inside the examples folder.

Installation and Usage

The CoffeeScript compiler is written in pure Ruby, and is available as a Ruby Gem.

gem install coffee-script

Installing the gem provides the coffee command, which can be used to compile CoffeeScript .coffee files into JavaScript, as well as debug them. In conjunction with Node.js (or Narwhal), the coffee command also provides direct evaluation and an interactive REPL. When compiling to JavaScript, coffee writes the output as .js files in the same directory by default, but output can be customized with the following options:

Examples:

coffee path/to/script.coffee
coffee --interactive
coffee --watch --lint experimental.coffee
coffee --print app/scripts/*.coffee > concatenation.js

Try CoffeeScript

Here's a live version of the CoffeeScript compiler, running within your browser.
Hit the compile button to generate JavaScript on the right-hand side. You can also paste in any of the examples from below.

Language Reference

This reference is structured so that it can be read from top to bottom, if you like. Later sections use ideas and syntax previously introduced. Familiarity with JavaScript is assumed. In all of the following examples, the source CoffeeScript is provided on the left, and the direct compilation into JavaScript is on the right.

Significant Whitespace CoffeeScript uses Python-style significant whitespace: You don't need to use semicolons ; to terminate expressions, ending the line will do just as well. Semicolons can still be used to fit multiple expressions onto a single line. Instead of using curly braces { } to delimit blocks of code (like functions, if-statements, switch, and try/catch), use indentation.

You don't need to use parentheses to invoke a function, if you're passing arguments:
print "coffee"

You can use newlines to break up your expression into smaller pieces, as long as CoffeeScript can determine that the line hasn't finished yet.

Functions and Invocation Functions are defined by a list of parameters, an arrow, and the function body. The empty function looks like this: ->. All functions in CoffeeScript are named by default, for easier debugging.

If you'd like to create an anonymous function, just wrap it in parentheses: ((x) -> x * x)

Assignment Use a colon : to assign, as in JSON. Equal signs are only needed for mathy things. While colons are preferred, the two may be used interchangeably, even within object literals.

Declaration of new variables are pushed up to the top of the nearest lexical scope, so that assignment may always be performed within expressions.

Objects and Arrays Object and Array literals look very similar to their JavaScript cousins. When you spread out each assignment on a separate line, the commas are optional. In this way, assigning object properties looks the same as assigning local variables, and can be moved around freely. Feel free to mix and match the two styles.

Lexical Scoping and Variable Safety The CoffeeScript compiler takes care to make sure that all of your variables are properly declared within lexical scope — you never need to write var yourself.

Notice how the all of the variable declarations have been pushed up to the top of the closest scope, the first time they appear. num is not redeclared within the inner function, because it's already in scope; the new_num within the function, on the other hand, should not be able to change the value of the external variable of the same name, and therefore has a declaration of its own.

Although suppressed within this documentation for clarity, all CoffeeScript output is wrapped in an anonymous function: (function(){ ... })(); This safety wrapper, combined with the automatic generation of the var keyword, make it exceedingly difficult to pollute the global namespace by accident.

If you'd like to create top-level variables for other scripts to use, attach them as properties on window, or on the exports object in CommonJS. The existential operator (below), gives you a reliable way to figure out where to add them, if you're targeting both CommonJS and the browser: root: exports ? this

Conditionals, Ternaries, and Conditional Assignment If/else statements can be written without the use of parentheses and curly brackets. As with functions and other block expressions, multi-line conditionals are delimited by indentation. There's also a handy postfix form, with the if or unless at the end.

CoffeeScript will compile if statements using the ternary operator when possible, to make it easier to use the result as an expression.

The conditional assignment operators are included: ||=, which only assigns a value to a variable if the variable's current value is falsy, and &&=, which only replaces the value of truthy variables.

Aliases Because the == operator frequently causes undesirable coercion, is intransitive, and has a different meaning than in other languages, CoffeeScript compiles == into ===, and != into !==. In addition, is compiles into ===, and isnt into !==.

You can use not as an alias for !.

For logic, and compiles to &&, and or into ||.

Instead of a newline or semicolon, then can be used to separate conditions from expressions, in while, if/else, and switch/when statements.

As in YAML, on and yes are the same as boolean true, while off and no are boolean false.

For single-line statements, unless can be used as the inverse of if.

As a shortcut for this.property, you can use @property.

Splats... The JavaScript arguments object is a useful way to work with functions that accept variable numbers of arguments. CoffeeScript provides splats ..., both for function definition as well as invocation, making variable numbers of arguments a little bit more palatable.

Arguments are Arrays If you reference the arguments object directly, it will be converted into a real Array, making all of the Array methods available.

While Loops The only low-level loop that CoffeeScript provides is the while loop. The main difference from JavaScript is that the while loop can be used as an expression, returning an array containing the result of each iteration through the loop.

Other JavaScript loops, such as for loops and do-while loops can be mimicked by variations on while, but the hope is that you won't need to do that with CoffeeScript, either because you're using each (forEach) style iterators, or...

Comprehensions (Arrays, Objects, and Ranges) For your looping needs, CoffeeScript provides array comprehensions similar to Python's. They replace (and compile into) for loops, with optional guard clauses and the value of the current array index. Unlike for loops, array comprehensions are expressions, and can be returned and assigned. They should be able to handle most places where you otherwise would use a loop, each/forEach, map, or select/filter.

If you know the start and end of your loop, or would like to step through in fixed-size increments, you can use a range to specify the start and end of your comprehension. (The long line-breaking "for" definitions in the compiled JS below allow ranges to count downwards, as well as upwards).

Comprehensions can also be used to iterate over the keys and values in an object. Use of to signal comprehension over the properties of an object instead of the values in an array.

Array Slicing and Splicing with Ranges CoffeeScript borrows Ruby's range syntax for extracting slices of arrays. With two dots (3..5), the range is inclusive: the first argument is the index of the first element in the slice, and the second is the index of the last one. Three dots signify a range that excludes the end.

The same syntax can be used with assignment to replace a segment of an array with new values (to splice it).

Everything is an Expression (at least, as much as possible) You might have noticed how even though we don't add return statements to CoffeeScript functions, they nonetheless return their final value. The CoffeeScript compiler tries to make sure that all statements in the language can be used as expressions. Watch how the return gets pushed down into each possible branch of execution, in the function below.

Even though functions will always return their final value, it's both possible and encouraged to return early from a function body writing out the explicit return (return value), when you know that you're done.

Because variable declarations occur at the top of scope, assignment can be used within expressions, even for variables that haven't been seen before:

Things that would otherwise be statements in JavaScript, when used as part of an expression in CoffeeScript, are converted into expressions by wrapping them in a closure. This lets you do useful things, like assign the result of a comprehension to a variable:

As well as silly things, like passing a try/catch statement directly into a function call:

There are a handful of statements in JavaScript that can't be meaningfully converted into expressions, namely break, continue, and return. If you make use of them within a block of code, CoffeeScript won't try to perform the conversion.

The Existential Operator It's a little difficult to check for the existence of a variable in JavaScript. if (variable) ... comes close, but fails for zero, the empty string, and false. CoffeeScript's existential operator ? returns true unless a variable is null or undefined, which makes it analogous to Ruby's nil?

It can also be used for safer conditional assignment than ||= provides, for cases where you may be handling numbers or strings.

The accessor variant of the existential operator ?. can be used to soak up null references in a chain of properties. Use it instead of the dot accessor . in cases where the base value may be null or undefined. If all of the properties exist then you'll get the expected result, if the chain is broken, undefined is returned instead of the TypeError that would be raised otherwise.

Soaking up nulls is similar to Ruby's andand gem, and to the safe navigation operator in Groovy.

Inheritance, and Calling Super from a Subclass JavaScript's prototypal inheritance has always been a bit of a brain-bender, with a whole family tree of libraries that provide a cleaner syntax for classical inheritance on top of JavaScript's prototypes: Base2, Prototype.js, JS.Class, etc. The libraries provide syntactic sugar, but the built-in inheritance would be completely usable if it weren't for a couple of small exceptions: it's awkward to call super (the prototype object's implementation of the current function), and it's awkward to correctly set the prototype chain.

CoffeeScript provides extends to help with prototype setup, :: for quick access to an object's prototype, and converts super() into a call against the immediate ancestor's method of the same name.

Pattern Matching (Destructuring Assignment) To make extracting values from complex arrays and objects more convenient, CoffeeScript implements ECMAScript Harmony's proposed destructuring assignment syntax. When you assign an array or object literal to a value, CoffeeScript breaks up and matches both sides against each other, assigning the values on the right to the variables on the left. In the simplest case, it can be used for parallel assignment:

But it's also helpful for dealing with functions that return multiple values.

Pattern matching can be used with any depth of array and object nesting, to help pull out deeply nested properties.

Function binding The fat arrow => can be used to both define a function, and to bind it to the current value of this, right on the spot. This is helpful when using callback-based libraries like Prototype or jQuery, for creating iterator functions to pass to each, or event-handler functions to use with bind. Functions created with the fat arrow are able to access properties of the this where they're defined.

Embedded JavaScript Hopefully, you'll never need to use it, but if you ever need to intersperse snippets of JavaScript within your CoffeeScript, you can use backticks to pass it straight through.

Switch/When/Else Switch statements in JavaScript are rather broken. You can only do comparisons based on string equality, and need to remember to break at the end of every case statement to avoid accidentally falling through to the default case. CoffeeScript compiles switch statements into JavaScript if-else chains, allowing you to compare any object (via ===), preventing fall-through, and resulting in a returnable, assignable expression. The format is: switch condition, when clauses, else the default case.

As in Ruby, switch statements in CoffeeScript can take multiple values for each when clause. If any of the values match, the clause runs.

Try/Catch/Finally Try/catch statements are just about the same as JavaScript (although they work as expressions).

Chained Comparisons CoffeeScript borrows chained comparisons from Python — making it easy to test if a value falls within a certain range.

Multiline Strings and Heredocs Multiline strings are allowed in CoffeeScript.

Heredocs can be used to hold formatted or indentation-sensitive text (or, if you just don't feel like escaping quotes and apostrophes). The indentation level that begins the heredoc is maintained throughout, so you can keep it all aligned with the body of your code.

Resources

• Source Code
  Use bin/coffee to test your changes, rake test to run the test suite, rake build:parser to regenerate the Racc parser if you're working on the grammar, and rake gem:install to create and install a custom version of the gem.
• CoffeeScript Issues
  Bugs reports, feature requests, and general discussion all belong here.
• If you'd like to chat, stop by #coffeescript on Freenode.
• rack-coffee
  Rack middleware for serving CoffeeScripts as JavaScript directly to the browser, without having to compile them first. From Matt Lyon.
• BistroCar
  A Rails plugin by Jonas Nicklas that includes CoffeeScript helpers, bundling and minification.
• coffee-haml-filter
  A custom HAML filter, by Ivan Nemytchenko, that embeds snippets of CoffeeScript within your HAML templates.

Change Log

0.3.2 @property is now a shorthand for this.property.
Switched the default JavaScript engine from Narwhal to Node.js. Pass the --narwhal flag if you'd like to continue using it.

0.3.0 CoffeeScript 0.3 includes major syntax changes:
The function symbol was changed to ->, and the bound function symbol is now =>.
Parameter lists in function definitions must now be wrapped in parentheses.
Added property soaking, with the ?. operator.
Made parentheses optional, when invoking functions with arguments.
Removed the obsolete block literal syntax.

0.2.6 Added Python-style chained comparisons, the conditional existence operator ?=, and some examples from Beautiful Code. Bugfixes relating to statement-to-expression conversion, arguments-to-array conversion, and the TextMate syntax highlighter.

0.2.5 The conditions in switch statements can now take multiple values at once — If any of them are true, the case will run. Added the long arrow ==>, which defines and immediately binds a function to this. While loops can now be used as expressions, in the same way that comprehensions can. Splats can be used within pattern matches to soak up the rest of an array.

0.2.4 Added ECMAScript Harmony style destructuring assignment, for dealing with extracting values from nested arrays and objects. Added indentation-sensitive heredocs for nicely formatted strings or chunks of code.

0.2.3 Axed the unsatisfactory ino keyword, replacing it with of for object comprehensions. They now look like: for prop, value of object.

0.2.2 When performing a comprehension over an object, use ino, instead of in, which helps us generate smaller, more efficient code at compile time.
Added :: as a shorthand for saying .prototype.
The "splat" symbol has been changed from a prefix asterisk *, to a postfix ellipsis ...
Added JavaScript's in operator, empty return statements, and empty while loops.
Constructor functions that start with capital letters now include a safety check to make sure that the new instance of the object is returned.
The extends keyword now functions identically to goog.inherits in Google's Closure Library.

0.2.1 Arguments objects are now converted into real arrays when referenced.

0.2.0 Major release. Significant whitespace. Better statement-to-expression conversion. Splats. Splice literals. Object comprehensions. Blocks. The existential operator. Many thanks to all the folks who posted issues, with special thanks to Liam O'Connor-Davis for whitespace and expression help.

0.1.6 Bugfix for running coffee --interactive and --run from outside of the CoffeeScript directory. Bugfix for nested function/if-statements.

0.1.5 Array slice literals and array comprehensions can now both take Ruby-style ranges to specify the start and end. JavaScript variable declaration is now pushed up to the top of the scope, making all assignment statements into expressions. You can use \ to escape newlines. The coffee-script command is now called coffee.

0.1.4 The official CoffeeScript extension is now .coffee instead of .cs, which properly belongs to C#. Due to popular demand, you can now also use = to assign. Unlike JavaScript, = can also be used within object literals, interchangeably with :. Made a grammatical fix for chained function calls like func(1)(2)(3)(4). Inheritance and super no longer use __proto__, so they should be IE-compatible now.

0.1.3 The coffee command now includes --interactive, which launches an interactive CoffeeScript session, and --run, which directly compiles and executes a script. Both options depend on a working installation of Narwhal. The aint keyword has been replaced by isnt, which goes together a little smoother with is. Quoted strings are now allowed as identifiers within object literals: eg. {"5+5": 10}. All assignment operators now use a colon: +:, -:, *:, etc.

0.1.2 Fixed a bug with calling super() through more than one level of inheritance, with the re-addition of the extends keyword. Added experimental Narwhal support (as a Tusk package), contributed by Tom Robinson, including bin/cs as a CoffeeScript REPL and interpreter. New --no-wrap option to suppress the safety function wrapper.

0.1.1 Added instanceof and typeof as operators.

0.1.0 Initial CoffeeScript release.