Kamil Mysliwiec

Let's track this here https://github.com/nestjs/nest/pull/13337

The original PR would cause a significant breaking change and cannot be merged as it would lead to major regressions elsewhere. I'll reopen this issue and if someone is willing...

It changed the default request method from "use" to "all" which knowing how different HTTP drivers work, would evidently affect many existing projects.

Would you like to create a PR for this issue?

> In case of going this way, [SSE doc page](https://docs.nestjs.com/techniques/server-sent-events) should be updated to reflect the possibilty of sending a Promise and some examples should be added. Why can't you...

You can declare a new custom strategy that inherits from the `ServerGrpc` class and overrides one method (I'm assuming `loadProto`) to register gRPC reflection API. If we want to make...

But this means adding yet another peer dependency to the `@nestjs/microservices` package which already has way too many of them. I agree that `@grpc/reflection` package has several benefits and using...

Let's pursue the number 1 option (easy to integrate with existing services and compatible with the regular gRPC microservice creation flow - with no need to explicitly import the server...

LGTM

Adding a mention in the docs sounds valuable