Thanks for sharing this information!

@luz 'MTD and eraseblocks' I wanted to say: maybe you should calculate the lifetime with eraseblocks (xx KBytes) instead of flash pages (256 Bytes) and you should take into account only a part of the chip. So at least at the mtd layer, it is operating with 64kB (0x10000) erase blocks. Thanks! I've forgotten - I had already read this in the OpenWrt documentation. It seems I'm getting older... Maybe I should write everything down.

@cas No worries again it put me on the right track and moved me on down the road so to speak.

FYI even when I do /overlay and make a 2GB swap file, the version of node does crash on some instances like installing "azure-iot-device-amqp" the nodejs run time has its own buffer that needs to be increased, though from the error they posted I dont think its this issue. Another thing about npm installs is that in some cases you need python or some other dependency like git and npm builds the module on the onion, that takes a lot of resources. For my application I use 81% file storage and have 4.7mb left but I have these modules installed: azure-iot-common colors popsicle azure-iot-device file-queue raven azure-iot-device-amqp graceful-fs serialport better-queue node-json-db client-oauth2 omega2-io-pro If you want to do RESTful messages using Oauth2, I have successfully done so using "client-oauth2" and "popcicile"

@tommaso-tani Can't think of any workaround except for cross-compiling ruby-dev yourself! Sorry!