[GH-ISSUE #663] Implement native Vinext route-aware type generation #141

New issue

Closed

opened 2026-05-06 12:37:35 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 12:37:35 +02:00

Owner

Originally created by @pacexy on GitHub (Mar 23, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/663

Summary

Vinext currently has an optional dev-time bridge that can run when Next.js is installed locally. That improves developer experience in the short term, but it should not be the long-term solution.

Vinext already scans the route tree internally via and . We should use that data to generate the route-aware files directly, without depending on Next.js.

Goal

Implement native Vinext type generation for helpers such as and , so route-aware typing no longer depends on or a local Next.js install.

Notes

The current integration is intended as a temporary stopgap for developer experience.
The native implementation should preserve Vinext's positioning as a Vite-based reimplementation rather than requiring the real Next.js package.

Originally created by @pacexy on GitHub (Mar 23, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/663 ## Summary Vinext currently has an optional dev-time bridge that can run when Next.js is installed locally. That improves developer experience in the short term, but it should not be the long-term solution. Vinext already scans the route tree internally via and . We should use that data to generate the route-aware files directly, without depending on Next.js. ## Goal Implement native Vinext type generation for helpers such as and , so route-aware typing no longer depends on or a local Next.js install. ## Notes - The current integration is intended as a temporary stopgap for developer experience. - The native implementation should preserve Vinext's positioning as a Vite-based reimplementation rather than requiring the real Next.js package.