When running in 'donejs start' mode, errors are not shown properly

[hurgleburgler]

How often can you reproduce it?

• Always
• Sometimes
• Rarely
• Unable
• I didn’t try

Description:
When running in 'donejs start' mode, with 'live-reload' removed from package.json.configDependencies, less errors are not shown on the server's command line. Instead, a generic UnhandledPromiseRejectionWarning: Unhandled promise rejection. is shown.

Steps to reproduce:

1. Create new donejs app
2. Remove 'live-reload' from package.json.configDependencies
3. Force a simple error state:

• Inside styles.less, add:

html {
  background-color: @blue;
}

4. Start app with 'donejs develop'
5. Load app in browser
6. Note the correct error is shown on the server command line:
   [LessError: variable @blue is undefined]
7. Restart app with 'donejs start' mode
8. Load app in browser
9. Note ambiguous "Warnings" on the command line as the server gobbles up the error messages:

(node:53335) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:53335) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 17)
(node:53335) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 19)

Expected results:
Running in 'donejs start' with 'live-reload' turned off should display actual errors and not hang app.

Running in 'donejs start' with 'live-reload' turned off hangs browser on less errors.

Actual results:

Environment:

Software	Version
donejs -V	3.2.0
node -v	v11.14.0
npm -v	6.9.0
Browser	Chrome
Operating system	OSX