a2ui-project / a2ui-project/a2ui
fix(dart): Widen preact_signals dependency constraint in a2ui_core to support ^7.0.0
- Dominant language
- TypeScript
- Stars
- 16.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 134
Description
### Description
Currently, `dart/a2ui_core/pubspec.yaml` pins `preact_signals` to:
```yaml
dependencies:
preact_signals: ^1.9.4
```
When integrating `a2ui_core` with modern signal-based architectures and Flutter packages that depend on `preact_signals: ^7.0.0` (such as `signals_core` 7.x or `bloc_signals`), Dart pub version solving fails:
```text
Because bloc_signals >=0.2.4 depends on preact_signals ^7.0.0 and a2ui_core >=0.0.1-dev002 depends on preact_signals ^1.9.4, bloc_signals >=0.2.4 is incompatible with a2ui_core >=0.0.1-dev002.
```
### Proposed Solution
Widen the dependency constraint in `dart/a2ui_core/pubspec.yaml` to:
```yaml
dependencies:
preact_signals: ">=1.9.4 <8.0.0"
# or: ^1.9.4 || ^7.0.0
```
The reactive signal primitives used by `a2ui_core` (`signal`, `computed`, `batch`) maintain full API compatibility across 1.9.x and 7.x.
Would the maintainers be open to a pull request with this change?
Contributor guide
Research direction
The file to edit is `dart/a2ui_core/pubspec.yaml`. Look for the `preact_signals` dependency line and change the version constraint to `>=1.9.4 <8.0.0` or `^1.9.4 || ^7.0.0`. Verify the change by running `dart pub get` in that directory to ensure it resolves. Done when the pubspec.yaml file is updated and the dependency constraint is widened.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100