migrate-to-vinext

To migrate a Next.js app to Vite, you can automate the process by scanning for next.config.js, replacing dependencies, converting to ESM, generating vite.config.ts, and preparing deployment configurations. This streamlines dependency swaps and config translation to minimize breakage.

Yes, vinext works with both Next.js app and pages directories. The migration process detects your router type during compatibility scanning and applies the necessary package replacements and Vite configuration generation for either structure.

To convert a Next.js project to ESM for Vite, the migration adds type: module to package.json and renames CommonJS config files like next.config.js to .cjs. This ensures the Vite-based runtime correctly processes your modules.

Yes, you can deploy to Cloudflare Workers. The migration generates a wrangler.jsonc configuration file for Cloudflare deployment and advises on Cloudflare bindings and RSC plugin requirements to ensure your Vite-native app runs correctly on the platform.

The best way to automate Next.js to Vite dependency swaps is using a migration tool that detects your package manager via lockfiles, installs vite and the RSC plugin, and updates your scripts automatically. This minimizes manual errors and downtime.

Limitations of migrating Next.js to vinext include potential breakage from ESM conversion and deployment differences. The migration performs compatibility scanning to produce a scored report, but you must verify routes and server components locally with vinext dev before deploying.