riverpod-containers

Manage Riverpod state in isolated tests by creating a disposable ProviderContainer.test() instance in pure Dart, allowing you to read providers and override state without needing a Flutter widget tree.

ProviderScope is a widget that wraps your app at the root to create and expose a ProviderContainer, providing the underlying state storage that holds and distributes Riverpod provider state to the widget tree.

Yes, you can configure container overrides and observers when setting up your ProviderContainer, allowing you to customize and monitor provider behavior during testing in non-UI contexts.

ProviderScope is the Flutter widget that exposes a ProviderContainer to the widget tree, while ProviderContainer is the actual object that stores provider state, which can also be used independently in pure Dart tests.

Yes, you must wrap your app with ProviderScope to expose a ProviderContainer, enabling the use of ref.watch and ref.read to access and manage Riverpod state throughout the widget tree.

Isolate state across tests by creating separate, disposable ProviderContainer.test() instances for each test, ensuring that state storage and overrides do not leak between test cases.