Just a thought on this. Espruino on ESP8266 now has many more JSvars available to it than the early versions of the port did - and I've been meaning to try the core espruino MQTT module on it to see if it runs - but, back in day, on the development versions, the module was just too big to load and then run any sort of application on the back of.
The errors you mention here would suggest to me that it is still too big. Just wondering if merely dumping the connections options as you did was enough to keep within memory..
Can you check process.memory when your code is loaded/running? It would be interesting to know what "free" is.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Just a thought on this. Espruino on ESP8266 now has many more JSvars available to it than the early versions of the port did - and I've been meaning to try the core espruino MQTT module on it to see if it runs - but, back in day, on the development versions, the module was just too big to load and then run any sort of application on the back of.
The errors you mention here would suggest to me that it is still too big. Just wondering if merely dumping the connections options as you did was enough to keep within memory..
Can you check
process.memory
when your code is loaded/running? It would be interesting to know what "free" is.