riverpod-providers

To declare Riverpod providers, define top-level final variables using Provider or NotifierProvider variants, then consume them in Flutter widgets via ProviderScope using ref.watch or ref.read to access memoized state.

FutureProvider fetches and caches asynchronous data returning a single result, while StreamProvider listens to streaming data emitting multiple values over time. Both expose memoized state and handle loading and error states automatically.

Yes, Riverpod works in Dart-only environments by using a ProviderContainer instead of a ProviderScope. You can declare top-level providers and interact with their state via ref.read and ref.watch to share logic outside of Flutter widgets.

Use the autoDispose modifier when state should be destroyed when no longer listened to, preventing memory leaks. Use the family modifier to create parameterized providers that generate state dynamically based on input arguments.

AsyncNotifierProvider manages complex asynchronous state flows by encapsulating mutable state and async logic within a Notifier class. It exposes methods to update state and integrates with ref to read and watch other providers seamlessly.

NotifierProvider enables mutable state management by exposing notifier methods to update state directly, whereas a basic Provider only exposes read-only computed values. This makes NotifierProvider suitable for interactive state flows.