vuex VS Hookstate

Pinia is a relatively new state management tool for the Vue ecosystem. It is the new preferred state management tool recommended by the Vue core team replacing Vuex. Compared to Vuex, Pinia is type-safe by default (direct-vuex was needed to make Vuex type-safe), extremely lightweight, and modular by design (meaning you can create multiple stores instead of multiple modules inside one store, which optimises... - Source: dev.to / 12 days ago

Vue.js also offers built-in features like animation and state management through Vuex which serve a wide range of development needs. - Source: dev.to / about 2 months ago

I really liked the idea of how all the core Vue libraries are maintained by Vue team themselves, making Vue feels like an all-in-one package instead of infinite npm install to add multiple community/personally maintained repos which often caused issues because they don't blend together. And now Pinia will be officially replacing Vuex, making me doubt if it'll be as reliable as Vuex. Source: 11 months ago

Pinia. No discussion. Have you checked the Vuex website? It says Pinia is default. Https://vuex.vuejs.org/. Source: about 1 year ago

Vuex itself, tells you to not use it and use Pinia instead. Source: about 1 year ago

Avoid using complex state structures to make it easier to manage and debug. There are multiple libraries to help manage complex state management such as Redux, Hookstate, etc. - Source: dev.to / 6 months ago

As you stumble on this post and article, do check out one library not mentioned in this list: hookstate. I'm a big fan, the API is very simple and it offers lots of extendability options. Source: almost 2 years ago

I have been using Hookstate, curiously aanbidt never mentioned in lists like this. Source: almost 2 years ago

I've never understood why Hookstate (https://hookstate.js.org/) doesn't get more love. It's super-simple (no boilerplate), modern (hook-based), performant (works great for all size apps) and even works outside of components beautifully. It's somewhat similar to context, but more robust and feature-rich (because it's a true state management solution, which context really isn't meant to be). It's basically the only... Source: almost 2 years ago

If your data requirements aren't particularly mutating / don't mutate regularly then the newer context api would be your friend it essentially variable that is scoped to your react tree which components can subscribe to changes of, but it is important to know that: unfortunately the current useContext hook (and by extension the rest of the context api) doesn't have any means of specifically "choosing" /... Source: almost 2 years ago