Vercel
Vercel configuration file
| Type | object |
|---|---|
| File match |
vercel.json
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/vercel/latest.json |
| Source | https://openapi.vercel.sh/vercel.json |
Validate with Lintel
npx @lintel/lintel check
Properties
Ignored. Can be set to get completions, validations and documentation in some editors.
Aliases that will get assigned when the deployment is READY and the target is production. The client needs to make a GET request to its API to ensure the assignment
An object containing another object with information to be passed to the Build Process
1 nested properties
An object containing the deployment's environment variable names and values to be passed to Builds. Secrets can be referenced by prefixing the value with @
A list of build descriptions whose src references valid source files.
When set to true, all HTML files and Serverless Functions will have their extension removed. When visiting a path that ends with the extension, a 308 response will redirect the client to the extensionless path.
An object containing the deployment's environment variable names and values. Secrets can be referenced by prefixing the value with @
An array of the passive regions the deployment's Serverless Functions should be deployed to that can be failed over to during a lambda outage
Same as passiveRegions. An array of the passive regions the deployment's Serverless Functions should be deployed to so we can failover to these regions on lambda outages
An object describing custom options for your Serverless Functions. Each key must be glob pattern that matches the paths of the Serverless Functions you would like to customize (like api/*.js or api/test.js).
2 nested properties
Specifies the branches that will not trigger an auto-deployment when committing to them. Any non specified branch is true by default.
If specified, the git repository will be exclusive to the specificed Team IDs. Teams that are not specified in the list will not be able to link new projects or create new deployments.
1 nested properties
A list of allowed Team IDs.
4 nested properties
When set to false, Vercel for GitHub will not deploy the given project regardless of the GitHub app being installed.
When set to false, Vercel for GitHub will always build pushes in sequence without cancelling a build for the most recent commit.
When set to false, Vercel for GitHub will not apply the alias upon merge.
[deprecated] Please use the Project Settings in the dashboard instead: https://vercel.link/46vERTS When set to true, Vercel for GitHub will stop commenting on pull requests and commits.
A list of header definitions.
10 nested properties
A name for the deployment
Whether a deployment's source and logs are available publicly
A list of redirect definitions.
The path to a file containing bulk redirects; supports JSON, JSONL, and CSV
An array of the regions the deployment's Serverless Functions should be deployed to
A list of rewrite definitions.
A list of routes objects used to rewrite paths to point towards other internal or external paths
This property determines the scope (user or team) under which the project will be deployed by Vercel CLI.
When false, visiting a path that ends with a forward slash will respond with a 308 status code and redirect to the path without the trailing slash.
The build command for this project. When null is used this value will be automatically detected
The dev command for this project. When null is used this value will be automatically detected
The framework that is being used for this project. When null is used no framework is selected
The install command for this project. When null is used this value will be automatically detected
The output directory of the project. When null is used this value will be automatically detected
An array of cron jobs that should be created for production Deployments.
Enables Fluid compute for the project. It's enabled by default for new projects.
Enables Bun for the project and specifies the version to use.
Enables configuration of multiple applications in a single repository. Map of application name to application configuration.
Defines dependencies for single-service projects. Map of dependency key to dependency configuration.
Enables configuration of multiple services in a single deployment. Map of service name to service configuration.
Enables grouping of services. Map of service group name to an array of service names belonging to that group.