riverpod-from-provider

To migrate from Provider to Riverpod, replace your ChangeNotifierProvider with NotifierProvider and swap ProxyProvider dependencies for Riverpod's ref.watch. This allows incremental adoption so both state management solutions can run in parallel.

The Riverpod equivalent of ProxyProvider is using ref.watch inside your Notifier to read and combine other provider states. This approach provides compile-time safety and replaces context-based state access with direct provider dependencies.

Yes, you can run Provider and Riverpod in parallel during incremental migration. This allows you to transition your Flutter app's state management gradually by replacing individual ChangeNotifierProvider instances with Riverpod NotifierProvider over time.

When migrating to Riverpod, you handle automatic state disposal and parameterization using the autoDispose modifier and the .family method. These replace manual provider lifecycle management with automatic cleanup and parameterized state access.

You should switch from package:provider to Riverpod to gain improved testability and compile-time safety for your Flutter state management. Riverpod removes context-based state access dependencies, making your providers more robust and easier to test independently.

To replace context-based state access when moving to Riverpod, use ref.watch within ConsumerWidget or Notifier classes instead of Provider.of. This decouples state reading from the BuildContext, enabling safer and more testable state management.