JavaScript Use Strict


 "use strict";  Defines that JavaScript code should be executed in "strict mode".


The "use strict" Directive

The "use strict" directive is new in JavaScript 1.8.5 (ECMAScript version 5).

It is not a statement, but a literal expression, ignored by earlier versions of JavaScript.

The purpose of "use strict" is to indicate that the code should be executed in "strict mode".

With strict mode, you can not, for example, use undeclared variables.

Note Strict mode is supported in:
Internet Explorer from version 10. Firefox from version 4.
Chrome from version 13. Safari from version 5.1. Opera from version 12.


Declaring Strict Mode

Strict mode is declared by adding "use strict"; to the beginning of a JavaScript file, or a JavaScript function.

Declared at the beginning of a JavaScript file, it has global scope (all code will execute in strict mode).

Declared inside a function, it has local scope (only the code inside the function is in strict mode).

Global declaration:

"use strict";
x = 3.14;       // This will cause an error
myFunction();   // This will also cause an error

function myFunction() {
    x = 3.14;
}

Try it Yourself »

Local declaration:

x = 3.14;       // This will not cause an error.
myFunction();   // This will cause an error

function myFunction() {
   "use strict";
    x = 3.14;
}

Try it Yourself »


The "use strict"; Syntax

The syntax, for declaring strict mode, was designed to be compatible with older versions of JavaScript.

Compiling a numeric literal (4 + 5;) or a string literal ("John Doe";) in a JavaScript program has no side effects. It simply compiles to a non existing variable and dies.

So "use strict;" only matters to new compilers that "understand" the meaning of it.


Why Strict Mode?

Strict mode makes it easier to write "secure" JavaScript.

Strict mode changes previously accepted "bad syntax" into real errors.

As an example, in normal JavaScript, mistyping a variable name creates a new global variable. In strict mode, this will throw an error, making it impossible to accidentally create a global variable.

In normal JavaScript, a developer will not receive any error feedback assigning values to non-writable properties.

In strict mode, any assignment to a non-writable property, a getter-only property, a non-existing property, a non-existing variable, or a non-existing object, will throw an error.


Not Allowed in Strict Mode

Using a variable (property or object) without declaring it, is not allowed:

"use strict";
x = 3.14;                 // This will cause an error (if x has not been declared)

Deleting a variable, a function, or an argument, is not allowed.

"use strict";
x = 3.14;
delete x;                 // This will cause an error

Defining a property more than once, is not allowed:

"use strict";
var x = {p1:10, p1:20};   // This will cause an error

Duplicating a parameter name is not allowed:

"use strict";
function x(p1, p1) {};    // This will cause an error

Octal numeric literals and escape characters are not allowed:

"use strict";
var x = 010;             // This will cause an error
var y = \010;            // This will cause an error

Writing to a read-only property is not allowed:

"use strict";
var obj = {};
obj.defineProperty(obj, "x", {value:0, writable:false});

obj.x = 3.14;            // This will cause an error

Writing to a get-only property is not allowed:

"use strict";
var obj = {get x() {return 0} };

obj.x = 3.14;            // This will cause an error

Deleting an undeletable property is not allowed:

"use strict";
delete Object.prototype; // This will cause an error

The string "eval" cannot be used as a variable:

"use strict";
var eval = 3.14;         // This will cause an error

The string "arguments" cannot be used as a variable:

"use strict";
var arguments = 3.14;    // This will cause an error

The with statement is not allowed:

"use strict";
with (Math){x = cos(2)}; // This will cause an error

For security reasons, eval() are not allowed to create variables in the scope from which it was called:

"use strict";
eval ("var x = 2");
alert (x)                // This will cause an error

In function calls like f(), the this value was the global object. In strict mode, it is now undefined.

Future reserved keywords are not allowed. These are:

  • implements
  • interface
  • package
  • private
  • protected
  • public
  • static
  • yield

Watch Out!

Note The "use strict" directive is only recognized at the beginning of a script or a function.



Color Picker

colorpicker