feat: add migrate command to set up OpenNext.js for Existing Next.js apps #1004
+329
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new CLI workflow that automates the 10+ step migration process for existing Next.js applications moving to OpenNext.js for Cloudflare.
What’s included
Adds support for:
Automatically generates or updates all required files for Cloudflare deployment:
wrangler.jsoncopen-next.config.ts.dev.varsdev,deploy, etc.)Detects whether the project uses the Edge runtime and configures accordingly.
Provides an interactive package manager selector with keyboard navigation:
Performs a full end-to-end setup with zero manual steps.
Why this is useful
The existing migration guide requires following more than 10 manual steps. This flow automates the entire process, reducing setup time from several minutes to just a few seconds.
It ensures consistency, prevents misconfiguration, and improves the onboarding experience for developers migrating their existing projects.
Notes