Same shape as the Python lab — variables, objects, loops, functions — then the same weather API call, closed out with fetch() instead of urllib. This runs as one continuous Node REPL session: values persist exercise to exercise.
Before We Start
Meet the Node REPL.
Typing node at a bash prompt drops you into JavaScript's version of the REPL you used in the Python labs — same idea, one line at a time, result printed immediately.
Its prompt is even shorter: > means ready for a new line, ... means it's still waiting on you (mid-block, same as Python's ...).
Click inside the black box below to focus it. Values persist across the whole lesson, same as before.
One honest simplification: a real Node REPL also prints undefined after any line that doesn't produce a value (like a const declaration). This lab skips that noise — so when the real one chats back undefined at you, nothing is wrong.
Done
Different syntax, identical shape.
A value, an instruction, a decision, a repeat, a function — same five ideas as the Python lab, curly braces instead of indentation. And the closer proves the real point: curl, Python's urlopen(), JavaScript's fetch() all just did the same request/response round trip from the HTTP lab. The language changes. The shape underneath doesn't.