clean-code-typescript VS zustand

If the problem is that, u can use the https://github.com/labs42io/clean-code-typescript repo, they have great examples and each example has a how to use

Clean code typescript

I understand why people complain about it, but honestly, I think the ratio of good advice to bad advice is 9:1. For example, if you look at this summary of Clean Code (adapted for TypeScript), I think most people will agree that 90% of the guidelines are generally good ideas.

Also, I feel like using typescript helps to keep the code clean. Martin's book has mentioned already multiple times, but here's a typescript adaptation of it: https://github.com/labs42io/clean-code-typescript

The general ideas are fine, but the examples are pretty outdated. For modern SPA, CSS naming has become largely obsolete. A lot of the JS code shows the principles it is supposed to well but sadly includes other cruft.

Here's a guide I would recommend instead: https://github.com/labs42io/clean-code-typescript

https://github.com/labs42io/clean-code-typescript https://github.com/torokmark/design_patterns_in_typescript

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

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