tc39/proposal-signals

A proposal to add signals to JavaScript.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on August 14th, 2023
Open Issues & Pull Requests: 114 (+0)
GitHub issues: Enabled
Number of forks: 74
Total Stargazers: 4,189 (+0)
Total Subscribers: 139 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.3 hours
Mean response time: 53.9 days
90th percentile: 172.7 days
Tracked items: 77

Most active contributors

Sign in to see contributor activity.

How this project is maintained

79% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 48
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 642 days
Stale 30+ days: 43
Stale 90+ days: 42

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • possible future features (9)
  • documentation (5)
  • good first issue (4)
  • prototyping (4)
  • Semantic details (3)
  • bug (2)
  • initial prototype (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Proposal Signals is a TC39 proposal that aims to add signals to the JavaScript language.

Signals provide a primitive for reactive programming, allowing developers to create values that automatically notify dependents when they change. The proposal addresses the problem of managing state updates and side effects in JavaScript applications by introducing a standardized mechanism for tracking dependencies and propagating changes. Rather than requiring applications to implement their own reactivity systems, signals would be built into the language itself, enabling more efficient and predictable state management across different frameworks and libraries.

Developers considering this proposal should understand that it represents a language-level feature under active standardization rather than a library ready for production use. The proposal is most relevant for framework authors and library developers who currently implement their own reactivity systems, as well as for applications that would benefit from a common, interoperable approach to reactive programming. By standardizing signals at the language level, the proposal aims to reduce duplication across the ecosystem and allow different tools to work together more seamlessly around a shared reactivity model.

The project shows active engagement from the TC39 committee and the broader JavaScript community, with ongoing discussion and refinement of the proposal's design. Development involves iterative feedback from stakeholders, with the proposal undergoing evaluation and revision as part of the formal standardization process.