Nicolas Lebacq

> i tried the exact code in the first post and it seems to work fine for me > > could you give some more info, like how you're building...

I can confirm installing the latest update results in Docker Desktop being uninstalled instead.

> Unless some significant feature is coming (like a new version of MQTT), it's not worth doing it. > > Usually, it's harder to get typescript code to be as...

> > Usually, it's harder to get typescript code to be as fast as JS, and a rewrite would require extensive benchmarks. > > Depending on the TS configuration, down...

> Anyway, I'm not totally opposed. I would recomemnd migrating to ESM at the same time and adopting node:test and Node 22+, and keep a purely type-stripping setup. You can...

> Let's do 22+ to leverage native TypeScript in Node tests for development. This future-proof setup avoids most of the pain when dealing with TypeScript, building, and running tests. I'm...

Would you prefer if I first converted the project to a super lenient TypeScript and then added each rule through a separate PR or do you prefer an all-in-one PR?

So I was not part of the original discussion but @robertsLando pointed me here. I just want to say that reading this: > Zero external dependencies. Makes me very happy....

I'm late to the party, but this code: ```ts export const getMqttClient = ({ clientId, username, password, ...handlers }: IMqttClientProps) => { const client = connect(MQTT_WS_URL, { clientId, username, password,...

@SimonWallner So I can see that you are on the "Status" section which does not cause any issue. You should be able to reproduce the issue if you go to...