Kamil Mysliwiec

I'll investigate this as soon as I can, thank you @weissmall

I can reproduce this with raw `kafkajs` setup so it doesn't seem to be related to NestJS ```ts import { Kafka } from "kafkajs"; const kafka = new Kafka({ clientId:...

Would you like to create a PR replacing kafkajs with node-rdkafka?

Sounds good @mkaufmaner

https://github.com/nestjs/nest/pull/10530 has just been merged

This will lead to compilation errors for projects with `skipLibCheck` set to false

I created a new PR based off this one with a slightly different approach in order to avoid introducing breaking changes Let's track this here https://github.com/nestjs/nest/pull/13337

So far the only way to accomplish this is to use a custom strategy that extends the built-in transporter. Example: ```typescript import { ServerMqtt } from '@nestjs/microservices'; import { MqttClient...

Instead of creating a new page, we should add a dedicated section to each transporter as the implementation can vary considerably

cc @tolgap 👀 @coderhammer this method call won't have any impact if `forceCloseConnections` is false (which is the default)