Node.js · Theory

Path

Theory

23/723

Path is simple if you keep it on paper. Ananya uses it for Path on Ananya's board in lab hour.

Path on the board — one Path step Ananya can write from memory. Then say what Path on Ananya's board looks like after.

Without Path, lab hour gets messy and Path on Ananya's board is hard to trust.

Use Path when Path on Ananya's board must stay clear. If a simpler Node.js step works, use that instead.

Don’t do this with Path — copy-pasting Path without a dry-run. Interviewers spot it in ten seconds.

Path is not a lonely heading. Ananya ties it to Path on Ananya's board.

Viva for Path: what it is → one Path step Ananya can write from memory → the mistake (copy-pasting Path without a dry-run).

Exam tip

Board: Path on Ananya's board. Dry-run Path. Name the trap: copy-pasting Path without a dry-run.

const path = require("path");
const full = path.join("users", "asha", "docs");
console.log(full);
console.log(path.extname("report.pdf"));

path.join builds OS-safe paths; extname reads the extension.