In the past I have used
var App = App || {};
to assign or instantiate a common App object in various js scripts loaded separately into the browser.
However, using let and const instead of var throws a reference error:
const App = App || {}; // or let App = App || {};
Uncaught ReferenceError: App is not defined
at <anonymous>:1:11
What's going on here? If I want to continue using this pattern, do I have to stick to var?
This is because when you are declaring a variable using let or a constant, the variable is in the temporal dead zone before being initialized.
In other words, trying let foo = foo will throw an error because foo is still in the temporal dead zone, and cannot be used. The same goes for const.
Note also that a variable defined whith let or a constant defined with const cannot share its name space in the same scope with another variable, be it with let, const, or var.
When javascript engine sees the statement, var App = App || {}, it breaks the statement down as follows:
var App;
App = App || {};
Due to variable hoisting, var App = App || {} is broken down into two parts.
var AppApp = App || {}The let and const declarations on the other hand, don't involve variable hoisting. Hence, the ReferenceError, as no variable called App exists yet.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With