finalhandler
finalhandler copied to clipboard
pillarjs
Node.js final http responder
See discussion in https://github.com/nodejs/undici/issues/1115, https://github.com/nodejs/node/issues/41011. There will be `TypeError: Cannot read properties of null (reading 'destroy')` when using req as body in undici.stream, which sets req.socket to null.
In `getErrorMessage`, which is used to create a pretty error messages that is both logged and returned to clients in non-production environments, the error message is found [by simply taking...
https://www.npmjs.com/package/http-errors When we're extracting the message out of a thrown error, we should consider respecting the `expose` property on it so that we provide consumers some way of exposing information...
The HTTP2 spec does not support sending a status message, so when `res.statusMessage` is set a process warning is emitted.
To avoid setting status message that is not supported by HTTP/2, checked if the request's HTTP major version is less than 2. Without this fix some of apps using this...
This PR fixes [nyc](https://github.com/istanbuljs/nyc) version to 14.1.1 when running tests in node 8 or node 9. `nyc 15.x` requires a `yargs` package version that requires node >=10. I've also added...
the 'cause' value in the Error class were not included in the response text. This PR closes https://github.com/expressjs/express/issues/5630
Hello, I am trying to upgrade `finalhandler` to the latest 1.x on another project and I'm not sure what exactly is in the release? I don't see any tags for...
The [`unpipe`](https://www.npmjs.com/package/unpipe) package was used to unpipes all destinations from a given stream. Taken from the unpipe readme: > With stream 2+, this is equivalent to stream.unpipe(). When used with...
Hi `finalhandler` maintainers, I noticed in the changelog for the latest release (v2.0.0) that there is a breaking change which states: > drop support for node