You are reading a single comment by @allObjects and its replies.
Click here to read the full conversation.
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.
@allObjects
I assume 'this file' is used to supply the IDE with data for auto completion and other useful 'stuff' - also at runtime.
Could this file be stored online and identified by a build (scope) ID? Or could be be transmitted ansd stored in the context of the IDE if not found (yet)? And in order to completely offload the device from having this file stored or having to store (wasting memory) and having it to transmit (everytime on connect wasting time), this file could be pulled from a store like the modules are for for upload to the board. A build builder's responsibility includes then to make this file available just as the built file... like source maps for (closure) compiled code. The only challenge is then to crate a unique id for the build... may be a sh1 or-a-like (like used in git) could do the job... still a fraction of bytes compered to all the bytes in 'this file'.
Having this file not anymore available at runtime... that would need a rethinking and separation of information for the IDE support and information for the runtime support.