Is using ‘var’ to declare variables optional? [duplicate]

Is using ‘var’ to declare variables optional? [duplicate]

This question already has an answer here:

What is the purpose of the var keyword and when should I use it (or omit it)?

18 answers

Is “var” optional?
myObj = 1;

same as ?
var myObj = 1;

I found they both work from my test, I assume var is optional. Is that right?


Solution 1:

They mean different things.
If you use var the variable is declared within the scope you are in (e.g. of the function). If you don’t use var, the variable bubbles up through the layers of scope until it encounters a variable by the given name or the global object (window, if you are doing it in the browser), where it then attaches. It is then very similar to a global variable. However, it can still be deleted with delete (most likely by someone else’s code who also failed to use var). If you use var in the global scope, the variable is truly global and cannot be deleted.

This is, in my opinion, one of the most dangerous issues with javascript, and should be deprecated, or at least raise warnings over warnings. The reason is, it’s easy to forget var and have by accident a common variable name bound to the global object. This produces weird and difficult to debug behavior.

Solution 2:

This is one of the tricky parts of Javascript, but also one of its core features. A variable declared with var “begins its life” right where you declare it. If you leave out the var, it’s like you’re talking about a variable that you have used before.

var foo = 'first time use';
foo = 'second time use';

With regards to scope, it is not true that variables automatically become global. Rather, Javascript will traverse up the scope chain to see if you have used the variable before. If it finds an instance of a variable of the same name used before, it’ll use that and whatever scope it was declared in. If it doesn’t encounter the variable anywhere it’ll eventually hit the global object (window in a browser) and will attach the variable to it.

var foo = "I'm global";
var bar = "So am I";

function () {
    var foo = "I'm local, the previous 'foo' didn't notice a thing";
    var baz = "I'm local, too";

    function () {
        var foo = "I'm even more local, all three 'foos' have different values";
        baz = "I just changed 'baz' one scope higher, but it's still not global";
        bar = "I just changed the global 'bar' variable";
        xyz = "I just created a new global variable";

This behavior is really powerful when used with nested functions and callbacks. Learning about what functions are and how scope works is the most important thing in Javascript.

Solution 3:

Nope, they are not equivalent.

With myObj = 1; you are using a global variable.

The latter declaration create a variable local to the scope you are using.

Try the following code to understand the differences:

external = 5;
function firsttry() {
  var external = 6;
  alert("first Try: " + external);

function secondtry() {
  external = 7;
  alert("second Try: " + external);

alert(external); // Prints 5
firsttry(); // Prints 6
alert(external); // Prints 5
secondtry(); // Prints 7
alert(external); // Prints 7

The second function alters the value of the global variable “external”, but the first function doesn’t.

Solution 4:

There’s a bit more to it than just local vs global. Global variables created with var are different than those created without. Consider this:

var foo = 1; // declared properly
bar = 2; // implied global
window.baz = 3; // global via window object

Based on the answers so far, these global variables, foo, bar, and baz are all equivalent. This is not the case. Global variables made with var are (correctly) assigned the internal [[DontDelete]] property, such that they cannot be deleted.

delete foo; // false
delete bar; // true
delete baz; // true

foo; // 1
bar; // ReferenceError
baz; // ReferenceError

This is why you should always use var, even for global variables.

Solution 5:

There’s so much confusion around this subject, and none of the existing answers cover everything clearly and directly. Here are some examples with comments inline.

//this is a declaration
var foo;

//this is an assignment
bar = 3;

//this is a declaration and an assignment
var dual = 5;

A declaration sets a DontDelete flag. An assignment does not.

A declaration ties that variable to the current scope.

A variable assigned but not declared will look for a scope to attach itself to. That means it will traverse up the food-chain of scope until a variable with the same name is found. If none is found, it will be attached to the top-level scope (which is commonly referred to as global).

function example(){
  //is a member of the scope defined by the function example
  var foo;

  //this function is also part of the scope of the function example
  var bar = function(){
     foo = 12; // traverses scope and assigns to 12

function something_different(){
     foo = 15; // traverses scope and assigns to 15

For a very clear description of what is happening, this analysis of the delete function covers variable instantiation and assignment extensively.

Solution 6:

var is optional. var puts a variable in local scope. If a variable is defined without var, it is in global scope and not deletable.


I thought that the non-deletable part was true at some point in time with a certain environment. I must have dreamed it.