riverpod-containers

To set up Riverpod state management in Flutter, you use a `ProviderScope` widget at the root of your application. This widget creates and manages the `ProviderContainer`, which is where all Riverpod state is actually stored and accessed.

`ProviderContainer` works in Dart by acting as the core storage mechanism for Riverpod state when Flutter widgets are unavailable. It allows you to manually read providers, manage state lifecycle, and configure overrides and observers independently.

You write unit tests for Riverpod providers by using the `ProviderContainer.test()` method. This creates an isolated container that allows you to override specific providers and reliably verify state logic without needing a full Flutter widget tree.

Yes, you can configure overrides and observers directly at the `ProviderContainer` or `ProviderScope` level. This allows you to inject mock dependencies for testing or monitor state lifecycle changes globally across your application.

`ProviderScope` is a Flutter widget that creates a `ProviderContainer` for the widget tree, while `ProviderContainer` is the underlying Dart class where Riverpod state is actually stored. `ProviderContainer` can also be used directly for testing or non-Flutter Dart apps.