Express

Express is the de facto standard web framework for Node.js, providing a thin layer of routing, middleware, and HTTP utilities on top of Node’s core http module. Since 2009 it has powered everything from small prototypes to large-scale production APIs, and its middleware-based architecture became the template most later JavaScript frameworks still borrow from.

With version 5 built on the standalone router package, Express keeps a tiny, unopinionated core — request/response helpers, a middleware chain, and view-engine integration — while leaving state management, ORM choice, and project structure entirely up to the developer.

What You Get

• A middleware-based request/response pipeline (app.use, app.METHOD)
• Built-in routing via the standalone Router class, with param handling and route chaining
• HTTP helpers on req/res for content negotiation, redirects, caching headers, and ETags
• View-engine integration supporting 14+ template engines through a consistent res.render() API
• Static file serving via serve-static
• json/urlencoded/raw/text body-parsing middleware built on body-parser

Common Use Cases

• Building REST/JSON APIs for single-page apps or mobile clients
• Server-rendered websites using template engines like EJS, Pug, or Handlebars
• Lightweight microservices and internal tooling backends
• Prototyping HTTP servers quickly before adopting a more opinionated framework

Under The Hood

Architecture lib/express.js’s createApplication() builds the app as a callable function wired to app.handle, mixes in EventEmitter and the lib/application.js prototype for app-level methods, and sets req/res prototypes from lib/request.js and lib/response.js, which extend Node’s http.IncomingMessage and http.ServerResponse. Routing itself is delegated to the standalone router package (split out in v5), while view rendering flows through lib/view.js; middleware registered via app.use()/app.METHOD() is layered onto the underlying Router instance, and each request is dispatched by app.handle(req, res, next) walking that middleware stack.

Tech Stack Pure JavaScript (CommonJS, no build step), requiring Node >= 18. The core depends on a curated set of small, single-purpose npm packages — body-parser, serve-static, finalhandler, router, mime-types, cookie, qs, on-finished, http-errors — rather than a monolithic internal implementation. Tooling is eslint 8 for linting and mocha + nyc for tests and coverage.

Code Quality 73 test files under test/ and test/acceptance/ cover both unit and acceptance-level behavior; every exported function in lib/ carries consistent JSDoc header comments describing params and return values. Error handling is centralized through http-errors and a dedicated finalhandler module rather than ad hoc try/catch. A long-running Technical Committee governance process with a published security policy and contributing guide further signals a mature, well-maintained codebase.

API Design Minimal boilerplate — const app = express(); app.get('/', handler); app.listen(3000) is a complete server. Naming is highly consistent (app.get/post/put/delete mirroring HTTP verbs, res.send/res.json/res.render as symmetric response helpers), and the repo ships 20+ runnable examples (auth, MVC, content negotiation, multi-router) alongside the expressjs.com documentation site, keeping the learning curve shallow despite the framework’s broad feature surface.