js-cookie VS vuex-persistedstate

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

You could just use something like https://www.npmjs.com/package/js-cookie

Have a look at js-cookie. Also, read this.

js-cookie might help?

Are you using js-cookie, this js-cookie, on the server?

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

This is a simple video start guide to see how to get, set and remove cookies using npm package js-cookie in react.

This post was written since robinvdvleuten/vuex-persistedstate has been archived on February 2022.

https://github.com/robinvdvleuten/vuex-persistedstate#readme

As others have stated, stick to router methods. For extra spiciness, you can also persist your state using vuex-persistedstate. Use thoughtfully.

Those localstorage plugins just call JSON.stringify and JSON.parse and write/read that from the localstorage (set & get)

Have a look a this, it works very well. https://github.com/robinvdvleuten/vuex-persistedstate

For the lock to function efficiently we will need to have our password and lock status data persistent on page reloads, to do this we'll use the vuex-persistedstate plugin.

If so, is this the right library to use? https://github.com/robinvdvleuten/vuex-persistedstate https://github.com/cmp-cc/vue-cookies

On the second tip you would query your server for all the items that exist in it and store them locally with the help of vuex and a persistence plugin such as vuex-persistedstate so that when the user reloads the website the data wont be lost. Afterwards for every subsequent search that will be performed by users the queries would be made to the item data pre-fetched and locally stored on the browser instead of making a new API call to your server on each search request. A point to be noted here is that this is a sound application if your database isn't being updated throughout the day, otherwise your users won't be able to query for the new added data.