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'm only aware of minifiers/shrinkwrappers written in Java or C/C++. There are reasons for it. (But: ...could a signed Java Applet solve the issue? ...of course a bit an overkill for the term 'Applet') .
In order to continue I pulled the module into the code. Since at development time for components the time (and space) is not as much on the line as at runtime, it worked for me. Having still modules - just not minified - is though already a leap towards a final solution with minification. Adding the cache for now is a very good tactical solution. I assume, the cache stays alive for the duration of a Web IDE session. Btw, for file name and path retention I was thinking about HTML5 storage. And for the cache beyond session I was thinking about a second, parallel modules directory - such as modulesm - that could store the minified version. Because of security I'm sure it would require a pop-up for the save-confirmation from the user, does it? - no pressure what so ever... ;-)