visx VS zustand

Official Website: https://airbnb.io/visx/

Website: Visx GitHub Page

Visx is a React-based library used for constructing data visualizations. It comprises a set of reusable, low-level visualization components that merge the power of D3 for data transformation and calculations with the benefits of React for updating the DOM.

Lol we migrated away from Nivo to Visx. Nivo is pretty cool but we're big fans of Visx due to how composable it is.

You could probably use this as a starting point to anchor it - there's a CodeSandbox link (which is a bit busted due to react-spring though) and I think you may just need to change the direction to "column."

Best one for React is VISX which is built on top of D3.js.

If you work in React and like this approach it's hard to go past Visx - https://airbnb.io/visx

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

I tried using skipHydration inside my zustand store based on their docs, then rehydrating it inside my modal. So far im getting the same errors. https://github.com/pmndrs/zustand/blob/main/docs/integrations/persisting-store-data.md

Reducer-based: requires dispatching actions to update a big centralised state, often called a “single source of truth”. In this group, we have Redux and Zustand.