I recently upgraded the Paho.MQTT.JavaScript library through the paho-mqtt NPM package to version 1.0.4 so that I could use the built in reconnect functionality. However, in doing so I discovered two issues:
The library now required me to assign a namespace to it;
that upon subscription the library would trigger the connectionLost callback, complaining that 'Paho is not defined'.
I narrowed down the issue to the library not being able to internally see the Message class, as when using require(), Paho.MQTT is not defined in the global scope, as it would when using the library through a simple Githubissues.
Githubissues is a development platform for aggregating issues.
Hello,
I recently upgraded the Paho.MQTT.JavaScript library through the paho-mqtt NPM package to version 1.0.4 so that I could use the built in reconnect functionality. However, in doing so I discovered two issues:
The library now required me to assign a namespace to it; that upon subscription the library would trigger the connectionLost callback, complaining that 'Paho is not defined'.
I narrowed down the issue to the library not being able to internally see the Message class, as when using require(), Paho.MQTT is not defined in the global scope, as it would when using the library through a simple Githubissues.