vue-query VS MobX

I started using the Vue port of this recently, VueQuery. Once you understand that this replaces the need for a store (for data at least) then everything starts falling into place and its really easy to implement caching, infinite scrolling and other cool endpoint stuff.

I use vue-query and would recommend it.

For server-side state I find something like https://github.com/DamianOsipiuk/vue-query to be nicer than Vuex, and then you can reserve Vuex for purely client-side state

I think you are looking for https://github.com/DamianOsipiuk/vue-query It uses react-query/core under the hood.

Are you looking for this? https://github.com/DamianOsipiuk/vue-query

React-Query, SWR, Redux Toolkit Query, Vue Query for RESTful APIs

Check out swrv or vue-query, they do this for you. One or two people from the vuex core team work on swrv.

React Query is React specific, but its core was fully separated from React and it can be used to build solutions for other frameworks as well. Such solutions have already begun to emerge. For example, Vue Query.

Hey, might give https://vue-query.vercel.app/ a try soon

State Management: MobX

Its decade-long evolution proves that implicit reactivity isn’t just clever—it’s robust. You can read more about companies who uses MobX here

MobX simplifies reactivity with automatic updates and minimal boilerplate.

MobX Guide

The "Diamond Problem" isn't a new challenge in the "eager" reactivity model. Some computation algorithms (especially those used by MobX) can tag the "nodes of the reactive dependency tree" to level out state computation. With this approach, the system would first evaluate the "root" data sources (A and E in our example), then B and C, and finally D. Changing the order of state computations helps to fix this kind of problem.

Libraries like Redux or MobX can be used for state management, but it is important to weigh the pros and cons of introducing a centralized state.

Official Website

For large-scale applications with frequently changing state, dedicated state management libraries like Redux, MobX, Zustand, etc. are generally better choices. These libraries offer efficient ways to handle state updates and minimize unnecessary re-renders.

States can also be organized in some central places (aka. stores). You can use Tini Store (very simple, ~50 lines) or other state management solutions such as MobX, TinyX, ...

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…