Caveat with remoteStorage.js and localforage in same app

Just ran into this, and it took a bit long to debug, so I thought I’d share it here:

When using remoteStorage.js and localforage in the same app, you should use the localforage.nopromises.js build. The normal build comes bundled with a Promises library that will override the one in remoteStorage.js and remove all the extra methods like e.g. Promise.defer.