vercel dev

The vercel dev command is used to replicate the Vercel deployment environment locally, allowing you to test your Vercel Functions and Middleware without requiring you to deploy each time a change is made.

If the Development Command is configured in your Project Settings, it will affect the behavior of vercel dev for everyone on that team.

If you're using a framework and your framework's Development Command already provides all the features you need, we do not recommend using vercel dev.

For example, Next.js's Development Command (next dev) provides native support for Functions, redirects, rewrites, headers and more.

vercel dev

These are options that only apply to the vercel dev command.

The --listen option can be used to specify which port vercel dev runs on.

vercel dev --listen 5005

To start vercel dev in a directory that is not linked to a Vercel Project, without setting up a project or logging in, use the --local option:

vercel dev --local

Without a linked project, the CLI does not pull environment variables from Vercel, and your project settings come from your local configuration, such as vercel.json.

The --yes option can be used to skip questions you are asked when setting up a new Vercel Project. The CLI answers the questions with the current directory for the Vercel Project name and location. The --yes option does not choose a team. If you belong to more than one team, also pass the --scope option.

vercel dev --yes

The following global options can be passed when using the vercel dev command:

• --cwd
• --debug
• --global-config
• --help
• --local-config
• --no-color
• --non-interactive
• --scope
• --token
• --version

For more information on global options and their usage, refer to the options section.