fix(router-modules): bump peer @modular-react/* to 2.x range

[diogomiguel]

Summary

Follow-up to #33. Same peer-descriptor drift on the router-modules side: all six @tanstack-react-modules/* and @react-router-modules/* core/runtime/testing packages still declare @modular-react/core: ^1.2.0 (and @modular-react/react: ^1.2.0 on runtime/testing), even though the runtime hooks consume React Contexts produced by the host's @modular-react/react@^2.x install.

Package	Before	After
@tanstack-react-modules/core	core: ^1.2.0	core: ^2.0.0
@tanstack-react-modules/runtime	core: ^1.2.0, react: ^1.2.0	core: ^2.0.0, react: ^2.0.0
@tanstack-react-modules/testing	core: ^1.2.0, react: ^1.2.0, journeys: ^1.0.0	core: ^2.0.0, react: ^2.0.0, journeys: ^1.0.1
@react-router-modules/core	core: ^1.2.0	core: ^2.0.0
@react-router-modules/runtime	core: ^1.2.0, react: ^1.2.0	core: ^2.0.0, react: ^2.0.0
@react-router-modules/testing	core: ^1.2.0, react: ^1.2.0, journeys: ^1.0.0	core: ^2.0.0, react: ^2.0.0, journeys: ^1.0.1

CHANGELOG entry added under Unreleased.

Why this matters for consumers

After #33 + the manually-published react@2.0.1 / journeys@1.0.1, autopilot's install resolves cleanly for journeys but the router-modules tree still nests an old core@1.5.0 + react@1.4.0 because of their stale peer ranges:

+-- @modular-react/core@2.0.0
+-- @modular-react/journeys@1.0.1
| +-- @modular-react/core@2.0.0 deduped
| `-- @modular-react/react@2.0.1
+-- @tanstack-react-modules/core@2.3.1
| `-- @modular-react/core@1.5.0          ← nested via stale peer range
`-- @tanstack-react-modules/runtime@2.5.0
  +-- @modular-react/core@1.5.0 deduped
  `-- @modular-react/react@1.4.0          ← duplicate React-binding instance

Two @modular-react/react copies means two distinct React Context objects: the host's <Manifest.Providers> produces a Provider against the 2.x context; @tanstack-react-modules/runtime's useZones / useNavigation / useRouteData reads against the 1.x context. The hooks silently return undefined and zone-driven layouts render empty.

The runtime code already works against @modular-react/core@2.x — the only thing required is the peer range correction.

Test plan

• pnpm install at the workspace root resolves cleanly (workspace deps use workspace:*)
• git diff shows only peer ranges + CHANGELOG entry — no behavior code touched
• After publish: npm install @modular-react/core@^2.0.0 @tanstack-react-modules/runtime@latest resolves to a single hoisted core@2.x + react@2.x everywhere

[coderabbitai]

Warning

Rate limit exceeded

@diogomiguel has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 23 minutes and 20 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 06e0c6fa-4508-4f98-b0fa-62e1483b9546

📥 Commits

Reviewing files that changed from the base of the PR and between b395c1c and acf8798.

📒 Files selected for processing (7)

• CHANGELOG.md
• packages/react-router-core/package.json
• packages/react-router-runtime/package.json
• packages/react-router-testing/package.json
• packages/tanstack-router-core/package.json
• packages/tanstack-router-runtime/package.json
• packages/tanstack-router-testing/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/router-modules-peer-deps-core-2x

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}