Skip to main content

Usage

Or using the short alias:

Options

string
default:"standalone"
Build target for deployment.Alias: -tOptions:
  • standalone - Standalone deployment
  • vercel-build-output-api - Vercel Build Output API
Example:
string
default:""
Output location for workflow manifest.Must end in .json, .js, .cjs, or .mjs.Alias: -mExample:

Positional Arguments

string
Build target (deprecated, use --target flag instead).Example:

Examples

Default Build

Builds with standalone target.

Vercel Build

Custom Manifest Location

Combined Options

Build Targets

standalone

Builds workflows for standalone deployment:
  • Creates workflow bundles
  • Generates manifest
  • Suitable for custom hosting
Output:

vercel-build-output-api

Builds workflows for Vercel deployment:
  • Creates Vercel Build Output API compatible functions
  • Configures serverless functions
  • Sets up edge routes
Output:

Output

Successful build:
With warnings:
Build error:

Error Handling

Invalid Manifest Extension

Invalid Target

Automatically falls back to standalone with a warning.

Build Failures

Displays detailed error message:

Configuration

The build command uses getWorkflowConfig() to load configuration:
  • Discovers workflow files in the project
  • Applies build target settings
  • Configures output paths
  • Sets up bundler options

Workflow Discovery

Automatically discovers workflows from:
  • workflows/ directory
  • Source directories configured by framework integrations
  • Files with "use workflow" or "use step" directives

Manifest Output

The manifest contains:

Exit Codes

  • 0 - Build succeeded
  • 1 - Build failed