One of the most widely used elements introduced in ES6 is the `let` variable initialization. Why is it better then `var`? Let's see. The main similarity is that var and let allow you to initialize a variable without assigning a value. Afterwards, you can update and change that value. value;

value = ;

value = ; .log(value); let 'string' 1 console // 1 And that's where the similarities end. 1. Block scope { ( i = ; i < ; i++) { value = i;
    } .log(value)
}

sayWhaaaat() ( ) function sayWhaaaat for var 0 4 var console // 3 What's going on above? We declare using `var` a variable called value. And we can access it outside the block! If you try you will be able to console.log the `i` as well. Initializing all variables using let will prevent similar issues as `let` is truly block scoped! When you replace the `var` with `let` and try to access it you will get `Uncaught ReferenceError: value is not defined`. Why is it important? you want variables to live only as long as it is required did you expect `value` to be accessible? No? Exactly! Code should be predictable to avoid bugs. 2. No repeated declaration { a = a = ; a;
}

repeatedDeclaration() ( ) function repeatedDeclaration var 'test' // some code var 'something else' return // 'something else' The above is a massive simplification, but I have seen functions 800 lines long, so by accident you can overwrite a variable. And if you do not write unit tests ( ) you might end up introducing a bug. Why writing unit tests is important If you use `let` you would get ` ` error. Uncaught SyntaxError: Identifier 'a' has already been declared 3. TDZ - temporal dead zone In ECMAScript 6, accessing a let or const variable before its declaration (within its scope) causes a ReferenceError. The time span when that happens, between the creation of a variable’s binding and its declaration, is called the . temporal dead zone https://2ality.com/2015/10/why-tdz.html Consider: .log(x); x = ; console // a ReferenceError let 'a string' The above code throws a Reference Error. It is an improvement as it is likely a bug to use a variable before it is defined. See code using `var`: .log(y) y = console // undefined var 'another string' Above we just get undefined, but is it helpful at all? After seeing the above examples one may presume that TDZ is related to using a variable before it is defined. But it is not entirely the case. Below example is from the book "JavaScript: The New Toys". { f = { .log(value);
    }; value = ;
    f();
}
temporalExample(); ( ) function temporalExample const => () console let 42 If you run it, you will get 42 logged. The `f` function even though references `value` doesn't use it until it gets called. The call happens after `value` is initialized. So you still can use a value before it is declared. The problem is not related to where a variable is placed in the code, but when it is used. Hope the above will help you writing better code and finally understand the most common use cases for using `let` instead of `const`. Enjoy!

Initialized

2022 - HackerNoon Contributor of the Year - Typescript

Nominated for 2022 - HackerNoon Contributor of the Year - Typescript

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

What I Wish Every Developer Knew About let In Javascript.

Too Long; Didn't Read

Company Mentioned

Mac Wasilewski

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

What I Wish Every Developer Knew About let In Javascript.

Too Long; Didn't Read

Company Mentioned

Mac Wasilewski

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES