js-cookie VS localForage

Once the user is logged in, you may need to access information like the user's name, email, etc. Choreo sends this information encoded in a cookie (named userinfo) upon successful login. We can extract the information using a cookie parsing library. For this example, we will be using js-cookie library.

Interesting thread. If oracle were to send a cease and desist to everyone that uses "javascript" I would have received one years ago: https://github.com/js-cookie/js-cookie

So something like this... (I’ll be using this package to simplify the code)

I created js-cookie with Klaus as we're planning to do something similar, but by leveraging crypto gains and leaving the money in a wallet to hopefully accrue some value over time and maximize the impact in other Open Source projects in the future.

There is an npm package we can use called js-cookie(or, alternatively, you can use a script tag to import it from jsDelivr CDN. Use this link for more info on how to install it.)

We use vuex-persisted state for session storage. We use https://github.com/js-cookie/js-cookie to set the auth cookie and then we have a getter in our store that checks the cookie token for validity for isLoggedIn

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