A proposal to add signals to JavaScript

Re:A proposal to add signals to JavaScript by Pufferbo on Sunday March 31, 2024 @07:58PM (#39889441)

You don’t need to pass a Preact signal as a prop to get reactivity. If you’re using Preact, signal references will make your component reactive by default, and if you’re using React you can introduce reactivity by way of the useSignals hook or a Babel plugin. (1)

React signals have become my go to state management tool. So easy to use and very flexible.

1: https://www.npmjs.com/package/@preact/signals-react

[ Parent | on HN ]

Re:A proposal to add signals to JavaScript by andrewstuart on Sunday March 31, 2024 @08:15PM (#39889526)

>> React signals have become my go to state management tool.

I've ditched almost all state in my React apps except state local to the component.

Custom events do all the work for passing information around the application and directing activity.

What do signals give me that events do not?

[ Parent | on HN ]

Re:A proposal to add signals to JavaScript by Pufferbo on Sunday March 31, 2024 @09:33PM (#39890032)

I’m also a fan of local state, but there are some cases where it makes sense for a bit of global state - mainly user context.

However you can use signals for local state as well and they work amazingly. Being able to assign a new value to a signal without having to go though a setter is a way cleaner pattern, in my opinion.

The other use cause is for communication between micro frontends. It’s so nice to just be able to import/export a signal and get its reactivity. Before them, I would create a pub/sub pattern and that’s just not as clean.

[ Parent | on HN ]