Why should you care?

Good scope stops name collisions — two functions can both use i in loops without breaking each other.

See it live — copy this example

Paste into an HTML file or the browser console (F12). Use Run below when the live editor is available.

let globalMsg = "outside";

function greet() {
  let localMsg = "inside function";
  console.log(globalMsg);
  console.log(localMsg);
}
greet();
// console.log(localMsg); // Error — not in scope

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• globalMsg is in the outer scope.
• localMsg exists only inside greet().
• Uncommenting the last line causes ReferenceError.

Practice next

1. Run greet() and see both messages print.
2. Uncomment console.log(localMsg) and read ReferenceError.
3. Add a nested function inside greet that reads localMsg.
4. Shadow globalMsg with a local let globalMsg inside greet.
5. Move localMsg to outer scope and show it is visible everywhere below.

Remember

Variables declared inside { } are block-scoped with let/const Functions create their own scope Avoid polluting the global scope

ScriptVerse analytics helper

Each chart module keeps private counters inside functions instead of polluting window with temp variables.

Outcome: Proper scope prevents name collisions when many scripts load on one dashboard page.