As the jsdoc notes, it leaves the module in a broken state. Thus, it should not be usable from the outside. So we may deprecate and remove it. Devs are supposed to either use `setCache` or manually reload via `loaadOptions`.
As the jsdoc notes, it leaves the module in a broken state. Thus, it should not be usable from the outside.
So we may deprecate and remove it.
Devs are supposed to either use
setCacheor manually reload vialoaadOptions.