A HTTP error will cause Node.js to exit (non-gracefully)

If a HTTP error occurs (for whatever reason) during a Mollie API Request, Node.js exits, without a way for the end-user to catch the error, i.e.:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: Parse Error
    at CleartextStream.socketOnData (http.js:1583:20)
    at CleartextStream.read [as _read] (tls.js:507:12)
    at CleartextStream.Readable.read (_stream_readable.js:320:10)
    at EncryptedStream.write [as _write] (tls.js:366:25)
    at doWrite (_stream_writable.js:221:10)
    at writeOrBuffer (_stream_writable.js:211:5)
    at EncryptedStream.Writable.write (_stream_writable.js:180:11)
    at write (_stream_readable.js:583:24)
    at flow (_stream_readable.js:592:7)
    at Socket.pipeOnReadable (_stream_readable.js:624:5)

This can/should be prevented by adding a request.on(‘error’, function(err) { … }) handler, and calling the end-user callback function with the appropriate feedback, in the rest client:

https://github.com/mollie/mollie-api-node/blob/master/src/lib/mollie/api/client.coffee#L82-92

[vernondegoede]

Please use our new @mollie/api-client module, which is completely rewritten to ES6 and fully tested.

You can find information on how to upgrade in our Migration guide.

[dabroek]

#18 is addressing this issue.