Douglas Wilson

This issue got closed by the OP before a vote / discussion was able to occur. Reopening as the tracking discussion for this.

I just wanted to circle around to this hanging issue. I believe this was discussed and the general consensus was to change the default to production to prevent client stack...

Hi @mqsoh, thank you for the pull request! I think that the pull request is reasonable, only thinking about the name of the setting and wondering if there is a...

Are you passing in the stream option to morgan in your app? It seems like the error is coming from whatever the stream that morgan is attempting to write to.

Can you provide full steps to reproduce the issue? Please include a complete app (could just use the example from the readme if it reproduces the issue) and the instructions...

Hi @CullenShane , the `req.params` property is only populated in the middleware/handler that has those parameters defined on the path. I assume you defined your error handler with no parameters...

Ah, very interesting. Even more so given you are seeing the error `Uncaught TypeError: Cannot read property 'params' of undefined occurring... I am not sure how you can possibly seeing...

> req.params is undefined when we expected it always at least be an empty object. Ah, thank you, that does help 👍 . I can say, at least, that `req.params`...

Thanks for that update @busticated . I just wanted to post here to see if you found anything additional at all or not so far.

> the one thing i did turn up is that - in our app at least - we get the same error / issue when invoking Express' default error handler...