mit einem Klick
update-examples-dependencies
// Update all the `./examples` dependencies to the latest repository/third-party versions and fix any compiler or analysis issues.
// Update all the `./examples` dependencies to the latest repository/third-party versions and fix any compiler or analysis issues.
Highly optimized Flutter UI bindings and GPU rendering for reactive signals.
Comprehensive hook utility functions integrating reactive signals seamlessly with flutter_hooks.
Comprehensive reactive state hooks for integration with flutter_hooks.
Standardized compiler diagnostics, static analysis lints, and automated IDE quick-fixes.
Review the current Jaspr docs, audit source code doc comments, edit the source code, and run the generator script to verify docs updates.
Detailed guidelines, patterns, and rules for migrating codebases from signals.dart version 6.x to version 7.x.
| name | update-examples-dependencies |
| description | Update all the `./examples` dependencies to the latest repository/third-party versions and fix any compiler or analysis issues. |
This skill provides a systematic and automated workflow to update dependencies in all Dart/Flutter examples located in the ./examples directory and fix any code compilation, deprecation, or linter warnings that arise.
Ensure all ./examples packages are upgraded to target the latest core package versions (e.g. signals) of the repository, run a full pub upgrade on third-party dependencies to prevent stale locks, and repair any broken code or deprecation warnings under analysis.
Locate the helper script at scripts/update_dependencies.dart or within this skill's scripts directory:
dart run .agents/skills/update-examples-dependencies/scripts/update_dependencies.dart
This script will:
packages/signals/pubspec.yaml to detect the current package version of signals.pubspec.yaml files inside ./examples/.signals dependency version constraint with the exact latest version constraint (e.g., ^6.3.1).flutter pub upgrade or dart pub upgrade on each example package.After upgrading individual package pubspecs, link the workspace packages and ensure they resolve successfully by running:
melos bootstrap
With all packages upgraded, run static analysis to check for breaking changes or new warnings:
melos run analyze
For any deprecations (such as v6 to v7 API transitions or external package changes):
migration-6-to-7 if migrating to v7).melos run analyze succeeds cleanly.