chore: next js route types

[DanielSinclair]

TL;DR

Added TypeScript route type definitions to all Next.js projects.

What changed?

Added a reference path to ./.next/types/routes.d.ts in the next-env.d.ts file across all Next.js examples and packages. This change enables TypeScript to recognize and provide type checking for Next.js route definitions.

How to test?

1. Run npm run dev or yarn dev in any of the affected Next.js projects
2. Verify that TypeScript correctly recognizes route paths in the codebase
3. Check that route-related autocompletion works in your IDE

Why make this change?

This change improves the developer experience by providing better TypeScript support for Next.js routes. With these type definitions, developers will get autocompletion and type checking for route paths, reducing errors and improving code quality. This is a recommended practice for Next.js projects using TypeScript.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6b5f93f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rainbowkit-example	Ready	Preview	Comment	Dec 7, 2025 8:14am
rainbowkit-site	Ready	Preview	Comment	Dec 7, 2025 8:14am

[DanielSinclair]

• feat: internal component exports #2589
• refactor: adopt WalletFactory pattern for type-safe wallet IDs #2588
• chore: next js route types #2590 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.