Skip to main content

​
Usage

workflow dev [options]
Or using the short alias: 
wf dev [options]

​
Status

This command is currently in development. When available, it will provide:
  • File watching for workflow changes
  • Development server for local workflows
  • Better error messages and debugging

​
Options

​
--port
number
default:"3000"
Port to run dev server on.Alias: -pExample:
workflow dev --port 3001
workflow dev -p 3001
​
--target
string
default:"standalone"
Build target for development.Alias: -tOptions:
  • standalone
  • vercel-build-output-api
Example:
workflow dev --target standalone
workflow dev -t vercel-build-output-api

​
Examples

​
Default Configuration

workflow dev
Runs on port 3000 with standalone target.

​
Custom Port

workflow dev --port 3001

​
Custom Target

workflow dev --target vercel-build-output-api

​
Combined Options

workflow dev --port 8080 --target standalone

​
Current Output

When run, the command currently displays: 
$ workflow dev

🚧 Development server is coming soon!

This command will provide:
• File watching
• Development server for local workflows
• Better error messages and debugging

Configured to run on port: 3000
Build target: standalone

For now, use: workflow build --target <target>

​
Planned Features

When implemented, this command will:
  1. File Watching: Automatically detect changes to workflow files
  2. Hot Reload: Rebuild workflows when files change
  3. Dev Server: Run a local server for testing workflows
  4. Enhanced Debugging: Provide better error messages and stack traces
  5. Live Logs: Show real-time logs of workflow execution

​
Alternative

Until workflow dev is available, use the build command: 
workflow build --target standalone
For development with framework integrations, use the framework’s dev server: 
# Next.js
npm run dev

# Nuxt
npm run dev

# Astro
npm run dev

# SvelteKit
npm run dev
These automatically watch for workflow changes and rebuild as needed.

Build docs developers (and LLMs) love

Get started for freeTalk to us