Skip to content

Issues: tc39/proposal-signals

We need your help to develop Signals!
#95 opened Apr 1, 2024 by littledan
Open 5
Get in touch with us about Signals
#96 opened Apr 1, 2024 by littledan
Open
Integration Stories
#116 opened Apr 1, 2024 by EisenbergEffect
Open 8
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

119 Open 44 Closed
119 Open 44 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

The signal graph protocol should be exposed for novel implementations
#258 opened Jan 23, 2025 by DavidANeil
Add utility for tracking Signal reads in a callback
#257 opened Jan 23, 2025 by DavidANeil
Signals should be able to efficiently return to an old value
#256 opened Jan 22, 2025 by DavidANeil
3
Computed signals should expose a callback that is invoked when a value is dropped
#255 opened Jan 22, 2025 by DavidANeil
Consumers can unexpectedly hold unused memories in dependencies
#254 opened Jan 22, 2025 by DavidANeil
Allow Computeds to eagerly recalculate to prevent dirty propagation
#253 opened Jan 22, 2025 by DavidANeil
Consumers should be held weakly to allow all nodes to be live
#252 opened Jan 22, 2025 by DavidANeil
7
watcher.watch(signal) and Signal.subtle.watched callback when signal is not up to date
#251 opened Jan 15, 2025 by divdavem
2
Signal.State.prototype.update to update values using callbacks
#249 opened Dec 24, 2024 by Ocean-OS
4
Updates around this proposal
#247 opened Dec 3, 2024 by WebReflection
7
Signal should be replace with Reactive
#246 opened Nov 19, 2024 by hansschenker
1
React library that supports JavaScript Signals standard proposal
#244 opened Oct 28, 2024 by finom
2
Add Signal.Buffer alongside Signal.State and Signal.Computed
#243 opened Oct 26, 2024 by dead-claudia
Rational: why no effects out of the box?
#242 opened Oct 7, 2024 by NullVoxPopuli
3
Subscription to a collection
#241 opened Oct 3, 2024 by DanielHeath
2
Add batching and batched effects to solve the interoperability / multi-actor problem with batches
#239 opened Sep 6, 2024 by justinfagnani
2
Volatile sources in the computation graph
#237 opened Aug 12, 2024 by PsychoLlama
7
Clarification request: (Semantic) equivalence of push-only and push/pull models
#233 opened Jul 17, 2024 by dehmer
1
Refactor Signal Class Hierarchy for Improved Type Safety and Extensibility
#230 opened Jun 18, 2024 by DeepDoge
6
Signal.subtle.watched/unwatched is not sufficient, we need to be notified when a signal is used (even without a watcher)
#227 opened Jun 12, 2024 by divdavem
5
How to allow set in a Computed to trigger a recomputation synchronously (until the result is stable)
#226 opened Jun 7, 2024 by divdavem
7
Do the benefits of signals as a language feature outweigh the costs of solidification into a standard?
#220 opened May 12, 2024 by devmachiine
30
cross realm signals
#219 opened May 8, 2024 by mhofman
1
Shorthand idea: false instead of () => false for equals
#218 opened May 7, 2024 by NullVoxPopuli
5
Really bad unwatch performance (3000%)
#215 opened Apr 30, 2024 by lifeart
2
ProTip! Type g i on any issue or pull request to go back to the issue listing page.