No BS TS #26 - Typescript/React - Global State

[@jackh3242]

I've been using easy-peasy for global state in my react typescript apps with great results. It's very friendly and minimal!

[@jherr]

Sounds like my kind of state manager! :)

[@align2source]

These days I watch your channel whenever I have a snack while taking a break from my project! Actually much more entertaining than Netflix or HBO 💚🛸✨

[@jherr]

Wow! Netflix, ok. But HBO, with HOTD, wow! ;)

[@ApurvaShekhar-hn5or]

This helped me a lot. concise content.

[@jovanaj8365]

This series is a life saver!

[@miguelyoutube100]

Thanks for the great video.

[@1879heikkisorsa]

Awesome!

[@infisspablo8602]

Cool stuff

[@jamesvo3462]

good stuff

[@ivayloyankov8120]

I like it.

[@robx_001]

awesome

[@netvaibhav]

Thanks for the great video. react-use looks quite nice and minimal. How does it compare to Valtio?

[@jherr]

Valtio is a great state manager. But it's doing the observables thing. So it's really a different model, IMHO. This `createGlobalState` is a "spot fix" for when you need state that is ... global. So if you are doing the custom hooks thing, then this would be great for that. But if you are doing more of a state manager approach that is light on hooks, then Valtio or Zustand would be a good choice.

[@ДмитроСорока-г5ж]

Thanks!

[@AAquaticAApe]

Great series!

[@higorcoimbra6591]

Can you please clarify why the previous solution, using useReducer, was not globally available?

[@denilsoncosta9837]

normally for this use case i prefer zustand to handle global states. I use for exemple in multi-language cases.

[@jherr]

:) Zustand is coming up. It's a personal favorite as well.

[@denilsoncosta9837]

@@jherr I can´t wait!

[@PostMeridianLyf]

I've been doing Android dev for 2 years and came over to build my first react app. Is it really worth all the hassle to configure global contexts or would it be easier to use a viewmodel? In kotlin I can use a view model with live data that triggers changes in other fragments. I'm not sure if there is an equivalent in React/Ts? I hate being stuck on such a simple issue lol.

[@jherr]

useState/useReducer would be the equivalent in React.

[@PostMeridianLyf]

@@jherr I actually figured that out from another video of yours. You are the man! The react-use library set me straight! When I am no longer poor I will buy you a beer!

[@PostMeridianLyf]

@@jherr I thought I had replied to this already but I guess it did not save. Thank you so much Jack! I learned more about react-use from another one of your videos and it really helped out! One day when i am not poor I will buy you a beer!

[@cas818028]

Would useContext be better suited for this example?

[@jherr]

Everything has pros/cons, but you can be the judge directly if you watch the useContext implementation in the previous episode - kzbin.info/www/bejne/haTIeGulhpeFeq8

[@piotr5014]

I'm doing all the same(I've even copied App and useTodos) and i got an error about invalid hook call when using useGlobalTodos(with no VSC problems appeard)

[@jherr]

Feel free to jump on the Discord server and see if you can get some help on there.

[@aryan7069_]

I have a question Is not changing state with setState(prev => new) more preferred than setState(new) Then why are you changin states like this

[@jherr]

I'm hearing more and more that setState(prev => new) should be used unless absolutely necessary, I'm not sure who is saying that, but it's not me and it's not the React documentation (read the section entitled "Is using an updater always preferred? "). Speaking more generally, if you hear advice that is super boolean (e.g. "Never do it like this."). Or you get advice that is clearly not supported by the official documentation. Then it's probably not great advice.

[@adamlerman4173]

comment for the algorithm XD

[@mortezatourani7772]

8:06 The main list didn't update!!! Something went wrong

[@jherr]

Hot refresh. Ugh.

[@hbela1000]

Thanks for the great video.

[@moretimeproductions]

Awesome!