ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When Express sits behind Nginx or a CDN, req.ip is wrong by default. Learn how trust proxy works, configure trusted hops safely, and verify client-IP behavior without exposing your app to header spoofing.
Learn how to use Kraken.js convention-based routing to eliminate manual route registration and organize API endpoints using the services directory pattern.
Use express.Router() for feature-level isolation in one Node.js process. Mount routers at prefixes to scope middleware, parameter handlers, and error handling; graduate to sub-apps or microservices as isolation needs grow.
Learn how to architect an Express.js middleware pipeline to separate cross-cutting concerns from business logic, establish trust boundaries, and avoid common pitfalls like hanging requests.
Learn how Express Router lets you group routes, attach route‑specific middleware, and keep your main app file tidy. Follow a step‑by‑step example, discover common mistakes, and see when a router is overkill.
Learn how Kraken.js uses directory-based routing to eliminate Express.js routing boilerplate and improve project scalability through implicit URL mapping.
Integration boundary When integrating Pug 3.x as an Express.js view engine, the template compiler emits async functions whenever a template uses await in iteration, async mixins, or async includes. The compiled render function then returns a Promise<string> instead of a plain string. Express's res.render method, however, expects the view engine's __exp
express
nodejs
krakenjs