https plugin fails silently

[abarbosa-godaddy]

🐛 Bug Report

The startServer function does not throw an error when port is already in use, it only prints a message. For applications that depend on the server working it should throw an error instead.

To Reproduce

Configure the gaket-plugin-https and try to get the server up twice.

Expected Behavior

It should throw an error.

[abarbosa-godaddy]

In my scenario, we are starting the server like this

import './alias-import';
import gasket from './gasket';

const gasketActions = gasket.actions;

gasketActions
  .startServer?.()
  .then(() => {
    console.log('server started sucessfully', gasketActions)
    gasketActions.getSwitchboardClient?.().catch(switchBoardErr => {
      throw new Error(`Error starting switchboard client: ${switchBoardErr}`);
    });
  })
  .catch(err => {
    console.error('Error while starting application:');

    throw err;
  });

This triggers as plugin, we have to setup stuff. Once we get express available it starts some stuff like Redis and BullMQ through a function named boot.

export default {
  name: 'routes-plugin',
  hooks: {
    express: async function (gasket: Gasket, app: Application) {
      boot(app, container.envConfig);
    }
  }
};

The thing is that this hook is being called even though the server could not get up - not sure if this is an expected behavior. This caused the app to start up Redis and bullmq, keeping it alive even though the server didn't get up.