Course Overview

Overview of history of the JavaScript language

History of JavaScript

Overview of the relationship between JavaScript and Java

JavaScript vs Java

Overview of how JavaScript is evolved as a programming language

How is it evolved?

Overview of how we can track upcoming features in the JavaScript language

How to track upcoming features?

Overview of how the ECMAScript is versioned

How is ECMAScript versioned?

Explanation of whether JavaScript is interpreted or a compiled language

Is it interpreted or compiled?

Explanation of how JavaScript is executed

How is it executed?

Execution Context

Explanation of what is a callstack and how it is used in JavaScript

Callstack

Overview of memory management in JavaScript

Memory

What is JavaScript

What is hoisting?

Explanation of common misconception about hoisting in JavaScript

Misconception about hoisting

Hoisting

What is scope?

Explanation of global scope in JavaScript

Global scope

Explanation of function scope in JavaScript

Function scope

Block scope

Explanation of module scope in JavaScript

Module scope

Scope chain

Scope

What is coercion?

Diving into inner details of  coercion in JavaScript

Deeper look at coercion

Explanation of what abstract operations are and common types of abstract operations in JavaScript

Abstract operations

Explanation of how abstract or loose equality works in JavaScript

Abstract equality operator

Explanation of how the addition operator works in JavaScript

Addition operator

Explanation of how relational operators work in JavaScript

Relational operators

Coercion exercise for testing and practicing the knowledge learned in this module

Coercion exercise

Coercion

What is a closure?

Explanation of a common misconception about closures in JavaScript

Misconception about closures

Explanation of the problem of closures inside loops and how to fix it

Closures inside loops

Explanation of closures can be used to hide data

Data hiding using closures

Closures

What is prototypal inheritance?

Prototype chain

__proto__ property

Explanation of how we can create objects with custom prototypes in JavaScript

Custom prototypes

Explanation of how prototype chain is set with ES6 classes

ES6 classes and prototypes

Prototypes

Explanation of this keyword in JavaScript

What is this?

Explanation of how "this" works inside arrow functions

Arrow functions and "this"

Explanation of how value of "this" can be set explicitly

Explicitly binding "this"

globalThis

Summarizing "this"

'this' keyword

What is a symbol?

Explanation of why symbols were added in JavaScript

Why symbols?

Symbols and privacy

Explanation of global symbols in JavaScript

Global symbols

Explanation of what well-known symbols are in JavaScript

Well-known symbols

Symbol

Overview of asynchronous behavior of JavaScript

Overview

Overview of how callbacks help us write asynchronous code in JavaScript

Callbacks

Event loop

Promise

Explanation of promise chaining in JavaScript

Promise chaining

Explanation of some static methods of promises and their use cases

Use cases for static Promise methods

Explanation of async-await syntax in JavaScript

async await

Explanation of microtasks, how they are processed, and how they are linked to promises

Microtasks

Explanation of common anti-patterns to avoid when using promises in JavaScript

Promise anti-patterns

Asynchronous JavaScript

Explanation of what is an iterator in JavaScript

Iterators

Explanation of what is a generator in JavaScript

Generators

Explanation of how we can create asynchronous iterators in JavaScript

Asynchronous iterators

Explanation of how we can create asynchronous generators in JavaScript

Asynchronous generators

Iterators and Generators

Overview of what is debugging and different ways to debug JavaScript

Debugging

Overview of using the "debugger" statement to debug JavaScript

Debugger statement

Overview of using the breakpoints in browser developers' tools to debug JavaScript

Breakpoints in browser

Overview of using the VS Code debugger to debug JavaScript

VS Code debugger

Debugging JavaScript

Final thoughts and advice regarding how to continue the exciting journey of learning JavaScript

Conclusion

Wrap up

Enter your name and email address below, then click the **"Send my free chapter"** button to get started

300+ page PDF

EPub

newline Access with Replits

All Code Samples

Discord Community Access

One-time price of $69

Become a confident JavaScript pro by unraveling the most challenging aspects of the language. With easy-to-understand explanations and code examples, you’ll gain a deeper and solid understanding of JavaScript's most complex features.

Advanced JavaScript Unleashed is for beginner and intermediate developers alike, who want to elevate their JavaScript skills and become senior engineers by gaining a deeper understanding of the core topics of the language.

Advanced JavaScript Unleashed

The global scope is generally the outermost scope that contains all other scopes nested inside it. Each nested scope has access to the global scope. In JavaScript, the global scope is the browser window or, more accurately, a browser window tab. The global scope is exposed to the JavaScript code using the 

 keyword or function declarations declared in the global scope are added as properties on the 

 object. The following code example verifies this claim:

var todoList = ["grocery", "exercise", "meeting"];

function emptyTodoList() {
  todoList = [];
}

console.log(window.hasOwnProperty("todoList")); // true
console.log(window.hasOwnProperty("emptyTodoList")); // true

, it wouldn't have been added as a property on the 

 object, but it would still be a global variable. Similarly, if the 

 was a function expression instead of a function declaration, and if the identifier referring to this function expression was declared using 

 object as its property. Instead, it would just be a global function expression.

const todoList = ["grocery", "exercise", "meeting"];

let emptyTodoList = function () {
  todoList = [];
};

console.log(window.hasOwnProperty("todoList")); // false
console.log(window.hasOwnProperty("emptyTodoList")); // false

 - As a JavaScript developer, either you have already heard this advice, or sooner or later, you will hear it from someone. But what does "polluting" the global scope even mean? Why should it be avoided?

Declaring everything (unnecessarily) in the global scope is what's considered as "polluting" the global scope. Too many declarations in the global scope can lead to unwanted problems.

The global scope is the parent scope of all other scopes; as a result, the declarations inside the global scope are visible to all other scopes. This can cause problems like variable name clashes, shadowing, etc. Another thing about the global scope is that it isn't destroyed until the application is closed, so if we are not careful, declarations in the global scope can remain in memory regardless of whether they are needed or not until the application is closed.

Having said all that, declarations in the global scope are typically unavoidable. So, the best we can do is avoid the global scope as much as possible. Keep the global declarations to a minimum. If a variable is only used inside a function, there is no point in declaring it in the global scope.

So, if you hadn't heard it before, you are hearing it now: 

---
title: Global scope
description: Explanation of global scope in JavaScript
isPublicLesson: false
useMdx: true
code: https://gitlab.com/fullstackio/books/newline-course-apps/advanced-javascript-unleashed-app/-/tree/main/module_03/lesson_03.02/global-scope-example3
---

The global scope is generally the outermost scope that contains all other scopes nested inside it. Each nested scope has access to the global scope. In JavaScript, the global scope is the browser window or, more accurately, a browser window tab. The global scope is exposed to the JavaScript code using the `window` object.

Variables created using the `var` keyword or function declarations declared in the global scope are added as properties on the `window` object. The following code example verifies this claim:

```js
var todoList = ["grocery", "exercise", "meeting"];

function emptyTodoList() {
  todoList = [];
}

console.log(window.hasOwnProperty("todoList")); // true
console.log(window.hasOwnProperty("emptyTodoList")); // true
```

If the `todoList` was declared with `let` or `const`, it wouldn't have been added as a property on the `window` object, but it would still be a global variable. Similarly, if the `emptyTodoList` was a function expression instead of a function declaration, and if the identifier referring to this function expression was declared using `let` or `const`, it also wouldn't be part of the `window` object as its property. Instead, it would just be a global function expression.

```js showLineNumbers
const todoList = ["grocery", "exercise", "meeting"];

let emptyTodoList = function () {
  todoList = [];
};

console.log(window.hasOwnProperty("todoList")); // false
console.log(window.hasOwnProperty("emptyTodoList")); // false
```

## Avoid polluting the global scope

_"Avoid polluting the global scope"_ - As a JavaScript developer, either you have already heard this advice, or sooner or later, you will hear it from someone. But what does "polluting" the global scope even mean? Why should it be avoided?

Declaring everything (unnecessarily) in the global scope is what's considered as "polluting" the global scope. Too many declarations in the global scope can lead to unwanted problems.

The global scope is the parent scope of all other scopes; as a result, the declarations inside the global scope are visible to all other scopes. This can cause problems like variable name clashes, shadowing, etc. Another thing about the global scope is that it isn't destroyed until the application is closed, so if we are not careful, declarations in the global scope can remain in memory regardless of whether they are needed or not until the application is closed.