@RolandGalibert, if you have initialization modules that and you can save the code reliably after they run and re-powering can pick up the initialized state, then there is an option to get rid of such modules after their execution. How much space you though get back all depends on how much of that initialization data is not referenced anymore after execution and the Modules cache is holding onto them as the only one that keeps it from getting garbage collected.
If you have initialization code that uses very verbose, human readable data which you transform into compressed, machine readable only, binary compact objects, that's where you get some RAM back. But depending on the Espruino device there are other options as @Robin points out.
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.
@RolandGalibert, if you have initialization modules that and you can save the code reliably after they run and re-powering can pick up the initialized state, then there is an option to get rid of such modules after their execution. How much space you though get back all depends on how much of that initialization data is not referenced anymore after execution and the Modules cache is holding onto them as the only one that keeps it from getting garbage collected.
If you have initialization code that uses very verbose, human readable data which you transform into compressed, machine readable only, binary compact objects, that's where you get some RAM back. But depending on the Espruino device there are other options as @Robin points out.