Warning: API changing from builds post 2015-10-24

As part of the work process to take the JavaScript (Espruino) support for ESP8266 out of beta, we are re-working some of the APIs so that they are consistent between the ESP8266 board and other boards on which Espruino runs. This means that some of the API calls that you may have used in the past will no longer be present in the future.
Specifically, many of the "ESP8266WiFi.xxx" methods have moved to a module.
A draft of the new docs for this can be found here:
https://github.com/nkolban/Espruino/blo ... r_Guide.md
Again ... this is only a temporary place to find docs and a week from now, you should be able to find the proper docs at the normal location of:
https://github.com/espruino/Espruino/bl ... r_Guide.md
The work items being tracked in Github for these changes can be found here:
https://github.com/espruino/Espruino/issues/589
and
https://github.com/espruino/Espruino/issues/630
Anyone interested in examining the specs for the new interface are welcome to come and join the conversations.
It is not envisaged that once these changes are made there will be any further disruption to the API (we hope) again.
Specifically, many of the "ESP8266WiFi.xxx" methods have moved to a module.
A draft of the new docs for this can be found here:
https://github.com/nkolban/Espruino/blo ... r_Guide.md
Again ... this is only a temporary place to find docs and a week from now, you should be able to find the proper docs at the normal location of:
https://github.com/espruino/Espruino/bl ... r_Guide.md
The work items being tracked in Github for these changes can be found here:
https://github.com/espruino/Espruino/issues/589
and
https://github.com/espruino/Espruino/issues/630
Anyone interested in examining the specs for the new interface are welcome to come and join the conversations.
It is not envisaged that once these changes are made there will be any further disruption to the API (we hope) again.