There is always the option to send the stuff 'over' to a (node.js) 'server' for the compile send the returned compiled artifact the board.... or store it in the module folder... or...
It should be possible to accessing the desktop that runs the WebIDE with a http request safely/securely enough by setting some TBD config in, for example, the project. The WebIDE is doing similar things to get the (module) code through google's closure compile service when uploading code with required('moduleName) to he board... under certain configuration circumstances... does it still, @Gordon?
For other tool chains I'm thinking along the same lines... javascript or any to javascript or native compilation, shrinkwrapping, packaging, etc., , etc...Doing so has most likely to consider OS variations and versions across Win-LIN*-OSX. It is though not anymore as bad as it was even a few years ago.
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.
There is always the option to send the stuff 'over' to a (node.js) 'server' for the compile send the returned compiled artifact the board.... or store it in the module folder... or...
It should be possible to accessing the desktop that runs the WebIDE with a http request safely/securely enough by setting some TBD config in, for example, the project. The WebIDE is doing similar things to get the (module) code through google's closure compile service when uploading code with required('moduleName) to he board... under certain configuration circumstances... does it still, @Gordon?
For other tool chains I'm thinking along the same lines... javascript or any to javascript or native compilation, shrinkwrapping, packaging, etc., , etc...Doing so has most likely to consider OS variations and versions across Win-LIN*-OSX. It is though not anymore as bad as it was even a few years ago.