Currently the next argument is not invoked

[jhusain]

Every middleware function must invoke the next argument once it has finished its job. See this article: http://expressjs.com/guide/using-middleware.html

Note that when we handle a request we neglect to call the next parameter.

[jasonphillips]

This was essentially handled back in 515e45c, right?

next() is now invoked on error from the datasource, and every other outcome is a res.send, which of course terminates the request and doesn't need to invoke next() at all. Unless I'm still missing something.

[ludovicthomas]

@jhusain As explained by @jasonphillips it has been resolved, but never published on NPM. Is it possible to publish the latest version please?
It's quite mandatory in order to get logs on the server about failures.
I'm adding @michaelbpaulson because he is the last one who has published on NPM.
Thanks

[blakeembrey]

Is someone planning to release this? I've been waiting months for the change personally, it really hinders development to not be able to debug errors properly. Most errors end up being output as { throwToNext: true }.