migrate-to-vinext

The migrate-to-vinext skill serves as an automated migration assistant for developers looking to move their existing Next.js applications to vinext, a Vite-based reimplementation of the Next.js API surface. This agent streamlines the modernization of your web project by handling the heavy lifting of framework swapping, configuration updates, and build tool orchestration without requiring manual code changes to your application logic. It is designed to work seamlessly with existing App Router or Pages Router projects, ensuring that you can leverage Vite's high-performance dev server, Hot Module Replacement (HMR), and native ESM support while maintaining compatibility with your current project structure. By using this skill, you reduce the operational burden of project refactoring, minimize the risk of configuration errors during manual setup, and gain immediate access to enhanced build performance and Cloudflare-native deployment options.

• Automatically detects and verifies existing Next.js project structures including App Router and Pages Router configurations.

• Executes comprehensive compatibility scans via vinext check to identify potential roadblocks before the migration starts.

• Performs full project migration including dependency remapping, Vite configuration generation, ESM conversion, and script updates in package.json.

• Facilitates deployment setup for Cloudflare Workers by auto-generating necessary config files such as wrangler.jsonc.

• Integrates seamless support for Cloudflare bindings (D1, R2, KV, AI) through native modules, allowing for clean implementation of server-side data access.

• Safely handles non-destructive migration flows, allowing you to run your legacy Next.js setup alongside the new vinext implementation for testing.

• Trigger the skill when you want to migrate, convert, or switch from Next.js to vinext by providing a command like 'migrate this project to vinext'.

• The skill operates on a phase-based approach: verification, compatibility checking, automated migration, and deployment optimization.

• Ensure your project has next in your package.json dependencies, as the skill requires this to confirm the target is a valid Next.js project.

• Be aware that while core features are supported, users should consult references/compatibility.md within the vinext repository for edge-case support regarding third-party library ecosystems.

• After running the automated migration, you can utilize the dev:vinext or build:vinext scripts to test and verify your application performance within the Vite environment before decommissioning the original Next.js configuration.