IPC error handling

[kirrg001]

This issue is a

• Bug Report
• Feature Request

Summary

There is something wrong when receiving an error from Ghost. I was testing with the local process manager only - not sure if this affects production as well. It's important to fix this error, because it's super hard for the user to know what's wrong if we ship dynamic routing, but the error is not forwarded correctly e.g. you change the routing file, but you received an error.

1. Ghost sends an IPC message e.g. {started: false, error: 'a message'}
2. The message is received here. It forwards only the message, no object.
3. The target process (which is in this case the local process manager) receives the error here. And here is the problem: this function tries to access error.message.

I guess we can simply change

instance.process.error(message.error);

to

instance.process.error({message:message.error, started: message.started});

Steps to Reproduce (for a bug report)

1. Throw an error with the local process manager.
2. See that the error log in the CLI does not show the error message.

Technical details (for a bug report)

• OS: Mac
• Node Version: 8
• Ghost-CLI Version: Latest
• Environment: development
• Command: ghost start

@acburdine Any opinion on that? Thanks!