The best would be to have two Storage 'drives' one for javascript code and some smaller data files and another bigger one in SPI flash. There is issue for that idea here https://github.com/espruino/Espruino/issues/1899
Got it, this looks like the use case I'm looking for. I'm was interested in the Storage API abstracting the access to the notion of files and doing the flash management behind the scenes, but I guess just designing the data so it fits the blocks (and then writing blocks) would work as well.
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.
Got it, this looks like the use case I'm looking for. I'm was interested in the Storage API abstracting the access to the notion of files and doing the flash management behind the scenes, but I guess just designing the data so it fits the blocks (and then writing blocks) would work as well.