signals_flutter
7.1.0, released 6 months ago by rodydavis.com
Fine-grained reactive state management library for Flutter using signals.
WASM-ready
What it does
Provides fine-grained reactivity and surgical widget rendering based on Preact Signals. Automatically tracks dependencies and only computes or re-renders parts of the UI that change.
AI-written summary of version 7.1.0, based on the package's README and metadata. Report an inaccuracy
Use it when
- You want fine-grained reactivity without explicit state management boilerplate
- You want optimal UI rebuilds targeting only the specific widgets that depend on updated signals
Skip it when
- You prefer structured architectural patterns like BLoC or Riverpod
- Your project relies on legacy state patterns that have been deprecated in this library
Strengths
- Fine-grained reactivity with surgical rendering
- Lazy evaluation of signals
- Small and flexible API surface
Weaknesses
- Frequent breaking changes and deprecations across recent major versions
- Documentation depends heavily on external website resources
Setup
- Kind
- Flutter widgets
- Effort
- Low
- Code generation
- No
- Direct dependencies
- 1
Not documented
SignalWidget(builder: (context) => Text('${counter.value}'))Alternatives
Packages that do the same job and could replace signals_flutter.
Works with
Packages commonly used together with signals_flutter: ones it builds on, ones built on it, and its own family.
- signals_coresignals_flutter depends on itFine-grained reactivity library for modeling state and business logic in Dart.
- signalsBuilt on signals_flutterReactivity made simple. Do more by doing less. Supports Flutter and any Dart project including HTML/JS, CLI, Shelf Server, VM and more.
- bloc_signals_flutterBuilt on signals_flutterFlutter UI extensions, providers, and bindings for the bloc_signals state management library.