effector-react VS pinia

In its docs, Astro recommends nanostores, but I’ve used effector in the past. And LOVED IT. So I’ve used it for this project as well.

I've been using effector, together with the apollo-client for the last few years and, while it works, it's completely detached from the actual screens. In other words, you need to fetch everything (at startup) you might use at some point and it stays in the memory for the entire duration of the session. Error handling is also tricky as you need to explicitly subscribe to the specific error stores in order to render them. And, if something goes wrong, it's tricky to tell what data is actually used in the current screen, so it's almost impossible to do the Retry efficiently. OTOH the screens are nice and simple - no spinners, the data is just there, thus the app feels (and is) fast.

Actually, Svelte uses Effector for state management under the hood. You can read more about it here: https://effector.dev/. It also has bindings for other frameworks including React, Vue and Solid. Effector is a little not beginner-friendly, but once you truly understand it, Effector becomes a very powerful.

A state-management library.

Effector it is the another way to create state and business logic for your frontend application.

https://effector.dev/ here you go

Then I found Effector which seems to have the same features, and SolidJs support.

Where’s effector?

https://ngneat.github.io/elf/ https://effector.dev/

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