skills.rest
masssi164
masssi164COMMUNITY
Explore all skills by this author →
GitHub

riverpod-3-0-migration

Migrate Riverpod 2.0 codebases to Riverpod 3.0 APIs and imports.

Updated Mar 28, 2026
Search Tags:#migration#upgrade#flutter#breaking-changes#riverpod#notifier
One-click install
npx skills add https://github.com/masssi164/weave --skill riverpod-3-0-migration-masssi164
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: riverpod-3-0-migration
Source: https://github.com/masssi164/weave/tree/main/.agent/skills/riverpod-3-0-migration
Command: npx skills add https://github.com/masssi164/weave --skill riverpod-3-0-migration-masssi164

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates Riverpod from 2.0 to 3.0 and consolidates migration guidance for breaking changes, API updates, and best practices.

Core Features & Use Cases

  • Automatic retries: understand how retry behavior changes and how to configure it globally or per provider.
  • Paused listeners behavior: learn how listeners are paused for off-screen widgets and how to manage that behavior.
  • API and typing updates: adapt code to Ref simplification, legacy imports, and Notifier/AsyncNotifier changes.
  • Use Case: upgrade a mid-size codebase by revising imports, updating provider types, and validating tests against Riverpod 3.0.

Quick Start

Update your Riverpod 2.0 providers, imports, and tests to Riverpod 3.0 with the guidance in this migration.

Frequently Asked Questions about riverpod-3-0-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Riverpod 2.0 to 3.0 in my Flutter project?▼

To migrate Riverpod 2.0 to 3.0, update legacy imports, adjust Notifier and AsyncNotifier APIs, modify Ref usage, and validate tests against the new provider lifecycles and breaking changes.

What breaking changes do I need to handle when upgrading to Riverpod 3.0?▼

Upgrading to Riverpod 3.0 requires handling breaking changes to automatic retries, paused listener behavior for off-screen widgets, Ref simplification, and updateShouldNotify adjustments.

Can I migrate a large Flutter codebase using StateProvider and StateNotifierProvider to Riverpod 3.0?▼

Yes, this migration supports large Flutter codebases by detailing specific changes for legacy providers like StateProvider and StateNotifierProvider, ensuring correct updates across your project.

How does Riverpod 3.0 change automatic retry behavior and paused listeners?▼

Riverpod 3.0 changes automatic retry behavior to allow global or per-provider configuration, and pauses listeners for off-screen widgets, requiring you to manage these behaviors during migration.

What is the best way to update Notifier and AsyncNotifier APIs for Riverpod 3.0?▼

The best way to update Notifier APIs for Riverpod 3.0 is to adapt your codebase to the Ref simplification and specific Notifier and AsyncNotifier typing updates detailed in the migration guidance.

Related Skills

Explore More Software Engineering Skills→
vertivolatamvertivolatam
1

State Management con Riverpod

Manage reactive state in Flutter applications using Riverpod providers.

Official
Intermediate
serverpodserverpod
8

riverpod-providers

Declare Riverpod providers for state management in Dart and Flutter applications.

Official
Intermediate
nonputtipongnonputtipong

dart-flutter-mcp

Analyze, test, and debug Dart and Flutter projects with MCP tools.

Community
Advanced
mokbhaimokbhai
1

microservices-patterns

Define service boundaries, communication patterns, and data ownership for microservice architectures.

Community
Basic