Fixes #207: Synchronously log error on exit

[Hilzu]

Calling process.exit(1) exits the process immediately and might prevent writes from completing as explained in process.exit documentation. Setting the exitCode property instead lets pending events in the event loop run (like writing to stderr) but prevents any additional work from being scheduled. This is the recommended way to exit Node processes.

[Hilzu]

It seems that setting the exitCode property doesn't have the effect I was hoping for (it doesn't actually exit). Let me rewrite the printErrorAndExit function to use fs.writeSync and exiting with process.exit(1)

[Hilzu]

According to the fs.writeSync documentation the version of the function that takes a string instead of buffer was only added in v0.11.5 but it seems to work according to my manual testing with v0.10.48 and the tests pass. This should be good now.

[LinusU]

Thank you!

[LinusU]

Released as 0.5.4, than you for your contribution 🚀

[mohd-akram]

This PR seems to have broken error messages when using a debugger such as Chromium. This can be seen by creating a file test.js with the following:

const fs = require('fs');
fs.writeSync(2, 'error\n');

And running node --inspect-brk test.ts then debugging in Chromium. You'll see that the output is printed in your terminal, but not in the Chromium console.

What was wrong with setting process.exitCode? I've tried it and it seems to work.