Called 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.
Called 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.
Called 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.
Called when the backend application shuts down. Contributions must perform only synchronous operations. Any kind of additional asynchronous work queued in the event loop will be ignored and abandoned.
the express application.
This service is responsible for serving the frontend files.
When not bound,
@theia/cligenerators will bind it on the fly to serve files according to its own layout.