Migration Experience: rivet_di v1 → dioxide v2
See what happens when you upgrade between major versions. Four find-and-replace patterns. No guesswork, no broken code left behind.
We break APIs when we have to. But we never break your trust.
The Problem
Framework upgrades are scary. Breaking changes mean hunting through your codebase, guessing what changed, and hoping you found everything. Most projects just stay on the old version.
The Solution
Every breaking change in dioxide comes with a clear migration guide. Renamed the package? Here are the four patterns to find and replace. Tests pass on the first try.