Matteo Collina

that's because the `onSend` hook that is being applied to the route is applied _after_ the one added by `@fastify/compress`, leading to garbled data. If you want to alter the...

> Whilst there is not much that Fastify compress can do in this situation, it might be good to potentially modify the return status from 200 OK to 500 Internal...

Sure, send a PR.

That feature was added a long time ago in https://github.com/fastify/fastify-compress/pull/34. I think we might want to revisit that.

I guess something very odd is happening within http/2. I don't think the problem here is GC - it's 100% true that HTTP/2 consumes more resources than HTTP/1.1 but the...

Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.

Thanks for reporting! Can you provide steps to reproduce? We often need a [reproducible example](https://stackoverflow.com/help/minimal-reproducible-example), e.g. some code that allows someone else to recreate your problem by just copying and...

Thanks for reporting! I think having a no-op would be problematic, but this certainly needs documenting. Would you like to open a PR?

Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.

It this a JS or a TS bug?