Memory management when using a web library that implements caching for offline use in the HTML component

What is JourneyApps’s best practice recommendations on memory management when using a web library that implements caching for offline use in the HTML component.

It is possible to make use of tech such as IndexDB / Local storage / Session storage. We don’t recommend this though, since caching inside an iframe is unpredictable, and not the intended use of the component. The best way to treat HTML components, is as pure functions that accept data over IPC, process and in some cases return data.