Orientation: Running and Reading JavaScript

Why it matters

“JavaScript” usually means two things bundled together: a language, and a set of extra tools the place running it hands you. Confusing the two is the single most common source of “why does this work in the console but not when I run the file?” bugs. Getting oriented here — what’s the language, what’s the environment, and how to read an error message — pays off in every lesson that follows.

Mental model

The language itself is standardized as ECMAScript. A JavaScript engine (V8 in Chrome and Node, SpiderMonkey in Firefox, JavaScriptCore in Safari) implements that standard: let, const, functions, arrays, Promise, and so on all work identically everywhere.

Everything else — console.log, the DOM (document, window), fetch, Node’s fs and process — is a host API. The browser and Node each hand your script a different toolbox on top of the same language:

Small example: three ways to run the same program

The same two-line program, run three different ways, produces the same output every time — because it only uses language features.

let greeting = 'Hello, JavaScript!';
console.log(greeting);

Hello, JavaScript!

The same file, saved as hello.js and run with node hello.js from a terminal, prints the exact same line — Node’s engine (V8) executes the same ECMAScript, and console.log happens to exist as a host API in both places.

Statements and expressions

An expression is anything that produces a value: 5 + 3, "hi".toUpperCase(), greeting. A statement is a complete instruction — expressions are often part of a statement, but a statement itself doesn’t produce a value you can use.

Statements are normally separated by semicolons. JavaScript will insert missing ones for you through a process called Automatic Semicolon Insertion (ASI) — which is exactly why the following is a well-known trap:

function makeGreeting() {
  return
  {
    text: 'Hello!',
  };
}

console.log(makeGreeting());

undefined

Reading an error message

Errors are evidence, not failures. Two you’ll see constantly this early on:

console.log(greting);

Uncaught ReferenceError: greting is not defined

That’s a ReferenceError — the code is grammatically valid, but at the moment it ran, no binding named greting existed (note the typo). Compare it with a error the engine catches before running anything at all:

console.log('Hello';

Uncaught SyntaxError: missing ) after argument list

A SyntaxError means the text isn’t valid JavaScript at all — nothing in the file runs, not even lines before the mistake. ReferenceError means the syntax was fine, but something the code pointed at doesn’t exist. Both messages name the error type first, which is the fastest way to know which category of problem you’re looking at before reading further.

Check your understanding

Practice: warm-up

Open a browser console and, one at a time, evaluate: 2 + 2, let a = 10;, a, console.log(a). For each, note whether the console shows a returned value, undefined, or nothing extra at all — and why.

2 + 2          -> 4 (an expression's value)
let a = 10;    -> (nothing shown — a statement, not a value)
a              -> 10 (a is now an expression referring to the binding)
console.log(a) -> prints 10, then shows undefined (console.log's own return value)

Practice: apply it

Save this as greet.js and run it with node greet.js. It’s broken — predict the error type before you fix it, then fix it.

function greet(name) {
  console.log('Hello, ' + name + '!'
}

greet('Ada');

Modification challenge: add the missing ), run it again, then change the greeting to also print the length of name.

Summary

• ECMAScript is the language; browsers and Node each add their own host APIs on top of it — code using only language features behaves identically everywhere.
• An expression produces a value; a statement is a complete instruction that may contain expressions but isn’t one itself.
• Automatic Semicolon Insertion fills in missing semicolons using specific rules — most notably, a line break right after return ends the statement there, which is why this lesson writes semicolons explicitly rather than relying on it.
• SyntaxError means the file never became valid JavaScript, so nothing in it ran. ReferenceError means it parsed fine but referenced a binding that doesn’t exist at that point.
• Reading the error type first tells you which category of problem to look for before you read the rest of the message.