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.
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