Kartik

The Request.json() method is an optimized version of the uWebsockets.js implementation. You can also consume the raw data using Request.on() since Request is a ReadableStream.

Ohhh I see what you are talking about now. Yeah, currently `hyper-express` looks for a `content-length` to pre-allocate a body Buffer for performance reasons. I didn't know Transfer-Encoding chunked is...

Hey, support for chunked transfer requests has been added in the recent `v6.15.2` versison.

Hey, this looks very interesting. I will review it within some large codebases of mine to test for breaking changes. Do you know about any major / guaranteed breaking changes...

Hey, apologize been a bit busy with some stuff. Will review this later this week and get merged. From a small project I tried your types in, no errors were...

Of course, feel free to do so. I think your current approach inspired by Fastify generics is probably the best course of action given a lot of Node.js developers prefer...

> I've finally found time to merge latest changes. Seems to not break anything. > > As I mentioned I would long time ago, I've added the possibility to type...

This is a great proposal and would significantly help performance for wrappers / libraries like `hyper-express` where currently, the headers and other request properties are always consumed from `HttpRequest` and...

> You don't need to know if it **will be**. You need to know if it _was_. Finding out if the request _was_ ended is easy. That's the whole point...

- Does Express.js support a similar format? - Is there a simpler function or methodlogy to parse and apply the regex from a path without having to depend on another...