var functionName = function() {} vs function functionName() {}

Question

I've recently started maintaining someone else's JavaScript code. I'm fixing bugs, adding features and also trying to tidy up the code and make it more consistent.

The previous developer used two ways of declaring functions and I can't work out if there is a reason behind it or not.

The two ways are:

var functionOne = function() {     // Some code }; 

function functionTwo() {     // Some code } 

What are the reasons for using these two different methods and what are the pros and cons of each? Is there anything that can be done with one method that can't be done with the other?

Answer 1

The difference is that functionOne is a function expression and so only defined when that line is reached, whereas functionTwo is a function declaration and is defined as soon as its surrounding function or script is executed (due to hoisting).

For example, a function expression:

// TypeError: functionOne is not a function  functionOne();    var functionOne = function() {    console.log("Hello!");  };

And, a function declaration:

// Outputs: "Hello!"  functionTwo();    function functionTwo() {    console.log("Hello!");  }

Historically, function declarations defined within blocks were handled inconsistently between browsers. Strict mode (introduced in ES5) resolved this by scoping function declarations to their enclosing block.

'use strict';      { // note this block!    function functionThree() {      console.log("Hello!");    }  }  functionThree(); // ReferenceError