store.js

Totally! I created an issue to pull this info together: https://github.com/marcuswestin/store.js/issues/189 Check back in coming days for more details. Store.js will soon have pluggable support for localForage (either by implementing similar functionality in separate storages, or by simply adding a pluggable storage which uses localForage under the hood). There are a few benefits to using store.js, such as full cross-browser support and useful plugins, but the biggest meaningful value-add over localForage is probably the availability of a synchronous API that allows you to read and write values without callbacks, promises, etc. In my experience you only want to use asynchronous APIs when you have to, since they add a fair amount of complexity, are a common source of errors, and are harder to debug properly. But yeah, check back later and

I'm genuinely interested in supporting all use cases! If you create an issue at https://github.com/marcuswestin/store.js and describe your use case in more detail we'll figure out what the right answer is. Thanks!

I created an issue to investigate viability and usefulness :) https://github.com/marcuswestin/store.js/issues/193

On the other hand, synchronous interfaces tend to be less error prone and simpler to work with (and more enjoyable...? :) There is an active issue to add the async indexdb/websql storages to Store.js (https://github.com/marcuswestin/store.js/issues/181) so that they can be used when needed (e.g when you need to store many tends of MGs of data), but for 90% of your use cases the simplicity of the synchronous store.js API may likely save you a meaningful amount of code and callback/Promise/stack trace debuggery :)

Created issue: https://github.com/marcuswestin/store.js/issues/183 Will tackle a bit down the road.

Had somehow missed that this was a thing, it looks amazing. Also kudos on https://github.com/marcuswestin/store.js#version-20 that is how to to do a readme page.

You can back it with any storage you want :) See https://github.com/marcuswestin/store.js#write-your-own-stor... for a quick explanation of how you'd do that.

I don't know when WebSQL would be better than other storage alternatives, but yes, you could easily add WebSQL storage :) The rationale behind the new architecture is to make it trivial to write new backing storages - see https://github.com/marcuswestin/store.js#write-your-own-stor... for a quick explanation of how you'd do that. This is also true for adding new functionality, which sits "on top of" the storage (and is agnostic to whatever particular storage is being used). Here's a list of plugins that come out of the box: https://github.com/marcuswestin/store.js#list-of-all-plugins, and here is a quick explanation for how you'd write your own plugin: https://github.com/marcuswestin/store.js#write-your-own-plug...

Nice! Also relevant: localStorage wrapper for all browsers without using cookies or flash. https://github.com/marcuswestin/store.js Perhaps worth using under the hood for locache?

Consider this project http://github.com/marcuswestin/store.js as a fallback for browsers that don't support localStorage.