Require Variable Declarations to be at the top of their scope (vars-on-top)
The vars-on-top
rule generates warnings when variable declarations are not used serially at the top of a function scope or the top of a program.
By default variable declarations are always moved (“hoisted”) invisibly to the top of their containing scope by the JavaScript interpreter.
This rule forces the programmer to represent that behaviour by manually moving the variable declaration to the top of its containing scope.
Rule Details
This rule aims to keep all variable declarations in the leading series of statements. Allowing multiple declarations helps promote maintainability and is thus allowed.
Examples
No variable declarations in a block.
// BAD
function doSomething() {
var first;
if (true) {
first = true;
}
var second; //not declared at the top
}
// GOOD
function doSomething() {
var first;
var second; //multiple declarations are allowed at the top
if (true) {
first = true;
}
}
No variable declarations in for initializer.
// BAD
function doSomething() {
for (var i=0; i<10; i++) {}
}
// GOOD
function doSomething() {
var i;
for (i=0; i<10; i++) {}
}
No variables after other statements.
// BAD
f();
var a;
// GOOD
var a;
f();
Directives may precede variable declarations.
// GOOD
"use strict";
var a;
f();
Comments can describe variables.
// GOOD
function doSomething() {
var first;
var second
}
// ALSO GOOD
function doSomething() {
// this is the first var.
var first;
// this is the second var.
var second
}
Further Reading
- JavaScript Scoping and Hoisting
- var Hoisting
- A criticism of the Single Var Pattern in JavaScript, and a simple alternative
- Multiple var statements in JavaScript, not superfluous
Version
This rule was introduced in ESLint 0.8.0.