Generators: Common misconceptions and three good use cases

Generators have been all the rage lately. Many Node developers (including myself!) are excited and intrigued about writing their asynchronous code like this:

var a = yield doAsyncFn()
var b = yield doAyncFnThatDependsOnA(a)

However, this is just one use case (although a clever one) of using generators.

In this article, we will explore the strengths of using generators. There is a GitHub repository with the code samples we will go through that you can check out. You will also need Node 0.11.x or greater (with the —harmony flag) to run these examples. I personally use nvm for this.

What is a generator?

Generators are function executions that can be suspended and resumed at a later point; a lightweight coroutine. This behavior happens using special generator functions (noted by function* syntax) and a couple of new keywords (yield nd yield*) which are only used in the context of a generator:

function* generatorFn () {
  console.log('look ma I was suspended')
var generator = generatorFn() // [1]
setTimeout(function () { // [2]
}, 2000)
  1. A generator starts in a suspended state. No console output.
  2. By invoking next() on the generator, it will execute up until it hits the next yield keyword or returns. Now we have console output.

Generators also have a built-in communication channel with yield:

function* channel () {
  var name = yield 'hello, what is your name?' // [1]
  return 'well hi there ' + name
var gen = channel()
console.log( // hello, what is your name? [2]
console.log('billy')) // well hi there billy [3]
  1. The yield keyword must always yield some value (even if its null). When execution resumes, it can optionally receive a value with the use of
  2. The object returned from includes a value and a done property. The value property is the currently yielded (or returned) value from the generator. The done property is a Boolean indicating whether or not the generator has run to completion.
  3. We can send a value into the generator using The value is then assigned to name, in this example, as the generator resumes.

In addition to communicating values, you can also throw exceptions into generators with:

gen.throw(new Error("oh no"))

Generators may be used for iteration via the shiny new for of loop:

function* iter () {
 for (var i = 0; i < 10; i++) yield i
for (var val of iter()) {
 console.log(val) // outputs 1 — 9

What is yield* all about? The yield* keyword enables a generator function to yield to another generator function. This essentially gives control over to the other generator function until it has exhausted all of its yields and then it returns control to the originating generator. It should not be thought of as a way to do recursion with generators as I learned.

A common misconception

Now that I can suspend functions, I can run all this stuff in parallel right? No.JavaScript is still single-threaded, but now we have the ability to say STOP in the middle of a function.

If you are looking to bolster raw performance, generators may not be your ticket. Here’s a sample CPU intensive task, calculating a Fibonacci sequence number:

function fib (n) {
  var current = 0, next = 1, swap
  for (var i = 0; i < n; i++) {
    swap = current, current = next
    next = swap + next
  return current

Now, we write a similar function using generators:

function* fibGen (n) {
  var current = 0, next = 1, swap
  for (var i = 0; i < n; i++) {
    swap = current, current = nex
    next = swap + nex
    yield current

The functions are almost identical, the first returns the final result, the second yields each result up until the final result.

If we were to benchmark these two using Benchmark.js:

var suite = new (require('benchmark')).Suite
 .add('regular', function () {
 .add('generator', function () {
   for (var n of fibGen(20));
 .on('complete', function () {
   this.forEach(function (result) {
     console.log(, result.count)

The results are pretty plain to see (higher is better). Generators aren’t doing anything magical for us here and there is a performance overhead:

regular 1263899
generator 37541

Of course this is a trivial example, and performance will likely get better. You may find performance benefits using some of the upcoming examples, but generators are still not a magic bullet. You don’t divvy work up, you simply suspend it. Performance tends to be slightly slower using generators for asynchronous tasks, but they come with substantial benefits as we’ll see in a moment.

Where generators shine

Generators enable functionality that was either not possible before in JavaScript or was complicated. I find these cases the most compelling.

Lazy evaluation

Lazy evaluation is already possible with JavaScript using closure tricks and the like, but its greatly simplified now with yield. By suspending execution and resuming at will, we are able to pull values only when we need to. For instance, our above fibGen function was not fast per say but it was lazy. We pull new values whenever we ask for them.

var fibIter = fibGen(20)
var next =

setTimeout(function () {
 var next =

Of course, if we want one after another, using a for of loop is more convenient and is still lazily evaluated:

for (var n of fibGen(20)) {

Infinite sequences

Since we can be lazy, it is possible to pull some Haskell tricks, like infinite sequences. Here is a Fibonacci generator that is able to yield an infinite amount of sequence numbers:

function* fibGen () {
  var current = 0, next = 1, swap
  while (true) {
    swap = current, current = next
    next = swap + next
    yield current

Now we evaluate a Fibonacci stream lazily, asking it to return the first Fibonacci number after 5000:

for (var num of fibGen()) {
 if (num > 5000) break
console.log(num) // 6765

That’s pretty cool.

Asynchronous control flow

Using generators for asynchronous control flow was first introduced by task.js (which no longer appears to exist) and popularized by frameworks like co and various promise libraries. But how to does it actually work?

In Node land, everything is set up to work with callbacks. It is our lowest-level asynchronous abstraction. However, callbacks don’t work well with generators but yield will. If we invert how we have been using generators and use the built-in communications channel, we can write synchronous looking asynchronous code!

run(function* () {
  var file = yield readFile("./async.js") // [1]
  1. Wait for the result of async.js to come back before continuing.

How do we do this? First, we need to convert asynchronous Node-style callback functions into thunks, a subroutine value we can reference until its ready to be executed:

function thunkify (nodefn) { // [1]
  return function () { // [2]
    var args =
    return function (cb) { // [3]
      nodefn.apply(this, args)
  1. Take an existing Node callback style function as input.
  2. Return a function that converts Node-style into a thunk-style.
  3. Enable the asynchronous function to be execute independently from its initial setup by delaying the execution until its returned function is called.

If you are having trouble wrapping your head around this function, this is how it works if you were to break out the pieces:

var fs = require('fs')
var readFile = thunkify(fs.readFile) // [1]
var readAsyncJs = readFile('./async.js') // [2]
readAsyncJs(function (er, buf) { ... }) // [3]
  1. Turn fs.readFile into a thunk-style function.
  2. Setup readFile to read async.js using the same fs.readFile API without passing the callback argument. No asynchronous operation is performed yet.
  3. Perform the asynchronous operation and callback.

Now, let’s write a run function, which takes a generator function and handles any yielded thunks:

function run (genFn) {
  var gen = genFn() // [1]
  next() // [2]

  function next (er, value) { // [3]
    if (er) return gen.throw(er)
    var continuable =

    if (continuable.done) return // [4]
    var cbFn = continuable.value // [5]
  1. Immediately invoke the generator function. This returns a generator in a suspended state.
  2. Then, invoke the next function. We call it right away to tell the generator to resume execution (since next triggers
  3. Notice how next looks just like the Node callback signature (er, value). Every time a thunk completes its asynchronous operation we will call this function.
  4. If there was an error from the asynchronous operation, throw the error back into the generator to be handled there.
  5. If successful, send the value back to the generator. This value gets returned from the yield call.
  6. If we have no more left to do in our generator, then stop by returning early.
  7. If we have more to do, take the value of the next yield and execute it using our next as the callback.

Now we can run our code and handle errors in a synchronous fashion!

var fs = require('fs')
var readFile = thunkify(fs.readFile)

run(function* () {
  try {
    var file = yield readFile('./async.js')
  catch (er) {


Generators are fun to play around with and I’m excited to see what other use cases we find for them. I would encourage you to play around with the GitHub repo. If there are other compelling use cases I didn’t mention, please let me know!

This article originally was published on the Strongloop blog.

What do you think? Submit a change/correction.

Up next:

Marc is the co-author of Node.js in Action and Node.js in Practice. He enjoys learning and writes technical stuff here and for IBM. Currently plays around with Go, TypeScript and Rust. Works as a full-stack engineer for @applieddataconsultants.