Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,8 +127,13 @@ Your existing `pages/`, `app/`, `next.config.js`, and `public/` directories work
| `vp exec vinext-cloudflare deploy` | Build and deploy to Cloudflare Workers with Vite+ |
| `vinext init` | Migrate a Next.js project to run under vinext |
| `vinext check` | Scan your Next.js app for compatibility issues before migrating |
| `vinext typegen [directory]` | Generate App Router route helper types without a full build |
| `vinext lint` | Delegate to eslint or oxlint |

Run `vinext typegen` before a standalone TypeScript check if your App Router project uses
`PageProps`, `LayoutProps`, or `RouteContext`. It writes `.next/types/routes.d.ts` and creates or
updates `next-env.d.ts` in the target project. The directory defaults to the current working directory.

`vinext dev` and `vinext build` remain as thin aliases for the project-local Vite commands.
They require a Vite config; if one is missing, run `vinext init`. Vite owns their options,
output, and exit behavior. For older configured projects, the aliases still preload dotenv
Expand Down