Verify Server module loaded before attempting to process server config

[kbaltrinic]

Ran into to this the other day as a result of a poorly set-up mimosa-config.coffee file. The file contained a server: { port: 3001 } entry but did not include the server module in list of modules to load. (It was actually being loaded in a profile specific config). As a result attempting to run mimosa build --package oddly failed at index.coffee line #111 because server.path was undefined . The simple fix was to use the -P switch so specify the correct profile to get the server module loaded. However the failure mode was that mimosa simply hung forever (it appears the path.relative call hangs in this case) resulting in an extended debugging session.

Thus is would be good if mimosa-web-package would test to ensure that the server module is indeed loaded and if not, output a warning to the effect that a server config was found but is being ignored because the server module is not loaded.