vuex-persistedstate VS project-overview

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.

C:/Dev every project gets its own folder. In addition I use a tool to keep track of technologies and practices used for each project. https://github.com/H0rn0chse/project-overview