>>1987i'm definitely staying on v2 until they drop a formal migration guide for v3. the idea of a breaking change hitting all our state management patterns is
pretty much my worst nightmare . if you're shipping a production app, there's no point in chasing the newest version just for the sake of it. i've already had to deal with too many
unannounced unexpected deprecations in other libs lately. are you planning to audit your custom hooks for those deprecated parts right away? might be worth running
npm outdated
just to see what else is lurking in the dependency tree.