mqttjs-v5 icon indicating copy to clipboard operation
mqttjs-v5 copied to clipboard

Development repository for an overhaul of the MQTT.js client.

Results 10 mqttjs-v5 issues
Sort by recently updated
recently updated
newest added

Unfortunately, I don't have the cycles to continue working on this rewrite. As a result, my colleagues and I have decided to put this development on hold. I'm writing this...

Please pay attention to this issue in the development of the new version: https://github.com/mqttjs/MQTT.js/issues/1568#issue-1528687681 I will be very grateful.

_EDIT (@vishnureddy17): As we continue with our vNext work, our thoughts on some of these topics have changed. As such there are corrections and updates in this thread, and some...

@vishnureddy17 going to create this issue to track our discussions and work on optimizing the number allocator. Can you share the benchmarking code and your results comparing the number-allocator package,...

You don't have to wait until you establish a connection before you start publishing. MQTT.js queues up all messages you publish in your outgoing store until it actually connects and...

From the MQTT spec: "Clients typically wait for a CONNACK Packet, However, if the Client exploits its freedom to send Control Packets before it receives a CONNACK, it might simplify...

Have some doubts on what we should name things in ConnectOptions. Making an issue here to track this. - `protocolVersion` or `protocolLevel`? Code currently uses `protocolVersion`, but MQTT spec uses...

Should the sequencer continue to have a write function, or should it emit packets so the upper level client can handle the write?