vuex-persistedstate VS vuex-orm

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.

You're absolutely right. I should have mentionned that the app uses Vuex-ORM to handle and query the data. The actual building of the reports contains various calculations and is done off the main thread. The reports are then saved as a model in vuex-orm, this basicaly acts as a cache. The thing is I don't know when to invalidate the cache or not so everything is invalidated when a new data event is added. There's nothing reactive about it.

Most people try to have front-end state be a 1-1 mapping of the DB. One of the easiest way about it is to use a front-end "ORM" like vuex-orm.

Not quite the same but Vuex ORM does a few of these things. Main similarity is helping to abstract your API calls out of each individual component. https://vuex-orm.org/

Most interactions with the store are done with VuexOrm, which gives us a gorgeous API. Stuff like this:

In one lib: Vuex-Orm

Thanks for great comment! I have one question.

The biggest thing I miss in react ecosystem is decent redux ORM. https://vuex-orm.org is just so great for so many use cases (agree that it might an antipattern in many situations). Is there any chance that https://github.com/redux-orm/redux-orm, which was actually what inspired vuex-orm, would get more love from anyone to become an actively maintained library?

Thanks

I know there is a package for persisting Vuex data via the local store but wondered if anyone knows this works with Vuex ORM.

Sounds like you need this: https://vuex-orm.org/

could peep this https://github.com/vuex-orm/vuex-orm