My understanding of a 'build for a device' is that the functionality is built-in (in low level implementation) and does not need to berequired("ModuleName"); - also implied to me by the fact that there is a ESP8266 Class with .connect() method in Espruino Reference. Over time stuff that was available (in 'older' versions through a loadable module became integrated in 'newer' version in the firmware / build. I may be going on a limb, but I notice(d) that with the experienced growth, (available) documentation becomes outdated - and misleading - because it it is a lot of work keeping it up in all corners.
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.
My understanding of a 'build for a device' is that the functionality is built-in (in low level implementation) and does not need to be
required("ModuleName");
- also implied to me by the fact that there is a ESP8266 Class with .connect() method in Espruino Reference. Over time stuff that was available (in 'older' versions through a loadable module became integrated in 'newer' version in the firmware / build. I may be going on a limb, but I notice(d) that with the experienced growth, (available) documentation becomes outdated - and misleading - because it it is a lot of work keeping it up in all corners.