Course contentsShow
← JavaScript
Lesson 1465 of 2,72332. JavaScript in the BrowserFree lesson

Implicit Global Access

How undeclared variables become global properties and why this is dangerous in non-strict mode.

Implicit Global Access

You'll learn how forgetting to declare a variable can accidentally create a global property—and why that's a silent disaster waiting to happen.

What Is Implicit Global Access?

In JavaScript (when not using strict mode), if you assign a value to a variable that hasn't been declared with var, let, or const, JavaScript doesn't throw an error. Instead, it automatically creates a property on the global object (like window in browsers). This is called implicit global access or implicit global creation.

Why This Happens

JavaScript assumes you meant to create a global variable if it can't find a declaration in any scope. It's like leaving your keys on a public counter instead of in your pocket—technically they're still "yours," but anyone can grab them.

function setCount() {
  count = 42; // Oops! Forgot 'let' or 'const'
}

setCount();
console.log(window.count); // 42 — now a global property!

Even though count looks local to the function, it became global.

Why This Is Dangerous

  • Silent bugs: Typos create globals instead of errors
  • Name collisions: You might overwrite existing global properties
  • Hard to debug: The variable "works" but pollutes the global scope
  • Security risks: Global variables are accessible everywhere, including third-party scripts
userName = "Alice"; // Meant to be local, now global
// Later, some library overwrites window.userName
// Your code breaks mysteriously

Key Takeaway: Always declare variables with let, const, or var. Implicit globals are accidents masquerading as features—strict mode ('use strict';) prevents this by throwing errors for undeclared assignments.