Explain the concept of REPL in Node.js | Interview Question

Q: Explain the concept of REPL in Node.js

**Target Audience:** Engineers preparing for Node.js phone screens — no prior REPL experience assumed. **Difficulty:** Easy > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . The session transcript below came from an **actually running, programmatic REPL session** on Node v24.19.0, not a description of expected behavior. ## 1. Why This Even Matters — A Story First A chemist testing a small reaction does not build an entire assembly line to try it — they use a bench: measure a bit, react it, observe the result, then decide the next step based on what just happened. The bench is not where the factory's actual production runs; it is where ideas get checked quickly before committing to the real process. The REPL is Node's bench. ## 2. The Core Idea 📌 **Interview term: REPL** — **Read-Eval-Print Loop**. Node reads one expression, evaluates it, prints the result, and loops back for more. Running `node` with no

The problem

Question presented to candidate: "Running node with no file arguments drops you into a prompt where you can type JavaScript directly. What is actually happening there, and is that prompt the same thing as running a .js file?"

What a strong answer should cover:

REPL stands for Read-Eval-Print Loop: Node reads one line/expression of input, evaluates it, prints the result, and loops back for the next input — running node with no file argument starts this interactive session.
It shares Node's actual JavaScript engine and standard library with any script — the REPL is not a separate, limited "toy" interpreter; require(), built-in modules, and full language features are all available inside it.
📌 A concrete, verifiable feature: the REPL keeps a special variable, _, always holding the result of the last evaluated expression — genuinely usable in the next line, not just documented behavior.
Multi-line input (an unfinished object literal, an open block) is handled by the REPL detecting the incomplete expression and prompting for continuation, rather than evaluating a syntactically broken partial line.
Special dot commands exist specifically for the REPL context: .exit, .help, .editor (a multi-line paste-friendly mode), .save/.load (persisting/reloading session history to/from a file) — these are REPL-specific, not valid inside an ordinary script.
A precise answer distinguishes the REPL's use case (quick, interactive exploration — checking how an API behaves, testing a small expression, inspecting a value) from a script file's use case (the actual, repeatable, version-controlled application logic) — the REPL is explicitly not the place application code lives.

Clarifying questions expected:

"Is the interviewer asking about the interactive CLI experience, or Node's programmatic repl module for building a custom REPL into an application?" — both exist and are related but distinct.
"Is there a specific dot command or REPL behavior the question is really getting at?"

Code / implementation expected: Optional for the interactive-CLI framing; showing the programmatic repl module actually evaluating input (including the _ variable) is a strong, concrete way to demonstrate real understanding rather than surface familiarity.

fundamentals
repl
cli

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for Node.js phone screens — no prior REPL experience assumed. Difficulty: Easy

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. The session transcript below came from an actually running, programmatic REPL session on Node v24.19.0, not a description of expected behavior.

1. Why This Even Matters — A Story First

A chemist testing a small reaction does not build an entire assembly line to try it — they use a bench: measure a bit, react it, observe the result, then decide the next step based on what just happened. The bench is not where the factory's actual production runs; it is where ideas get checked quickly before committing to the real process.

The REPL is Node's bench.

2. The Core Idea

📌 Interview term: REPL — Read-Eval-Print Loop. Node reads one expres

The solution is hidden so you can try first

6 min read · 9 sections

Read the code

JavaScriptA real, programmatic REPL session (repl.start) verifying the special _ last-result variable

const repl = require("repl");
const { PassThrough } = require("stream");

const input = new PassThrough();
const output = new PassThrough();
let collected = "";
output.on("data", (d) => { collected += d.toString(); });

repl.start({ input, output, terminal: false, prompt: "" });

input.write("2 + 2\n");
input.write("_ + 10\n"); // "_" refers to the previous line's result, 4
input.write(".exit\n");

setTimeout(() => console.log(collected), 200);
// 4
// 14   <- proves "_" genuinely held the prior result

Discussion

Other approaches, follow-ups and how it went in real interviews.

Sign in to join the discussion.

No comments yet. Share how you would answer it.

The solution is hidden so you can try first

Keep your momentum going.