riverpod-eager-initialization

You can eagerly initialize Riverpod providers by placing a root Consumer under ProviderScope to watch selected providers, rendering the main app only after essential services are ready and handling loading or error states within the initializer.

Eager initialization in Riverpod ensures critical providers are prewarmed at startup. Use it for essential services like auth, config, or caches so the UI renders immediately without intermediate async loading screens across routes.

Handle loading and error states within a lightweight root initializer widget by watching the providers and using AsyncValue.requireValue, keeping the rest of the widget tree stable until the preloaded state is available.

Yes, you can prewarm critical services such as authentication, configuration, and caches by eagerly watching their providers in a root Consumer, ensuring they are fully available before the remainder of the app is used.

Intermediate loading screens appear when providers are lazily initialized. Eagerly initializing Riverpod providers at startup preloads state across routes, minimizing these async waits by ensuring essential services are ready beforehand.