The REPL & Quick Experiments

The Node.js REPL is an interactive shell for probing APIs, inspecting objects, and validating assumptions before you commit code to a file.

Recipe

Quick-reference recipe card - copy-paste ready.

node                          # start REPL
node --env-file=.env          # preload env vars into REPL context
node -e "console.log(process.version)"
node --input-type=module -e "import { ok } from 'node:assert'; ok(1)"

When to reach for this:

• Exploring an unfamiliar npm package's return shapes
• Verifying regex, date math, or Buffer encoding quickly
• Debugging a one-off fetch response before wiring it into a service
• Teaching teammates how process or import.meta behave

Working Example

# Start REPL with env file (Node 20+)
node --env-file=.env.development

> const { readFile } = await import('node:fs/promises')
> const raw = await readFile('package.json', 'utf8')
> const pkg = JSON.parse(raw)
> pkg.engines
{ node: '>=24.18.0 <25' }
 
> // Inspect built-in fetch headers
> const res = await fetch('https://httpbin.org/headers')
> [...res.headers.entries()].slice(0, 3)
[
  [ 'content-type', 'application/json' ],
  [ 'content-length', '...' ],
  [ 'date', '...' ]
]
 
> .save repl-session.js
> .exit

What this demonstrates:

• Top-level await works in the REPL without wrapping in an async function
• Dynamic import() loads ESM built-ins inside the REPL session
• .save writes every evaluated expression to a file for later cleanup
• --env-file mirrors production config loading during experiments

Deep Dive

How It Works

• The REPL compiles each line with V8, maintains a persistent context (global), and prints expression results.
• Multi-line input opens when braces are unclosed - paste async functions or object literals freely.
• _ holds the last evaluated result; _error holds the last thrown error (Node REPL convention).
• Dot-commands (.help, .break, .clear) are meta-commands and not sent to V8.

Useful Dot-Commands

TypeScript Notes

# Run TypeScript in REPL-like one-liners with tsx
npx tsx -e "const x: number = 42; console.log(x)"
 
# Or start tsx REPL for typed experiments
npx tsx

For typed exploration, tsx REPL is preferable to plain node when you need interfaces and generics.

Gotchas

• Shipping .save output directly - saved sessions include > prompts and may lack imports. Fix: refactor into a proper module and add tests.
• Secrets in REPL history - pasted API keys persist in .node_repl_history. Fix: .clear sensitive lines; never .save sessions with secrets.
• Assuming REPL === production module scope - require is not defined in ESM-first projects. Fix: use await import() or start with --input-type=module.
• Large object dumps - console.log(hugeArray) blocks the terminal. Fix: use util.inspect(obj, { depth: 2, maxArrayLength: 10 }).
• No test coverage from REPL checks - experiments validate intuition, not regressions. Fix: copy validated snippets into node:test cases.

Alternatives

FAQs

node --input-type=module
> import.meta.url
'file:///...'

Related

• Node.js Basics - first node commands
• Running Scripts & Shebang - when experiments become scripts
• Reading the Official Docs & Diagnostics - dig deeper after REPL surprises
• node:test - graduate experiments to tests

External Related Links

• NodeSchool - Free interactive workshoppers.
• Node.js Learn Guides - Official learning path.
• Node.js API Documentation - Complete reference for core modules and APIs.
• Get Programming with Node.js - Introductory programming with Node.js.
• Node.js in Action, 2nd Edition - Classic practical Node.js.

Stack versions: This page was written for Node.js 24.18.0 (Active LTS), npm 10+, TypeScript 5.6+, Express 5, Fastify 5, and NestJS 11.