vuex-orm VS pinia

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

Pinia tab is a feature integrated with Pinia, allowing you to view the registered modules and their details.

pinia

If you like Vuex, you'll love Pinia (the new official Vue state management library). At least, I enjoyed recently migrating my personal app from Vuex to Pinia. Pinia is even simpler / more straightforward than Vuex (and even more so compared to Redux).

Related

const authMiddleware: Middleware = ({ pinia }) => { // !!! Important !!! // tell all the stores you are contacting // Pinia instance, otherwise you will have problems because Pinia will access the global object // https://github.com/vuejs/pinia/blob/8626aac0049243de231401a01fe20092eeaf279c/packages/pinia/src/store.ts#L870 if (!authStore(pinia).isAuth) { return { path:'/login', status: 401, } } }

When installing the "pinia" package via npm i pinia, I got a bunch of errors, similar to what's described here. This seems to be an issue with npm. Solution to that : install using yarn add -D pinia

Does using the main branch of pinia fix your issue? Over aggressive unwrapping was changed in https://github.com/vuejs/pinia/pull/1444

Also, I tried one syntax based on : https://github.com/vuejs/pinia/discussions/1096