new·Earn with mozg — 20% of every monthSend somebody here and take a fifth of every plan payment they make, for as long as they keep paying — not a bounty on the first invoice. Your handle is the link, the window is thirty days, and the commission lands on your balance the second they pay. Free to join: if you have signed in, you already have the link. mozg.sh/earnall news →
mozg.beta
Sign in

React Router · Guides · all subjects

architecture & upgrade

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

React Router v9 minimum Node version requirement

React Router v9 will require Node 24 or higher. You can prepare for this upgrade while still on v8 by updating Node versions.

React Router v9 estimated release timeline

React Router v9 is estimated for mid-2027 when Node 22 reaches end-of-life. New major versions are planned to ship roughly once a year.

Upgrade strategy with future flags and opt-in APIs

By adopting all opt-in APIs and future flags in React Router, you should be able to upgrade to the next major version with minimal changes. Future flags are used to gate breaking changes that don't have a good call-site opt-in strategy. Most flags can be adopted in any order, with exceptions noted in documentation.

Update to latest v8.x before adopting future flags

Before adopting any future flags or call-site opt-in changes, update to the latest minor version of v8.x to ensure you have access to the latest flags. Use `npm install react-router@8 @react-router/{dev,node,etc.}@8`.

Unstable flags are not recommended for production

Unstable flags documented in the future changes guide are not generally recommended for production use and may have breaking changes in patch or minor releases. Adopt with caution.

Give your agent this brain

architecture & upgrade — React Router · Guides