Better to just use {count} instead of {count.value} in your jsx part, because it doesn’t cause the whole component to rerender on change, it just updates that placeholder
Do Preact signals work with React version 18, I can't remember who's video I watched but I thought they said that signals do not work with React concurrent mode. I might of heard that wrong. They do look very good though, seems to solve some of React's problems.
Yeah, they definitely solve the prop drilling and state management issues. Even out of the components’ scope. I tested it with the latest version of React in this video. I haven’t specifically tested with a deep dive in concurrent mode yet
@@CodeWithAhsan Thanks for replying, sorry but could you tell me a brief overview of what React concurrent mode is. I am new to web development and the coding bootcamp I am on hasn't covered what concurrent mode is.
It updates the value like "count.value++". Does it mean it does update the value in a mutable way? what if we have a complex data like var foo = signal({ a: 1, b: 2, d : { e: 5 } }) should I have to update the original object like foo.value.d.e = 10 // update the e value ??
Signals can be nested. So in this example it would be: signal({ a: signal(1), b: signal(2), d: { e: signal(5) } }) Or, if you're planning on updating "d": signal({ a: signal(1), b: signal(2), d: signal({ e: signal(5) )} }) // Wrapped "{e:signal(5)}" into another signal ---- I recon, this approach will lead to a lot of pain when trying to manage complex states.
Shameless plug, but if you want Signals to scale like a full state management solution, you grab preact-signal-store. Currently it only supports Preact, but I'm working on converting it to a monorepo that exports a package that works with React as well.
Hey there. I use davinci resolve for editing my videos :) I had the overlay (with green screen) created from a video editor. I just use that in all videos now.
![MV วิถีชีวิตใต้ - ผา อัยย๊ะ [Official MV HD]](http://i.ytimg.com/vi/nODlkOUu9B0/mqdefault.jpg)
![State management with Preact Signals - Getting started with the new package [2022] (Preact/React)](/img/n.gif)
Do you think this is better than Redux? Or will you keep using Redux? Or is there a different State Management library that you prefer?
I prefer angular forever 😍
@@greekapostle4548 hahah!! For sure!!! Angular FTW
It will be a bit difficult to shift from reduced 😊
Changes are always difficult. True
No need for redux with the native components built into React for a while now.
Better to just use {count} instead of {count.value} in your jsx part, because it doesn’t cause the whole component to rerender on change, it just updates that placeholder
Is this with the AuthSignals the recommended way to store the values?
Nice Video. I'm trying to use signals, but it seems they don't work with `react-navigation` ?
What error did you face with signals and React navigation ?
Do Preact signals work with React version 18, I can't remember who's video I watched but I thought they said that signals do not work with React concurrent mode. I might of heard that wrong.
They do look very good though, seems to solve some of React's problems.
Yeah, they definitely solve the prop drilling and state management issues. Even out of the components’ scope.
I tested it with the latest version of React in this video. I haven’t specifically tested with a deep dive in concurrent mode yet
@@CodeWithAhsan Thanks for replying, sorry but could you tell me a brief overview of what React concurrent mode is. I am new to web development and the coding bootcamp I am on hasn't covered what concurrent mode is.
Hi...i love ur video could you tell me how u edited, mostly putting ur social handle in d video. Thanks
It updates the value like "count.value++". Does it mean it does update the value in a mutable way?
what if we have a complex data like
var foo = signal({ a: 1, b: 2, d : { e: 5 } })
should I have to update the original object like foo.value.d.e = 10 // update the e value ??
Signals can be nested.
So in this example it would be: signal({ a: signal(1), b: signal(2), d: { e: signal(5) } })
Or, if you're planning on updating "d": signal({ a: signal(1), b: signal(2), d: signal({ e: signal(5) )} }) // Wrapped "{e:signal(5)}" into another signal
----
I recon, this approach will lead to a lot of pain when trying to manage complex states.
First time in my life where library(@preact/signals-react
) is not working
Shameless plug, but if you want Signals to scale like a full state management solution, you grab preact-signal-store. Currently it only supports Preact, but I'm working on converting it to a monorepo that exports a package that works with React as well.
Hey! That’s awesome 👏
Wow! React has caught to Vue.
Looks like it.
And we have Angular introducing signals soon too. Exciting times!
great content
Thanks 🙏
Maybe add which signals package to install. Not sure why you skipped that.
Hi Ahsan, can you please share the source code on github or something similar. I would be very greatful.
Hi...i love ur video could you tell me how u edited, mostly putting ur social handle in d video. Thanks
Hey there.
I use davinci resolve for editing my videos :) I had the overlay (with green screen) created from a video editor. I just use that in all videos now.
Okay thank you
Have a second question. I tried coding along but I got stuck it not working or updating I use react18 I don't know why.
Thank you