riverpod-refs

To read and watch Riverpod provider states in Flutter, you use ref methods to interact with providers, allowing widgets to access state and rebuild automatically when observed data updates.

Managing Riverpod provider lifecycle involves using callbacks like onDispose and onCancel to trigger proper resource cleanup, ensuring that controllers and streams are safely discarded when they are no longer needed.

You can listen to and invalidate Riverpod providers by utilizing ref methods to subscribe to state alterations and manually force provider re-evaluation or refresh stale data streams within your application.

Yes, Riverpod ref supports refreshing provider states dynamically by invoking ref.refresh, which forces the provider to recreate its current state and fetch new data while properly handling previous resource disposal.

Use ref.watch in Flutter state management to rebuild widgets on provider changes, whereas ref.listen should be used to trigger side effects like navigation or showing modals without rebuilding the widget tree.