Router() base-path mounting middleware-order consistency across NODE_ENV

When an Express application uses router() to mount modular route definitions under a shared base path, the placement of application-level middleware relative to that mount point influences which handlers execute for inbound requests. The documented behavior states that middleware order determines pipeline execution, and that router() provides modular route definitions mountable under a base path. However, the precise interaction when middleware is declared both before and after a router() mount, especially across differing NODE_ENV settings, remains unspecified. This uncertainty affects the reliability of repeatable development environments where the same file tree and middleware stack must produce consistent request handling in development and production.

• What is the interaction between middleware positioned before router() mounting and routes defined within the mounted router when the base path is matched?
• Does express.json() body-parser behavior differ between NODE_ENV development and production when router()-mounted routes handle JSON payloads?
• Can middleware error-handling boundaries be reliably attached after router() mounting without risk of unhandled promise rejections in stacked pipeline configurations?