Skip to content

Zustand 5 is too good. #2789

Open
Open
@enricoros

Description

@enricoros

Saying this is a piece of art is an understatement - this library is in the upper echelon with things like Zod, tRPC or even Typescript itself or linters. Thank you Poimandres, @dai-shi .

I ported my app to 5.0 (clean, without use-sync-external-store), and couldn't be happier of the results.

  • in particular removing the cause of 'recursion' errors (if you know you know) has added stability to states and made the app faster and more resilient, and proved a great investment for UX!

I couldn't find a way to comment on the release itself, so here is to you!
🎊 Congrats to the Zustand team!!! 🥇

(and you can safely close this ticket :)

Activity

dai-shi

dai-shi commented on Oct 14, 2024

@dai-shi
Member

So nice to hear that! (Let's keep this open for a while.)

sagarpanchal

sagarpanchal commented on Oct 16, 2024

@sagarpanchal

@dai-shi My comment could be off-topic.

Initially, I believed that zustand was React specific because the create returned a hook.
But zustand is very good with vanilla JavaScript. The ability to create stores using createStore and use with React or just JavaScript and DOM is outstanding. I am used to a pattern where I create stateful services (like sdk) for front-end that would return store, actions and selectors and they could be paired with JS or React. Subscriptions also helped me avoid using useEffect when UI is not a concern with the effect.

lemondreamtobe

lemondreamtobe commented on Oct 25, 2024

@lemondreamtobe

Saying this is a piece of art is an understatement - this library is in the upper echelon with things like Zod, tRPC or even Typescript itself or linters. Thank you Poimandres, @dai-shi .

I ported my app to 5.0 (clean, without use-sync-external-store), and couldn't be happier of the results.

  • in particular removing the cause of 'recursion' errors (if you know you know) has added stability to states and made the app faster and more resilient, and proved a great investment for UX!

I couldn't find a way to comment on the release itself, so here is to you! 🎊 Congrats to the Zustand team!!! 🥇

(and you can safely close this ticket :)

absolutely agree!.I think zustand is the most perfect store library for React.~ I love it!

csvan

csvan commented on Nov 7, 2024

@csvan

Indeed, thank you so much for this lib <3

rg-lahcene

rg-lahcene commented on Nov 18, 2024

@rg-lahcene

I will screenshot this issue in my ADR for choosing zustand as state managment library :D

Sharqiewicz

Sharqiewicz commented on Nov 19, 2024

@Sharqiewicz

❤️

zxkws

zxkws commented on Dec 3, 2024

@zxkws

Saying this is a piece of art is an understatement - this library is in the upper echelon with things like Zod, tRPC or even Typescript itself or linters. Thank you Poimandres, @dai-shi .
I ported my app to 5.0 (clean, without use-sync-external-store), and couldn't be happier of the results.

  • in particular removing the cause of 'recursion' errors (if you know you know) has added stability to states and made the app faster and more resilient, and proved a great investment for UX!

I couldn't find a way to comment on the release itself, so here is to you! 🎊 Congrats to the Zustand team!!! 🥇
(and you can safely close this ticket :)

absolutely agree!.I think zustand is the most perfect store library for React.~ I love it!

Me too!

radaco99

radaco99 commented on Jan 12, 2025

@radaco99

When I realized I needed state management for my app, my first thought was, "Oh no, here comes Redux again!" Back when I was learning React, Redux was pretty much the only option. But then I discovered Zustand—and wow, what a game-changer!

It's so simple that I was initially skeptical, but nope, it’s rock solid! I rarely leave comments or feedback, but this library is truly in a league of its own. Incredible work, team—well done! 👏

94Rabbit

94Rabbit commented on Feb 7, 2025

@94Rabbit

I also used zustand by chance and it was like a treasure 😂。

KrishnaPG

KrishnaPG commented on Apr 10, 2025

@KrishnaPG

Not sure if this is the right forum, but wondering: pmndrs has multiple state management libraries: valtio, zustand, koota and jotai.

All seem to be pretty much targeting the same functionality.

Q:

  1. It is not clear why there exists multiple, and there does not seem to be any documentation comparing and contrast these with each other (specifically, when to use what, pros and cons etc.)
  2. Or is it more like one of these is going to replace all the others?

It is really confusing to see multiple packages of same functionality under one brand. It would be great if they all either get merged into one or others get marked as deprecated and one remains.

dai-shi

dai-shi commented on Apr 10, 2025

@dai-shi
Member
KrishnaPG

KrishnaPG commented on Apr 10, 2025

@KrishnaPG

Thank you @dai-shi Done: #3077

ipnon

ipnon commented on Apr 23, 2025

@ipnon

zustand makes React bearable 🧸

In all seriousness it is like LiveView in that it gets very near to an ideal way to write stateful client programs. And in such a simple way too. Us mortal programmers are not meant to keep endless waterfalls of props and callbacks in short-term memory.

I knew zustand was going to be good when I saw so much praise and so little documentation! A library that barely needs explanation will rarely let you down.

Thank you for your excellent work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @enricoros@dai-shi@csvan@KrishnaPG@sagarpanchal

        Issue actions

          Zustand 5 is too good. · Issue #2789 · pmndrs/zustand