OptionalconfigureCalled after the initialization of the backend application is complete. Use this to configure the Express app before it is started, for example to offer additional endpoints.
The implementation may be async, however it will still block the configuration step until it's resolved.
the express application to configure.
either undefined or a Promise resolving to undefined.
OptionalinitializeCalled during the initialization of the backend application. Use this for functionality which has to run as early as possible.
The implementation may be async, however it will still block the initialization step until it's resolved.
either undefined or a Promise resolving to undefined.
OptionalonCalled right after the server for the Express app is started. Use this to additionally configure the server or as ready-signal for your service.
The implementation may be async, however it will still block the startup step until it's resolved.
the backend server running the express app.
either undefined or a Promise resolving to undefined.
OptionalonCalled when the backend application shuts down.
When shutdown is initiated via SIGINT/SIGTERM, contributions are dispatched
in parallel and any returned promise is awaited up to SHUTDOWN_TIMEOUT_MS
milliseconds while injected services from the root container are still
resolvable.
On synchronous-exit fallback paths (uncaught exceptions, server bind failures, or normal process exit), the hook is invoked synchronously and any returned promise is discarded. Implementations should be resilient to either path.
Contributions must be independent of one another during stop because they are dispatched in parallel.
Optionalapp: Applicationthe express application.
Contribution for hooking into the backend lifecycle:
initialize()configure(expressApp)onStart(httpServer)onStop()