Cache loaded modules to be used offline

[Brendonovich]

Now that we load federated modules via the custom URI scheme we have the opportunity to cache them to disk for offline use.

[Brendonovich]

Implemented in 4a9c669 by taking SHA-1 of the URL hosts (ie http://localhost:3001) and SHA-1 of the URL path (/remoteEntry.js) and caching the files at /{cache_dir}/{host_sha}/{path_sha}.
We may need to cache based on the contents of remoteEntry.js/mf-manifest.json to ensure different versions of packages don't have their files getting mixed together.

[denjell-crabnebula]

Can we close this @Brendonovich ?

[zackarychapple]

ooooh this is going to get spicy :) @Brendonovich did you see the Re.Pack example? There are a lot of analogous things to pull from.

[Brendonovich]

More caching logic is probably needed for removing old files and what I said above. Does re.pack cache the remote modules after first load?

[zackarychapple]

@jbroma is the right person to ask about the Re.Pack implementation

[jbroma]

More caching logic is probably needed for removing old files and what I said above. Does re.pack cache the remote modules after first load?

Yes, the modules are cached after successful load (eval)