You can now update a project's framework preset and build settings directly from the CLI, without opening the dashboard.
Run
Settings can also be returned to automatic detection instead of an explicit override:
For automation or further inspection, return the result as JSON:
JSON output includes whether anything changed, the list of changed settings, the project ID and name, and the requested settings. Output is written to stdout with no other output mixed in, so it's safe to pipe and parse.
Agents can use this to repair misconfigured projects end to end: after diagnosing a failed build, an agent can correct the framework preset, build command, or output directory and redeploy, without dashboard access. Invalid framework slugs and settings are rejected with suggestions before any API call is made.
Update the Vercel CLI to v54.21.1 or later with
Read more
Continue reading...
Run
vercel project update from a linked project, or pass a project name directly:Settings can also be returned to automatic detection instead of an explicit override:
For automation or further inspection, return the result as JSON:
JSON output includes whether anything changed, the list of changed settings, the project ID and name, and the requested settings. Output is written to stdout with no other output mixed in, so it's safe to pipe and parse.
Agents can use this to repair misconfigured projects end to end: after diagnosing a failed build, an agent can correct the framework preset, build command, or output directory and redeploy, without dashboard access. Invalid framework slugs and settings are rejected with suggestions before any API call is made.
Update the Vercel CLI to v54.21.1 or later with
npm i -g vercel@latest to get started. Learn more in the Vercel project documentation.Read more
Continue reading...