riverpod-eager-initialization

To eagerly initialize Riverpod providers at Flutter app startup, watch the target providers within a root Consumer widget. This forces the providers to load immediately rather than waiting for first use in the UI.

Handle async loading and error states during Riverpod initialization by using AsyncValue.requireValue. This ensures your application gracefully manages asynchronous data availability before the main UI is rendered.

You should force a Flutter provider to initialize before the app loads when critical data like authentication tokens must be available immediately. This prevents UI rendering delays or errors due to missing initial data.

Yes, Riverpod supports loading authentication tokens before rendering the main UI by eagerly initializing the relevant provider. You can watch the provider at the root of your app to ensure tokens are ready.

Your Riverpod provider initializes late because Riverpod uses lazy initialization by default. To fix this, watch the provider in a root Consumer widget to force eager initialization at application startup.