Aurelio De Rosa - The Modern JavaScript Collection

Arrow functions were introduced with ES6 as a new syntax for writing JavaScript functions. They save developers time and simplify function scope. The good news is that many major modern browsers support the use of arrow functions.

This chapter will cover the details of arrow functions how to use them, common syntaxes, common use cases, and gotchas/pitfalls.

Arrow functions also called fat arrow functions, from CoffeeScript (a transcompiled language) are a more concise syntax for writing function expressions. They utilize a new token, =>, that looks like a fat arrow. Arrow functions are anonymous and change the way this binds in functions.

Arrow functions make our code more concise, and simplify function scoping and the this keyword. They are one-line mini functions which work much like Lambdas in other languages like C# or Python. (See also lambdas in JavaScript). By using arrow functions, we avoid having to type the function keyword, return keyword (its implicit in arrow functions), and curly brackets.

There are a variety of syntaxes available in arrow functions, of which MDN has a thorough list. Well cover the common ones here to get you started. Lets compare how ES5 code with function expressions can now be written in ES6 using arrow functions.

Code Example at JSBin.

The arrow function example above allows a developer to accomplish the same result with fewer lines of code and approximately half the typing.

Curly brackets arent required if only one expression is present. The preceding example could also be written as:

Parentheses are optional when only one parameter is present

Code Example at JSBin.

Parentheses are required when no parameters are present.

Code Example at JSBin.

Arrow functions, like function expressions, can be used to return an object literal expression. The only caveat is that the body needs to be wrapped in parentheses, in order to distinguish between a block and an object (both of which use curly brackets).

Code Example at JSBin.

Now that weve covered the basic syntaxes, lets get into how arrow functions are used.

One common use case for arrow functions is array manipulation and the like. Its common that youll need to map or reduce an array. Take this simple array of objects:

We could create an array of objects with just the names or prices by doing this in ES5:

An arrow function is more concise and easier to read:

Code Example at JSBin.

Heres another example using the array filter method:

Code Example at JSBin.

Code that makes use of asynchronous callbacks or promises often contains a great deal of function and return keywords. When using promises, these function expressions will be used for chaining. Heres a simple example of chaining promises from the MSDN docs:

This code is simplified, and arguably easier to read using arrow functions:

Arrow functions should similarly simplify callback-laden NodeJS code.

Whats the meaning of this?!

The other benefit of using arrow functions with promises/callbacks is that it reduces the confusion surrounding the this keyword. In code with multiple nested functions, it can be difficult to keep track of and remember to bind the correct this context. In ES5, you can use workarounds like the .bind method (which is slow) or creating a closure using var self = this;.

Because arrow functions allow you to retain the scope of the caller inside the function, you dont need to create self = this closures or use bind.

Developer Jack Franklin provides an excellent practical example of using the arrow function lexical this to simplify a promise:

Without Arrow functions, the promise code needs to be written something like this:

Using an arrow function, the same result can be achieved more concisely and clearly:

You can use function expressions if you need a dynamic this and arrow functions for a lexical this.

The new arrow functions bring a helpful function syntax to ECMAScript, but as with any new feature, they come with their own pitfalls and gotchas.

Kyle Simpson, a JavaScript developer and writer, felt there were enough pitfalls with Arrow Functions to warrant this flow chart when deciding to use them. He argues there are too many confusing rules/syntaxes with arrow functions. Others have suggested that using arrow functions saves typing but ultimately makes code more difficult to read. All those function and return statements might make it easier to read multiple nested functions or just function expressions in general.

Developer opinions vary on just about everything, including arrow functions. For the sake of brevity, here are a couple things you need to watch out for when using arrow functions.

As was mentioned previously, the this keyword works differently in arrow functions. The methods call(), apply(), and bind() will not change the value of