AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

react18-dep-compatibility

React 18.3.1 and React 19 dependency compatibility matrix.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--react18-dep-compatibility at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 3

references/router-migration.md

React Router v5 → v6 - Scope Assessment

Why This Is a Separate Sprint

React Router v5 → v6 is a complete API rewrite. Unlike most React 18 upgrade steps which touch individual patterns, the router migration affects:

  • Every <Route> component
  • Every <Switch> (replaced by <Routes>)
  • Every useHistory() (replaced by useNavigate())
  • Every useRouteMatch() (replaced by useMatch())
  • Every <Redirect> (replaced by <Navigate>)
  • Nested route definitions (entirely new model)
  • Route parameters access
  • Query string handling

Attempting this as part of the React 18 upgrade sprint will scope-creep the migration significantly.

Recommended Approach

Option A - Defer Router Migration (Recommended)

Use [email protected] with --legacy-peer-deps during the React 18 upgrade. This is explicitly documented as a supported workaround by the react-router team for React 18 compatibility on legacy root.

# In the React 18 dep surgeon:
npm install [email protected] --legacy-peer-deps

Document in package.json:

"_legacyPeerDepsReason": {
  "[email protected]": "Router v5→v6 migration deferred to separate sprint. React 18 peer dep mismatch only - no API incompatibility on legacy root."
}

Then schedule the v5 → v6 migration as its own sprint after the React 18 upgrade is stable.

Option B - Migrate Router as Part of React 18 Sprint

Only choose this if:

  • The app has minimal routing (< 10 routes, no nested routes, no complex navigation logic)
  • The team has bandwidth and the sprint timeline allows it

Scope Assessment Scan

Run this to understand the router migration scope before deciding:

echo "=== Route definitions ==="
grep -rn "<Route\|<Switch\|<Redirect" src/ --include="*.js" --include="*.jsx" | grep -v "\.test\." | wc -l

echo "=== useHistory calls ==="
grep -rn "useHistory()" src/ --include="*.js" --include="*.jsx" | grep -v "\.test\." | wc -l

echo "=== useRouteMatch calls ==="
grep -rn "useRouteMatch()" src/ --include="*.js" --include="*.jsx" | grep -v "\.test\." | wc -l

echo "=== withRouter HOC ==="
grep -rn "withRouter" src/ --include="*.js" --include="*.jsx" | grep -v "\.test\." | wc -l

echo "=== history.push / history.replace ==="
grep -rn "history\.push\|history\.replace\|history\.go" src/ --include="*.js" --include="*.jsx" | grep -v "\.test\." | wc -l

Decision guide:

  • Total hits < 30 → router migration is feasible in this sprint
  • Total hits 30–100 → strongly recommend deferring
  • Total hits > 100 → must defer - separate sprint required

v5 → v6 API Changes Summary

| v5 | v6 | Notes | |---|---|---| | <Switch> | <Routes> | Direct replacement | | <Route path="/" component={C}> | <Route path="/" element={<C />}> | element prop, not component | | <Route exact path="/"> | <Route path="/"> | exact is default in v6 | | <Redirect to="/new"> | <Navigate to="/new" /> | Component rename | | useHistory() | useNavigate() | Returns a function, not an object | | history.push('/path') | navigate('/path') | Direct call | | history.replace('/path') | navigate('/path', { replace: true }) | Options object | | useRouteMatch() | useMatch() | Different return shape | | match.params | useParams() | Hook instead of prop | | Nested routes inline | Nested routes in config | Layout routes concept | | withRouter HOC | useNavigate / useParams hooks | HOC removed |