Node's built-in http module can create a web server with no dependencies. In practice most apps use a framework like Express on top of it, but understanding the raw server clarifies what frameworks do for you.
http ;
server = http.( {
(req. === && req. === ) {
res.(, { : });
res.(.({ : }));
} {
res.();
res.();
}
});
server.(, .());
The callback runs for every request. You inspect req (url, method, headers) and write to res (status, headers, body). Note you handle routing and parsing entirely by hand.
let body = "";
req.on("data", chunk => body += chunk); // body arrives in chunks
req.on("end", () => {
const data = JSON.parse(body); // parse once fully received
});
With raw http, even reading the request body means manually collecting stream chunks — tedious, which is exactly what frameworks abstract away.
import express from "express";
const app = express();
app.use(express.json()); // body parsing handled for you
app.get("/", (req, res) => res.json({ message: "Hello" })); // routing handled
app.post("/users", (req, res) => res.status(201).json(req.body));
app.listen(3000);
Express adds routing, body parsing, middleware, and convenient helpers (res.json, res.status) — replacing dozens of lines of manual http code.
The http module is the foundation every Node web framework builds on.
Knowing how to create a raw server — and seeing the manual work it requires (routing by inspecting req.url/req.method, collecting body chunks, setting headers) — makes clear what value frameworks like Express add (routing, body parsing, middleware, helpers).
This understanding helps you debug at the right level and appreciate why frameworks are standard for real applications, while raw http remains useful for lightweight services or learning the fundamentals.