tc39/proposal-signals

We need your help to develop Signals!

Open

#95 opened on Apr 1, 2024

View on GitHub
 (5 comments) (21 reactions) (0 assignees) (71 forks)github user discovery
good first issue

Repository metrics

Stars
 (4,125 stars)
PR merge metrics
 (PR metrics pending)

Description

There's a lot that you all can do to help, including:

  • Try out signals within your framework or application
  • Improve the documentation/learning materials for signals
  • Document use cases (whether it's something the API supports well or not)
  • Write more tests, e.g., by porting them from other signal implementations #70
  • Port other signal implementations to this API
  • Write benchmarks for signals, both synthetic and real-world application ones #71
  • File issues on polyfill bugs, your design thoughts, etc.
  • Development reactive data structures/state management abstractions on top of signals
  • Implement signals natively in a JS engine (behind a flag/in a PR, not shipped!)

Contributor guide

Research direction
Pick one of the listed tasks (e.g., improving documentation, writing tests, porting implementations). Start by reading the existing signal polyfill and the proposal document to understand the API. Then make a small contribution, such as adding a test or clarifying a documentation section.
Tech stack
javascript
Domain
developer experience
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85