ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #express
How Express's four-argument error middleware works, why it must be mounted last, and a complete asyncHandler pattern with curl commands to verify both error and success paths.
How Kraken.js maps URLs to controller modules via the `routes` config, with a working example, the silent-failure pitfalls, and how to verify routes actually registered.
Learn how to structure Express.js microservices using Express.Router to isolate concerns, enforce middleware boundaries, and keep the main app file maintainable.
Learn how to implement, order, and test Express.js error‑handling middleware for reliable, production‑safe error reporting.
Learn how to use Express.Router to separate route handlers by feature, reduce app.js clutter, and keep middleware scoped—complete with a working example and verification steps.
Pug’s extends/block inheritance lets you define a single parent layout and override only the sections that differ per page — eliminating copy‑paste duplication while keeping asset injection composable via append/prepend.
KrakenJS moved Express middleware and route wiring into JSON config, enabling environment-specific behavior without code changes. The pattern is excellent; the framework is unmaintained.
When app.js hits hundreds of lines of route handlers, Express Router lets you split routes into focused, mountable modules. Here's a worked example with param validation, scoped middleware, and the ordering pitfalls to avoid.
Passport's local strategy leaves two decisions to you: what the verify callback returns and what goes into the session. Get both right—id-only serialization, single-purpose verify—and the rest is just routes.
nodejs
krakenjs