vercel build

The vercel build command can be used to build a Vercel Project locally or in your own CI environment. Build artifacts are placed into the .vercel/output directory according to the Build Output API.

When used in conjunction with the vercel deploy --prebuilt command, this allows a Vercel Deployment to be created without sharing the Vercel Project's source code with Vercel.

This command can also be helpful in debugging a Vercel Project by receiving error messages for a failed build locally, or by inspecting the resulting build artifacts to get a better understanding of how Vercel will create the Deployment.

It is recommended to run the vercel pull command before invoking vercel build to ensure that you have the most recent Project Settings and Environment Variables stored locally.

vercel build

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

The --prod option can be specified when you want to build the Vercel Project using Production Environment Variables. By default, the Preview Environment Variables will be used.

vercel build --prod

The --yes option can be used to bypass the confirmation prompt and automatically pull environment variables and Project Settings if not found locally.

vercel build --yes

Use the --target option to define the environment you want to build against. This could be production, preview, or a custom environment. For more information, see Using an environment through the Vercel CLI.

vercel build --target=staging

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

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

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

• How can I use the Vercel CLI for custom workflows?