Local Fallback

[viktoriialurie]

Short Description

Network access is not always available, having the ability to run module federation with local files improves both the end customer experience but also the developer experience.

Longer Description

Whether for an “Offline Mode” for an application using technologies similar to Electron or ReactNative, having the ability to work with both locally cached federated remotes and federated remotes over the wire in an easy and transparent fashion is very beneficial for the end user.

Additionally, when developers are working on the codebase it is helpful for them to be able to point federated remotes to their local environment, either to reduce reliance on network connectivity or to inject local files into a more comprehensive remote application.

The functionality for fetching remotes and comparing them to locally cached versions will allow for a more stable and up-to-date local fallback.

Business Value

The desire for higher customer-perceived resiliency for applications and websites is one of the core drivers for adding offline mode. Another driver is greater developer productivity. With network connectivity and potential shared service availability issues having development teams that can work in an offline environment increases overall productivity.

Acceptance Criteria

• Offline Mode
• If the remote is not available in real-time, the application should use the local copy of the remote that it currently has
• TBD: writable: true, to have a local cache of remote containers inMemory or for Disk (to speed up local dev)
• TBD: fallback like react suspense fallback option.