I've watched many Zustand/TypeScript vids but didn't really catch on and actually work with code until now. I didn't follow your examples but was able to imeplement it all into some code of my own, and it all works. Thanks!
Great course. One thing is missing is explaining selectors. Without them. when you de-structure the store and use the de-structured values in code. they will cause re-render to other values as well. For example if you change username in user store it will cause a re-render to the email as well. But when you use selectors it prevents not essential re-renders :)
@Maks-fc7kv Context API is not a state management system and was never intended to be used in such a way. It does not solve the problem of isolating state away from the components as you still need to define it as the Provider level and pass it down. At scale, it ends up with the same original problem. React Query doesn’t have proper APIs to grab and update data from the store. You also said you don’t need a state management library but React Query actually claims to be one, by their definition……
@@ansonthedev Thank you very much for your reply. I am learning your react-nest chat application. It is really helpful. What you do is very meaningful.
i used a context hook to navigate information between components in my job and i don't like this approche beacuse most of the time it repeat and more code. but this video help me to fix this problem thanks
![[#2024MAMA] BIGBANG (빅뱅) - 뱅뱅뱅 (BANG BANG BANG) + FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/EQsYfiPR9uM/mqdefault.jpg)
I've watched many Zustand/TypeScript vids but didn't really catch on and actually work with code until now. I didn't follow your examples but was able to imeplement it all into some code of my own, and it all works. Thanks!
we have project that were using zustand and this video just came out, thank you brother!!
Great course. One thing is missing is explaining selectors.
Without them. when you de-structure the store and use the de-structured values in code. they will cause re-render to other values as well.
For example if you change username in user store it will cause a re-render to the email as well.
But when you use selectors it prevents not essential re-renders :)
WTH, I am just doing a project with Zustand & typescript and this video came out
Thanks a lot bro! Your Express.js tutorial was really helpful.
Thanks for the tutorial
This is amazing!!!!
Anson!! where the fu** have you been😆🤣🤣, i have missed you 💌💌
Bro ❤❤❤ glad you back.
Nextjs full course with project ❤❤❤ waiting 🎉🎉🎉
what version of zustand did you use?
Thx
❤ Best of the best
Contexts + React Query and you don't need any state management library in ~>90%.
@Maks-fc7kv Context API is not a state management system and was never intended to be used in such a way. It does not solve the problem of isolating state away from the components as you still need to define it as the Provider level and pass it down. At scale, it ends up with the same original problem.
React Query doesn’t have proper APIs to grab and update data from the store. You also said you don’t need a state management library but React Query actually claims to be one, by their definition……
Your video is great. Do you have the intention to make a systematic video that combines nest and next? Thank you again for your contribution
It could happen.
@@ansonthedev Thank you very much for your reply. I am learning your react-nest chat application. It is really helpful. What you do is very meaningful.
i used a context hook to navigate information between components in my job and i don't like this approche beacuse most of the time it repeat and more code. but this video help me to fix this problem thanks
Thats exactly what I would tell people who are debating between using context and state management solution.
React with TypeScript when?
Bruv thanks always on time.