If we support #32, we can have a custom require loader, that will load our custom implementations of:
@adobe/aio-lib-state
@adobe/aio-lib-files
These will support all the APIs available.
@adobe/aio-lib-state - in memory hashmap, backed up by a .json file written to disk, and read on startup.
@adobe/aio-lib-files - in memory file tree, pointing to a specific location on disk as the root to read the files from. The file hierarchy is read on startup
If we support #32, we can have a custom require loader, that will load our custom implementations of:
These will support all the APIs available.