pullstate VS crux

PullState - https://lostpebble.github.io/pullstate/

Pullstate. It's a lot like svelte's store.

And automatically, any components using uiStateStore.useState and watching the isSidebarOpen property will get updated, exactly the same as the normal useState hook - just shared.

It's so dead simple and has made complex app-building so much easier for me.

The one caveat is that if I have a component with many handlers, e.g. onClick, onMouseMove, onContextMenu, onMouseLeave, etc (and in some cases I do), components can get bloated. I haven't found a fix to that yet. But that's more an inherent issue with react than anything to do with state management.

[1] https://github.com/lostpebble/pullstate

Sounds like you're on the right track. React is very hire-able. Try out multiple store systems. The big one is react + redux. Then after you have some experience with that, try a simpler one like pullstate.

You could try out pullstate - its basically just global objects which you can mutate and which automatically update your state over your entire app, for whichever parts you have "pulled" the state into.

I built a simple router in about 50 lines: https://github.com/andyjessop/crux/blob/main/apps/dev/src/shared/router/router.service.ts

For comparison, I'm writing a front-end framework where the entire size (including router, data fetching/caching, state management) is less than the size of axios.

It's like looking in a mirror. This is exactly why I'm working on crux. Seeing as you have similar thoughts, I'd love to hear your feedback.

Immer's a cool library if you don't mind doing this at the top of every reducer: /* eslint-disable no-param-reassign */. I normally prefer some kind of immutable merge function, like this:

Wow, you've done an amazing job there. I prefer your syntax over RTKQuery, and I really like the idea of the queue. I'm implementing a similar kind of thing myself, except just for redux and not as fully-featured as your solution.

Yeah I get this. I would say two things. Firstly, this is aimed primarily at people who are already using Redux. And secondly (and more importantly), Redux itself is not inherently complex - you can write it in 20 lines of code - it's just that the accepted best practices add lots of boilerplate. I've addressed this in my createSlice library, which removes all but the most essential code from the config: https://github.com/andyjessop/crux/tree/main/packages/redux-slice

100% agree (both with your opinion and that it's controversial), that's why I'm working on my own framework that attempts to solve this issue: https://github.com/andyjessop/crux

I don't think there's an issue with boilerplate in Redux any more, especially with RTK's prevalence. I made my own createSlice that simplifies the creation of reducers and actions still further - it has an extremely straightforward API and is only 30 or so lines of code.

It's not ready for production yet (far from it), but here it is if anyone is interested in finding out more and/or contributing: https://github.com/andyjessop/crux