How is caching handled on web js-sdk and how is it different from the ts-sdk
On the Typescript SDK, caching is disabled by default and opt-in on demand. Default caching strategy is a group banal object storages with a set of simple method (read, write, erase). In the SDK are also available replacements (on disk persistent store) for you to compose the caching strategy which fits your application the best.
The “runQuery” function, which enables poking in cache first, will still work if the cache is disabled (but of course, without its any of its benefits). It can be useful to keep implementing all functions with it if your application proposes to let your end-user choose about the caching policy of their session.