NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
A variant of ValueNotifier that helps you better manage phases of asynchronous operations.
Last release 9 months ago
08 Jan 2026
Ships fairly regularly
a new release about every 3 months
Nearly every release is documented
notes for 18 of 18 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
18 releases · first in 2022
One column per quarter.
Fix issue where updateType() didn't correctly detect type returned by wrapped higher-order functions.
updateType() didn't correctly detect type returned by wrapped higher-order functions.Remove deprecated updateOnlyPhase() from AsyncPhaseNotifier.
updateOnlyPhase() from AsyncPhaseNotifier.onComplete in updateType() now receives data, matching other methods.onWaiting now triggers only on start and receives data.
Deprecate updateOnlyPhase() in favour of updateType().
updateType() to AsyncPhaseNotifier for more flexible phase control.updateOnlyPhase() in favour of updateType().updateType() must return a value. (Add return or use
an arrow function =>).AsyncPhase, the notifier's value reflects
that specific phase.AsyncPhase (e.g. from a repository)
and it results in an AsyncError, you can now simply return that phase to
apply the error state to the notifier, without needing to call rethrowError().onComplete:
onComplete callback no longer receives the result data, as the data
remains unchanged.Bump async_phase version to 0.6.0.
onWaiting, onComplete and onError callbacks to update() and updateOnlyPhase().Add support for replacing notifier in AsyncPhaseListener.
AsyncPhaseListener.Avoid the error that occurred when update() ended after AsyncPhaseNotifier was disposed.
runAsync().update() ended after AsyncPhaseNotifier was disposed.update() and remove unnecessary reassignment of new phase to value.- Update async_phase to 0.5.2.
- Update async_phase to 0.5.1.
See the change log of package:async_phase for details and non-breaking changes.
AsyncPhaseNotifier constructor to be no longer optional.runAsync() to no longer receive current data.runAsync() from FutureOr to Future.
runAsync() in favour of new update().// Before
final notifier = AsyncPhaseNotifier<int>();
// After
final notifier = AsyncPhaseNotifier<int>(0);
// Before
class MyNotifier extends AsyncPhaseNotifier<int> {
MyNotifier();
}
// After
class MyNotifier extends AsyncPhaseNotifier<int> {
MyNotifier() : super(0);
}
// Before
await runAsync((data) => yourFunc(data));
// After
await update(() => yourFunc(data)); // `data` here is a new getter for `value.data`.
AsyncPhase.from() is now Future instead
of FutureOr.error and stackTrace of AsyncError is now non-nullable.update() to AsyncPhaseNotifier as a replacement of deprecated runAsync().updateOnlyPhase() to AsyncPhaseNotifier,data getter for value.data to AsyncPhaseNotifier.runAsync().
AsyncError had stale data if fallback data was not provided and
value.data was updated while the callback was executed.- Upgrade async_phase to 0.4.0.
Improve comments and tests to reduce risk of nullability mistakes.
data in README.copyWith() added to AsyncPhase at async_phase 0.3.2 is available.
copyWith() added to AsyncPhase at async_phase 0.3.2 is available.dispose() of AsyncPhaseNotifier.listenFor().Rename listen() to listenFor().
listen() to listenFor().listen() method.
listenFor() takes several callback functions, each of which corresponds to a certain phase.Raise minimum Flutter SDK version to 3.10.0.
Change listeners to listen to not only errors but also changes to waiting/complete phases.
listenError() to listen() and add callbacks.AsyncErrorListener to AsyncPhaseListener and add callbacks.
BuildContext is not passed to onError any more.listen() is not used.Fix description on AsyncPhaseListener.
There are some breaking changes.
value setter that was needlessly complex and possibly led to wrong behaviours.- Initial version.
Your coding agent can read these notes before it upgrades. Set up the MCP server →