riverpod-migration

To migrate Riverpod StateNotifier to Notifier, open the matching migration guide in the reference folder and apply the recommended changes to modernize your provider patterns and update provider types.

The best way to upgrade Riverpod from 0.14 to 1.0 is using the version-transition playbooks and CLI-assisted upgrades to ensure safe, reproducible changes across your modules.

Yes, you can use CLI tooling guidance to migrate ChangeNotifier to AsyncNotifier, which simplifies state management and improves error handling using AsyncValue.

Yes, Riverpod migration supports moving initialization logic to the build method and provides guidance on correct usage of ref.watch and ref.notifier for updated providers.

You validate Riverpod migration changes in large apps by running tests after applying the step-by-step migration guides to ensure correct behavior across modules.

You should avoid using the riverpod migrate CLI command when your project does not use StateNotifier or ChangeNotifier, as the migration guides specifically target these provider patterns.