State management with Preact Signals - Getting started with the new package [2022] (Preact/React)

[@bufootballa]

Excellent first look at signals! Just randomly found your channel and subscribed after watching. Good luck with the channel as you have an excellent way of explaining while you code through things! Can't wait to see more of your content!

[@codingwithrobby]

Appreciate the kind words!

[@AtRiskMedia]

great vid. (i had to shield my eyes from the light mode tho). more preact + signals content would be awesome

[@ivansativ5450]

this is neat how-to video, I'd appreciate if you'd compare the performance to a signal-less React app of the same structure as the motivation of using signals is performance improvements

[@MarkConstable]

Preact + signals in Fresh Deno would be great.

[@meherajsheikh4488]

Please make a video on pre-rendering & serviceWorkers & ssg & ssr in preact....thank you

[@MrBl0m]

Also thank you for the video :) . Can you please share your vs code plugins for the auto import thank you

[@RasmusSchultz]

15:05 something is wrong here - notice the count on the console? I think you're scheduling another effect with every change, like they're stacking up and never get cleaned up...?

[@codingwithrobby]

Good catch. I'm guessing that it's triggering twice because of the useComputed, but this is definitely something I should look into.

[@MrGarkin]

​@@codingwithrobby it triggers extra time on each render. In the end it's actually called 8 times pre click. Don't call `effect()` inside render function directly. Wrap it using hooks API and don't forget to dispose correctly.

[@omereker8824]

I dont know if there is a strict mode on preact like react has, but it might be rendering twice because of that

[@MrBl0m]

why use it as a local state instead of useState ?