react-flow VS zustand

Not sure if this is useful or fit your needs. I found out on the discord (https://discord.com/channels/457912077277855764/1078272116916494366) that ReactFlow for Svelte is in the works. https://github.com/wbkd/react-flow/discussions/2971

If you want something in react - https://github.com/wbkd/react-flow

And, with 12k stars on Github and an average weekly download of 161k, it's popular among devs. It has extensive community support that allows it to be maintained, thus giving users a long time assurance and scalability.

I recall coming across a GPT-3 "flow" application - it was a GUI where you could create prompts and inputs, then link them together to create a "chain". It reminded me of react-flow in the way that it looked.

State Management: Zustand

For our case, points 1 and 2 can help us provide a better way of handling updates in our rapidly updating application. I have used zustand for the application.

Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:

Zustand

Link: https://zustand-demo.pmnd.rs/

For more code examples visit the documentation here

Have you ever wanted to learn state-management but it felt so overwhelming to get started with Redux? Or maybe you're already using Redux but don't want to take the burden anymore? If so, you might want to take a shot at Zustand! Its an amazing state management library that's easy to get started and maintain in a long run. In this post, we'll dive into creating & sharing stores with this tiny Redux alternative.

You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?

Zustand