broadcast-channel VS localForage

Not really an answer but have you looked into https://github.com/localForage/localForage

LocalForage: this is a wrapper around IndexedDB, WebSQL, LocalStorage, and SessionStorage with a way to define more interfaces (called drivers) *for additional storage solutions. It does a great job handling all your serialization needs, it is **asynchronous **and handles a large set of data types. Its **API resembles Web Storage API* and it is ridiculously simple to learn.

Depending on what kind of storage requirements you have, LocalForage might be a good fit. It provides a unified API to access WebSQL, indexedDB or localStorage.

Have a look at local forage. It is an almost drop in replacement for local storage, but with doing what you want and using the much nicer indexeddb when available.

This is why we have localForage.

I have been using localforage (https://github.com/localForage/localForage) in non vue applications and haven't looked back since. All the features of indexeddb with the same interface as localstorage.

localForage: A Polyfill providing a simple name-value syntax for client-side data storage, which uses IndexedDB in the background, but falls back to WebSQL and then localStorage in browsers that don't support IndexedDB.

Or even a wrapper like this https://github.com/localForage/localForage which falls back to local storage if indexeddb or Web SQL are not available

LocalForage is a good wrapper for it that had worked well for me in Vue 3. https://github.com/localForage/localForage