name: vercel description: Vercel deployment platform documentation. Use for deploying web applications, serverless functions, Edge Functions, environment variables, domains, CI/CD, and framework integrations (Next.js, React, Vue, etc.).

Vercel Skill

Comprehensive assistance with vercel development, generated from official documentation.

When to Use This Skill

This skill should be triggered when:

Working with vercel
Asking about vercel features or APIs
Implementing vercel solutions
Debugging vercel code
Learning vercel best practices

Quick Reference

Common Patterns

Pattern 1: DocsAPI ReferenceGetting StartedExpand menuProjects and DeploymentsUse a TemplateImport Existing ProjectAdd a DomainBuy a DomainTransfer an Existing DomainCollaborateNext StepsSupported FrameworksExpand menuFull-stackExpand menuNext.jsSvelteKitNuxtRemixTanStack StartFrontendsExpand menuAstroViteReact RouterCreate React AppBackendsExpand menuNitroExpressElysiaFastAPIFastifyFlaskHonoNestJSxmcpAll FrameworksIncremental MigrationProduction ChecklistKnowledge BaseDocs llms-full.txtAccessExpand menuAccount ManagementSign in with VercelExpand menuGetting StartedScopes & PermissionsTokensAuthorization Server APIManage from DashboardConsent PageTroubleshootingActivity LogDeployment ProtectionExpand menuBypass Deployment ProtectionExpand menuExceptionsOPTIONS AllowlistProtection Bypass for AutomationSharable LinksProtect DeploymentsExpand menuPassword ProtectionTrusted IPsVercel AuthenticationDirectory SyncSAML SSOTwo-factor (2FA)AIExpand menuVercel AgentExpand menuCode ReviewbetaExpand menuManaging ReviewsInvestigationbetaPricingAI SDKAI GatewayExpand menuGetting StartedModels & ProvidersObservabilityPricingProvider OptionsOpenAI-Compatible APIAuthenticationBYOKUsage & BillingFramework IntegrationsExpand menuLangChainLangFuseLiteLLMLlamaIndexMastraPydantic AIApp AttributionImage GenerationExpand menuUsing AI SDKUsing OpenAI-Compatible APIModel VariantsZDRMCPExpand menuDeploy MCP serversVercel MCP serverbetaExpand menuToolsIntegrations for AgentsIntegrations for ModelsExpand menuAdding a ProviderAdding a ModelxAIGroqfalDeep InfraElevenLabsLMNTOpenAIPerplexityPineconeReplicateTogether AIBuild & DeployExpand menuBuildsExpand menuBuild FeaturesBuild ImageBuild QueuesConfiguring a BuildManaging BuildsDeploy HooksDeployment ChecksDeployment RetentionDeploymentsExpand menuEnvironmentsGenerated URLsManaging DeploymentsPromoting DeploymentsTroubleshoot Build ErrorsAccessing Build LogsClaim DeploymentsInspect OG MetadataPreview Deployment SuffixSharing a Preview DeploymentTroubleshoot project collaborationEnvironment VariablesExpand menuFramework Environment VariablesManaging Environment VariablesReserved Environment VariablesRotating Environment VariablesSensitive Environment VariablesShared Environment VariablesSystem Environment VariablesGit IntegrationsExpand menuGitHubAzure DevOpsBitbucketGitLabInstant RollbackMicrofrontendsExpand menuGetting StartedLocal DevelopmentPath RoutingConfigurationManaging MicrofrontendsExpand menuSecurityUsing Vercel ToolbarTesting & TroubleshootingMonoreposExpand menuTurborepoRemote CachingNxMonorepos FAQPackage ManagersRestricting Git Connections to a single Vercel teamRolling ReleasesSkew ProtectionWebhooksExpand menuWebhooks API ReferenceCDNExpand menuOverviewRegionsHeadersExpand menuSecurity HeadersCache-Control HeadersRequest HeadersResponse HeadersCDN CacheExpand menuPurge CDN CacheEncryptionCompressionIncremental Static RegenerationExpand menuGetting StartedUsage & PricingRedirectsExpand menuConfiguration RedirectsBulk redirectsExpand menuGetting StartedRewritesImage OptimizationExpand menuGetting StartedLimits and PricingManaging Usage & CostsLegacy PricingManage CDN UsageRequest CollapsingCLIExpand menuDeploying from CLIProject LinkingTelemetryGlobal Optionsvercel aliasvercel bisectvercel blobvercel buildvercel cachevercel certsvercel curlvercel deployvercel devvercel dnsvercel domainsvercel envvercel gitvercel helpvercel httpstatvercel initvercel inspectvercel installvercel integrationvercel integration-resourcevercel linkvercel listvercel loginvercel logoutvercel logsvercel openvercel projectvercel promotevercel pullvercel redeployvercel removevercel rollbackvercel rolling-releasevercel switchvercel teamsvercel telemetryvercel whoamiCollaborationExpand menuCommentsExpand menuEnabling CommentsUsing CommentsManaging CommentsIntegrationsDraft ModeEdit ModeFeature FlagsExpand menuFlags ExplorerExpand menuGetting StartedReferencePricingFlags SDKWith Runtime LogsWith Vercel PlatformWith Web AnalyticsToolbarExpand menuAdd to EnvironmentsExpand menuAdd to LocalhostAdd to ProductionManaging ToolbarBrowser ExtensionsAccessibility Audit ToolInteraction Timing ToolLayout Shift ToolComputeExpand menuFluid ComputeFunctionsExpand menuGetting StartedStreamingRuntimesExpand menuNode.jsExpand menuAdvanced Node.js UsageSupported Node.js versionsBunPythonRustGo RuntimeGoRubyWasmEdge RuntimeConfiguring FunctionsExpand menuDurationMemoryRuntimeRegionAdvanced ConfigurationAPI ReferenceExpand menuNode.jsPythonLogsLimitsConcurrency ScalingPricingExpand menuLegacy Usage & PricingData CacheRouting MiddlewareExpand menuGetting StartedAPICron JobsExpand menuGetting StartedManaging Cron JobsUsage & PricingOG Image GenerationExpand menu@vercel/ogExamplesSandboxbetaExpand menuCLI ReferenceExamplesPricing and LimitsWorkflowbetaMulti-tenantExpand menuDomain ManagementLimitsObservabilityExpand menuOverviewExpand menuInsightsObservability PlusAlertsbetaLogsExpand menuRuntimeTracingExpand menuInstrumentationSession TracingQueryExpand menuQuery ReferenceMonitoringExpand menuGetting StartedMonitoring ReferenceLimits and PricingNotebooksSpeed InsightsExpand menuGetting StartedUsing Speed InsightsMetricsPrivacy@vercel/speed-insightsLimits and PricingTroubleshootingMigrating from LegacyDrainsExpand menuUsing DrainsReferenceExpand menuLogsTracesSpeed InsightsWeb AnalyticsSecurityWeb AnalyticsExpand menuGetting StartedUsing Web AnalyticsFilteringCustom EventsRedacting Sensitive DataPrivacy@vercel/analyticsPricingTroubleshootingManage & OptimizePlatformExpand menuProjectsExpand menuManaging projectsProject DashboardTransferring a projectProject ConfigurationExpand menuGeneral SettingsProject SettingsGit ConfigurationGit SettingsGlobal ConfigurationSecurity settingsDomainsExpand menuWorking with DomainsExpand menuAdding a DomainAdding a Domain to an EnvironmentAssigning a Domain to a Git BranchDeploying & Redirecting DomainsRemoving a DomainRenewing a DomainTransferring DomainsViewing & Searching DomainsWorking with DNSManaging DNS RecordsWorking with NameserversManaging NameserversWorking with SSLCustom SSL CertificatesPre-Generate SSL CertificatesSupported DomainsTroubleshooting DomainsUsing Domains APIIntegrationsExpand menuExtend VercelExpand menuAdd a Connectable AccountAdd a Native IntegrationPermissions and AccessIntegrate with VercelExpand menuNative integration conceptsCreate a Native IntegrationDeployment integration actionsNative Integration FlowsIntegration Approval ChecklistUsing Integrations APIExpand menuIntegrations API ReferenceSecrets RotationIntegration Image GuidelinesRequirements for listing an IntegrationUpgrade an IntegrationCMS IntegrationsExpand menuAgility CMSButterCMSContentfulDatoCMSFormspreeMakeswiftSanitySitecoreEcommerce IntegrationsExpand menuBigCommerceShopifyBuilding Integrations with Vercel REST APIExternal PlatformsExpand menuKubernetesDashboardExpand menuNavigating the DashboardSupport CenterUsing the Command Menu NotificationsBuild Output APIExpand menuBuild Output ConfigurationFeaturesVercel PrimitivesGlossaryLimitsExpand menuFair use GuidelinesChecksExpand menuChecks APIChecks ReferencePricingExpand menuPlansExpand menuHobby PlanPro PlanExpand menuPro Plan TrialSwitch to the Pro PlanBilling FAQEnterprise PlanExpand menuBilling FAQMIUs for AILegacy Pro PlanExpand menuBilling FAQPricingExpand menuRegional PricingExpand menuCape Town, South AfricaCleveland, USADubai, UAEDublin, IrelandFrankfurt, GermanyHong KongLondon, UKMumbai, IndiaOsaka, JapanParis, FrancePortland, USASan Francisco, USASão Paulo, BrazilSeoul, South KoreaSingaporeStockholm, SwedenSydney, AustraliaTokyo, JapanWashington, D.C., USAManage and Optimize UsageCalculating Usage of ResourcesBilling & InvoicesLegacy MetricsSales TaxSpend ManagementSecurityExpand menuOverviewExpand menuSecurity & Compliance MeasuresShared Responsibility ModelPCI DSS iframe IntegrationReverse Proxy Servers and VercelAccess ControlAudit LogsFirewallExpand menuFirewall ConceptsDDoS MitigationAttack Challenge ModeWeb Application FirewallExpand menuCustom RulesRate LimitingRule ConfigurationSystem Bypass RulesRate Limiting SDKIP BlockingManaged RulesetsExamplesUsage & PricingFirewall APIFirewall ObservabilityBot ManagementBotIDExpand menuGet Started with BotIDHandling Verified BotsAdvanced BotID ConfigurationForm SubmissionsLocal Development BehaviorConnectivityExpand menuSecure ComputeStatic IPsExpand menuGetting StartedOIDCExpand menuAWSAzureConnect your APIGoogle Cloud PlatformOIDC ReferenceRBACExpand menuAccess RolesExpand menuExtended PermissionsProject Level RolesTeam Level RolesAccess GroupsManaging Team MembersTwo-factor EnforcementStorageExpand menuOverviewBlobExpand menuServer UploadsClient UploadsUsing the SDKPricingSecurityExamplesEdge ConfigExpand menuGetting StartedUsing Edge ConfigEdge Configs & REST APIEdge Configs & DashboardEdge Config SDKLimits & PricingIntegrationsExpand menuDevCycleHypertuneLaunchDarklySplitStatsigMenuSystem environment variablesCopy pageAsk AI about this pageLast updated November 25, 2025Vercel provides a set of environment variables that are automatically populated by the system, such as the URL of the deployment or the name of the Git branch deployed. Automatically expose system environment variables To expose these environment variables to your deployments: Navigate to your project on your dashboard. Go to the Settings tab and click on the Environment Variables section. Select the Automatically expose System Environment Variables checkbox. If you disable this setting, no deployment ID will be made available for supported frameworks (like Next.js) to use, which means Skew Protection will also be disabled. System environment variables If you are using a framework for your project, Vercel provides the following prefixed environment variables: When you choose to automatically expose system environment variables, some React warnings, such as those in a will display as build errors. For more information on this error, see How do I resolve a error? VERCELAvailable at:Both build and runtimeAn indicator to show that system environment variables have been exposed to your project's Deployments..envVERCEL=1CIAvailable at:Build timeAn indicator that the code is running in a Continuous Integration environment..envCI=1VERCEL_ENVAvailable at:Both build and runtimeThe environment that the app is deployed and running on. The value can be either production, preview, or development..envVERCEL_ENV=productionVERCEL_TARGET_ENVAvailable at:Both build and runtimeThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envVERCEL_TARGET_ENV=productionVERCEL_URLAvailable at:Both build and runtimeThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envVERCEL_URL=my-site.vercel.appVERCEL_BRANCH_URLAvailable at:Both build and runtimeThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envVERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appVERCEL_PROJECT_PRODUCTION_URLAvailable at:Both build and runtimeA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envVERCEL_PROJECT_PRODUCTION_URL=my-site.comVERCEL_REGIONAvailable at:RuntimeThe ID of the Region where the app is running..envVERCEL_REGION=cdg1VERCEL_DEPLOYMENT_IDAvailable at:Both build and runtimeThe unique identifier for the deployment, which can be used to implement Skew Protection..envVERCEL_DEPLOYMENT_ID=dpl_7Gw5ZMBpQA8h9GF832KGp7nwbuh3VERCEL_PROJECT_IDAvailable at:Both build and runtimeThe unique identifier for the project..envVERCEL_PROJECT_ID=prj_Rej9WaMNRbffVm34MfDqa4daCEvZzzEVERCEL_SKEW_PROTECTION_ENABLEDAvailable at:Both build and runtimeWhen Skew Protection is enabled in Project Settings, this value is set to 1..envVERCEL_SKEW_PROTECTION_ENABLED=1VERCEL_AUTOMATION_BYPASS_SECRETAvailable at:Both build and runtimeThe Protection Bypass for Automation value, if the secret has been generated in the project's Deployment Protection settings..envVERCEL_AUTOMATION_BYPASS_SECRET=secretVERCEL_OIDC_TOKENAvailable at:Build timeWhen Secure Backend Access with OpenID Connect (OIDC) Federation is enabled in Project Settings, this value is set to a Vercel-issued OIDC token. At runtime, the token is set to thex-vercel-oidc-token header on your functions' Request object. In local development, you can download the token using the CLI commandvercel env pull..envVERCEL_OIDC_TOKEN=secretVERCEL_GIT_PROVIDERAvailable at:Both build and runtimeThe Git Provider the deployment is triggered from..envVERCEL_GIT_PROVIDER=githubVERCEL_GIT_REPO_SLUGAvailable at:Both build and runtimeThe origin repository the deployment is triggered from..envVERCEL_GIT_REPO_SLUG=my-siteVERCEL_GIT_REPO_OWNERAvailable at:Both build and runtimeThe account that owns the repository the deployment is triggered from..envVERCEL_GIT_REPO_OWNER=acmeVERCEL_GIT_REPO_IDAvailable at:Both build and runtimeThe ID of the repository the deployment is triggered from..envVERCEL_GIT_REPO_ID=117716146VERCEL_GIT_COMMIT_REFAvailable at:Both build and runtimeThe git branch of the commit the deployment was triggered by..envVERCEL_GIT_COMMIT_REF=improve-about-pageVERCEL_GIT_COMMIT_SHAAvailable at:Both build and runtimeThe git SHA of the commit the deployment was triggered by..envVERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081VERCEL_GIT_COMMIT_MESSAGEAvailable at:Both build and runtimeThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envVERCEL_GIT_COMMIT_MESSAGE=Update about pageVERCEL_GIT_COMMIT_AUTHOR_LOGINAvailable at:Both build and runtimeThe username attached to the author of the commit that the project was deployed by..envVERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeVERCEL_GIT_COMMIT_AUTHOR_NAMEAvailable at:Both build and runtimeThe name attached to the author of the commit that the project was deployed by..envVERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeVERCEL_GIT_PREVIOUS_SHAAvailable at:Build timeThe git SHA of the last successful deployment for the project and branch..envVERCEL_GIT_PREVIOUS_SHA=fa1eade47b73733d6312d5abfad33ce9e4068080VERCEL_GIT_PULL_REQUEST_IDAvailable at:Both build and runtimeThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envVERCEL_GIT_PULL_REQUEST_ID=23Was this helpful? supported.SendCopy pageGive feedbackAsk AI about this page

vercel alias

Pattern 2: MenuSystem environment variablesCopy pageAsk AI about this pageLast updated November 25, 2025Vercel provides a set of environment variables that are automatically populated by the system, such as the URL of the deployment or the name of the Git branch deployed. Automatically expose system environment variables To expose these environment variables to your deployments: Navigate to your project on your dashboard. Go to the Settings tab and click on the Environment Variables section. Select the Automatically expose System Environment Variables checkbox. If you disable this setting, no deployment ID will be made available for supported frameworks (like Next.js) to use, which means Skew Protection will also be disabled. System environment variables If you are using a framework for your project, Vercel provides the following prefixed environment variables: When you choose to automatically expose system environment variables, some React warnings, such as those in a will display as build errors. For more information on this error, see How do I resolve a error? VERCELAvailable at:Both build and runtimeAn indicator to show that system environment variables have been exposed to your project's Deployments..envVERCEL=1CIAvailable at:Build timeAn indicator that the code is running in a Continuous Integration environment..envCI=1VERCEL_ENVAvailable at:Both build and runtimeThe environment that the app is deployed and running on. The value can be either production, preview, or development..envVERCEL_ENV=productionVERCEL_TARGET_ENVAvailable at:Both build and runtimeThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envVERCEL_TARGET_ENV=productionVERCEL_URLAvailable at:Both build and runtimeThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envVERCEL_URL=my-site.vercel.appVERCEL_BRANCH_URLAvailable at:Both build and runtimeThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envVERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appVERCEL_PROJECT_PRODUCTION_URLAvailable at:Both build and runtimeA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envVERCEL_PROJECT_PRODUCTION_URL=my-site.comVERCEL_REGIONAvailable at:RuntimeThe ID of the Region where the app is running..envVERCEL_REGION=cdg1VERCEL_DEPLOYMENT_IDAvailable at:Both build and runtimeThe unique identifier for the deployment, which can be used to implement Skew Protection..envVERCEL_DEPLOYMENT_ID=dpl_7Gw5ZMBpQA8h9GF832KGp7nwbuh3VERCEL_PROJECT_IDAvailable at:Both build and runtimeThe unique identifier for the project..envVERCEL_PROJECT_ID=prj_Rej9WaMNRbffVm34MfDqa4daCEvZzzEVERCEL_SKEW_PROTECTION_ENABLEDAvailable at:Both build and runtimeWhen Skew Protection is enabled in Project Settings, this value is set to 1..envVERCEL_SKEW_PROTECTION_ENABLED=1VERCEL_AUTOMATION_BYPASS_SECRETAvailable at:Both build and runtimeThe Protection Bypass for Automation value, if the secret has been generated in the project's Deployment Protection settings..envVERCEL_AUTOMATION_BYPASS_SECRET=secretVERCEL_OIDC_TOKENAvailable at:Build timeWhen Secure Backend Access with OpenID Connect (OIDC) Federation is enabled in Project Settings, this value is set to a Vercel-issued OIDC token. At runtime, the token is set to thex-vercel-oidc-token header on your functions' Request object. In local development, you can download the token using the CLI commandvercel env pull..envVERCEL_OIDC_TOKEN=secretVERCEL_GIT_PROVIDERAvailable at:Both build and runtimeThe Git Provider the deployment is triggered from..envVERCEL_GIT_PROVIDER=githubVERCEL_GIT_REPO_SLUGAvailable at:Both build and runtimeThe origin repository the deployment is triggered from..envVERCEL_GIT_REPO_SLUG=my-siteVERCEL_GIT_REPO_OWNERAvailable at:Both build and runtimeThe account that owns the repository the deployment is triggered from..envVERCEL_GIT_REPO_OWNER=acmeVERCEL_GIT_REPO_IDAvailable at:Both build and runtimeThe ID of the repository the deployment is triggered from..envVERCEL_GIT_REPO_ID=117716146VERCEL_GIT_COMMIT_REFAvailable at:Both build and runtimeThe git branch of the commit the deployment was triggered by..envVERCEL_GIT_COMMIT_REF=improve-about-pageVERCEL_GIT_COMMIT_SHAAvailable at:Both build and runtimeThe git SHA of the commit the deployment was triggered by..envVERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081VERCEL_GIT_COMMIT_MESSAGEAvailable at:Both build and runtimeThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envVERCEL_GIT_COMMIT_MESSAGE=Update about pageVERCEL_GIT_COMMIT_AUTHOR_LOGINAvailable at:Both build and runtimeThe username attached to the author of the commit that the project was deployed by..envVERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeVERCEL_GIT_COMMIT_AUTHOR_NAMEAvailable at:Both build and runtimeThe name attached to the author of the commit that the project was deployed by..envVERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeVERCEL_GIT_PREVIOUS_SHAAvailable at:Build timeThe git SHA of the last successful deployment for the project and branch..envVERCEL_GIT_PREVIOUS_SHA=fa1eade47b73733d6312d5abfad33ce9e4068080VERCEL_GIT_PULL_REQUEST_IDAvailable at:Both build and runtimeThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envVERCEL_GIT_PULL_REQUEST_ID=23Was this helpful? supported.Send

VERCEL=1

Pattern 3: MenuTroubleshooting Build ErrorsCopy pageAsk AI about this pageLast updated November 25, 2025You can troubleshoot build errors that occur during the Build step of your deployment to Vercel. This guide will help you understand how to investigate build failures and long build times. Troubleshooting views You can use the following views on your dashboard to troubleshoot a build: Build logs - the console output when your deployment is building which can be found under the Deployment Status section of the Project's Deployment page. Resources tab - the functions, middleware, and assets from your deployment's build. Source tab - the output of the build after the deployment is successful. This can also be accessed by appending to the Deployment URL You can navigate to these views from the Deployment page by clicking on the Source tab, the Resources tab or the Build Logs accordion as shown below. Troubleshoot Build failures If your build fails, Vercel will report the error message on the Deployments page so that you can investigate and fix the underlying issue. In the following we show you how to look up the error message of your failed build. Investigating Build logs Build logs provide you with an insight into what happened during the build of a deployment and can be accessed by: From your Vercel dashboard, select the project and then the Deployments tab Select the deployment. When there are build issues you will notice an error status next to deployment name Error status on the Deployments tab. On the errored deployment's page, you will see a summary of the error in the preview section. In the Deployment Details section, expand the Building accordion to expand the logs. There are situations where build logs are not available, in this scenario the error will be presented in the UI instead. Scroll down in the build logs until you find a red section where the keyword "Error" is mentioned. It can be mentioned once or multiple times. In many cases, the last mention is not indicative like in the example below where it says . If you look a few lines above, you will see an additional error which in this case indicates where the problem is with a link for more details. Sometimes, an error may not be mentioned in the lines above but the output will often help you identify where the problem is. Error in the logs of the Building accordion. It is recommended to build your project on your local machine first (the build command varies per project) before deploying on Vercel. This will catch issues specific to your code or to your project's dependencies. In the example above, when the command (that runs ) is run in the local console for a Next.js project, the error happens after building locally. Error in local console. Build Logs not available Builds can fail without providing any build logs when Vercel detects a missing precondition that prevents a build from starting. For example: An invalid configuration was committed When using Ignored Build Steps Commits were made from a contributor that is not a team member In this case, you cannot access the Building accordion described above, and instead, Vercel will present an overlay that contains the error message. Build logs not available for a deployment. Cancelled Builds due to limits Sometimes, your Deployment Build can hit platform limits so that the build will be cancelled and throw a corresponding error that will be shown in the Build logs. Review the limits below in case you run into them. Build container resources Every Build is provided with the following resources: HobbyProEnterpriseMemory8192 MB8192 MBCustomDisk space23 GB23 GBCustomCPUs24Custom For Hobby customers, these limits are fixed. Pro and Enterprise customers can purchase Enhanced or Turbo build machines with extra CPUs, larger memory, and storage. Exceeding the memory or disk space allocations limits cancels the build and triggers a system report in your Build logs, identifying memory and disk space issues. By default, the system generates this report only when it detects a problem. To receive a report for every deployment, set as an environment variable. This report helps you detect hidden Out of Memory (OOM) events, and provides insights into disk usage by breaking down the sizes of your source code, , and output, and flagging files over 100 MB. The input size in the report corresponds to the size of your checked-out repository or files uploaded by CLI. The size represents the total size of all folders on disk. ResourceAllocationDescriptionMemory8192 MBFixed memory allocation. Builds exceeding this limit will be cancelledCPUs4Number of CPUs allocated for build processingDisk Space23 GBFixed disk space allocation. Builds exceeding this limit will be cancelledSystem ReportConditionalGenerated in Build logs when memory or disk space limits are reached. Available by defaultForced ReportingOptionalSet as an environment variable to enable reporting for all builds Review the below steps to help navigate this situation: Review what package the error is related to and explore the package's documentation to see if the memory allocation can be customized with an install or Build command If no package is specified, look into reducing the amount of JavaScript that your Project might be using or find a more efficient JavaScript bundler Review what you are importing in your code such as third-party services, icons and media files Build duration The total build duration is shown on the Vercel Dashboard and includes all three steps: building, checking, and assigning domains. Each step also shows the individual duration. A Build can last for a maximum of 45 minutes. If the build exceeds this time, the deployment will be canceled and the error will be shown on the Deployment's Build logs. If you run into this limit, review this guide that explains how to reduce the Build time with a Next.js Project. Caching The maximum size of the Build's cache is 1 GB. It is retained for one month and it applies at the level of each Build cache key. It is not possible to manually configure which files are cached at this time. Other Build errors You may come across the following Build-specific errors when deploying your Project. The link for each error provides possible causes of the error that can help you troubleshoot. Missing Build script Recursive invocation of commands Pnpm engine unsupported A 'module not found' error is a syntax error that will appear at build time. This error appears when the static import statement cannot find the file at the declared path. For more information, see How do I resolve a 'module not found' error? Troubleshoot Build time Understanding Build cache The first Build in a Project will take longer as the Build cache is initially empty. Subsequent builds that have the same Build cache key will take less time because elements from your build, such as framework files and node modules, will be reused from the available cache. The next sections will describe the factors that affect the Build cache to help you decrease the Build time What is cached Vercel caches files based on the Framework Preset selected in your Project settings. The following files are cached in addition to : FrameworkCache PatternNext.js.next/cache/**Nuxt.nuxt/**Gatsby.js{.cache,public}/**Eleventy.cache/**Jekyll{vendor/bin,vendor/cache,vendor/bundle}/Middleman{vendor/bin,vendor/cache,vendor/bundle}/ Note that the framework detection is dependent on the preset selection made in the Build settings. You should make sure that the correct framework is set for your project for optimum build caching. Caching process At the beginning of each build, the previous Build's cache is restored prior to the Install Command or Build command executing. Each deployment is associated with a unique Build cache key that is derived from the combination of the following data: Personal Account or Team Project Framework Preset Root Directory Node.js Version Package Manager Git branch Let's say that under your account , you have a project that is connected to your Git repository on the branch for the production environment. When you make a commit to the branch for the first time, you trigger a build that creates a production deployment with a new unique cache key. For any new commits to the branch of , the existing Build cache is used as long as is under . If you create a new Git branch in and make a commit to it, there is no cache for that specific branch. In this case, the last production Deployment cache is used to create a preview deployment and a new branch cache is created for subsequent commits to the new branch. If you use Vercel functions to process HTTP requests in your project, each Vercel Function is built separately in the Build step and has its own cache, based on the Runtime used. Therefore, the number and size of Vercel functions will affect your Build time. For Next.js projects, Vercel functions are bundled to optimize Build resources as described here. At the end of each Build step, successful builds will update the cache and failed builds will not modify the existing cache. Excluding development dependencies Since development dependencies (for example, packages such as or ) are not needed in production, you may want to prevent them from being installed when deploying to Vercel to reduce the Build time. To skip development dependencies, customize the Install Command to be or . Managing Build cache Sometimes, you may not want to use the Build cache for a specific deployment. You can invalidate or delete the existing Build cache in the following ways: Use the Redeploy button for the specific deployment in the Project's Deployments page. In the popup window that follows, leave the checkbox Use existing Build Cache unchecked. See Redeploying a project for more information. Use with Vercel CLI to build and deploy the project without the Build cache Use an Environment Variable with a value of on your project to skip the Build cache Use an Environment Variable with a value of on your project to skip Turborepo Remote Cache Use the optional query parameter with a value of when creating a new deployment with the Vercel API to skip the Build cache When redeploying without the existing Build Cache, the Remote Cache from Turborepo and Nx are automatically excluded.Was this helpful? supported.Send

.next/cache/**

Pattern 4: MenuFramework environment variablesCopy pageAsk AI about this pageLast updated July 18, 2025Frameworks typically use a prefix in order to expose environment variables to the browser. The following prefixed environment variables will be available during the build step, based on the project's selected framework preset. Using prefixed framework environment variables locally Many frontend frameworks require prefixes on environment variable names to make them available to the client, such as for Next.js or for SvelteKit. Vercel adds these prefixes automatically for your production and preview deployments, but not for your local development environment. Framework environment variables are not prefixed when pulled into your local development environment with . For example, will not be prefixed to . To use framework-prefixed environment variables locally: Define them in your project settings with the appropriate prefix Scope them to Pull them into your local environment with Vercel CLI using the command Framework environment variables Next.jsNuxtCreate React AppGatsby.jsSolidStart (v0)SvelteKit (v0)AstroSolidStart (v1)Vue.jsRedwoodJSHydrogen (v1)ViteSanity (v3)SanityNEXT_PUBLIC_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envNEXT_PUBLIC_VERCEL_ENV=productionNEXT_PUBLIC_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envNEXT_PUBLIC_VERCEL_TARGET_ENV=productionNEXT_PUBLIC_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envNEXT_PUBLIC_VERCEL_URL=my-site.vercel.appNEXT_PUBLIC_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envNEXT_PUBLIC_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appNEXT_PUBLIC_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envNEXT_PUBLIC_VERCEL_PROJECT_PRODUCTION_URL=my-site.comNEXT_PUBLIC_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envNEXT_PUBLIC_VERCEL_GIT_PROVIDER=githubNEXT_PUBLIC_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envNEXT_PUBLIC_VERCEL_GIT_REPO_SLUG=my-siteNEXT_PUBLIC_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envNEXT_PUBLIC_VERCEL_GIT_REPO_OWNER=acmeNEXT_PUBLIC_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envNEXT_PUBLIC_VERCEL_GIT_REPO_ID=117716146NEXT_PUBLIC_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envNEXT_PUBLIC_VERCEL_GIT_COMMIT_REF=improve-about-pageNEXT_PUBLIC_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envNEXT_PUBLIC_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081NEXT_PUBLIC_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envNEXT_PUBLIC_VERCEL_GIT_COMMIT_MESSAGE=Update about pageNEXT_PUBLIC_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envNEXT_PUBLIC_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeNEXT_PUBLIC_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envNEXT_PUBLIC_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeNEXT_PUBLIC_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envNEXT_PUBLIC_VERCEL_GIT_PULL_REQUEST_ID=23NUXT_ENV_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envNUXT_ENV_VERCEL_ENV=productionNUXT_ENV_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envNUXT_ENV_VERCEL_TARGET_ENV=productionNUXT_ENV_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envNUXT_ENV_VERCEL_URL=my-site.vercel.appNUXT_ENV_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envNUXT_ENV_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appNUXT_ENV_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envNUXT_ENV_VERCEL_PROJECT_PRODUCTION_URL=my-site.comNUXT_ENV_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envNUXT_ENV_VERCEL_GIT_PROVIDER=githubNUXT_ENV_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envNUXT_ENV_VERCEL_GIT_REPO_SLUG=my-siteNUXT_ENV_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envNUXT_ENV_VERCEL_GIT_REPO_OWNER=acmeNUXT_ENV_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envNUXT_ENV_VERCEL_GIT_REPO_ID=117716146NUXT_ENV_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envNUXT_ENV_VERCEL_GIT_COMMIT_REF=improve-about-pageNUXT_ENV_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envNUXT_ENV_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081NUXT_ENV_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envNUXT_ENV_VERCEL_GIT_COMMIT_MESSAGE=Update about pageNUXT_ENV_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envNUXT_ENV_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeNUXT_ENV_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envNUXT_ENV_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeNUXT_ENV_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envNUXT_ENV_VERCEL_GIT_PULL_REQUEST_ID=23REACT_APP_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envREACT_APP_VERCEL_ENV=productionREACT_APP_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envREACT_APP_VERCEL_TARGET_ENV=productionREACT_APP_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envREACT_APP_VERCEL_URL=my-site.vercel.appREACT_APP_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envREACT_APP_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appREACT_APP_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envREACT_APP_VERCEL_PROJECT_PRODUCTION_URL=my-site.comREACT_APP_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envREACT_APP_VERCEL_GIT_PROVIDER=githubREACT_APP_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envREACT_APP_VERCEL_GIT_REPO_SLUG=my-siteREACT_APP_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envREACT_APP_VERCEL_GIT_REPO_OWNER=acmeREACT_APP_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envREACT_APP_VERCEL_GIT_REPO_ID=117716146REACT_APP_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envREACT_APP_VERCEL_GIT_COMMIT_REF=improve-about-pageREACT_APP_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envREACT_APP_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081REACT_APP_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envREACT_APP_VERCEL_GIT_COMMIT_MESSAGE=Update about pageREACT_APP_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envREACT_APP_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeREACT_APP_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envREACT_APP_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeREACT_APP_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envREACT_APP_VERCEL_GIT_PULL_REQUEST_ID=23GATSBY_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envGATSBY_VERCEL_ENV=productionGATSBY_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envGATSBY_VERCEL_TARGET_ENV=productionGATSBY_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envGATSBY_VERCEL_URL=my-site.vercel.appGATSBY_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envGATSBY_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appGATSBY_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envGATSBY_VERCEL_PROJECT_PRODUCTION_URL=my-site.comGATSBY_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envGATSBY_VERCEL_GIT_PROVIDER=githubGATSBY_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envGATSBY_VERCEL_GIT_REPO_SLUG=my-siteGATSBY_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envGATSBY_VERCEL_GIT_REPO_OWNER=acmeGATSBY_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envGATSBY_VERCEL_GIT_REPO_ID=117716146GATSBY_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envGATSBY_VERCEL_GIT_COMMIT_REF=improve-about-pageGATSBY_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envGATSBY_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081GATSBY_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envGATSBY_VERCEL_GIT_COMMIT_MESSAGE=Update about pageGATSBY_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envGATSBY_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeGATSBY_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envGATSBY_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeGATSBY_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envGATSBY_VERCEL_GIT_PULL_REQUEST_ID=23VITE_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envVITE_VERCEL_ENV=productionVITE_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envVITE_VERCEL_TARGET_ENV=productionVITE_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envVITE_VERCEL_URL=my-site.vercel.appVITE_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envVITE_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appVITE_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envVITE_VERCEL_PROJECT_PRODUCTION_URL=my-site.comVITE_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envVITE_VERCEL_GIT_PROVIDER=githubVITE_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_SLUG=my-siteVITE_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_OWNER=acmeVITE_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_ID=117716146VITE_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envVITE_VERCEL_GIT_COMMIT_REF=improve-about-pageVITE_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envVITE_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081VITE_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envVITE_VERCEL_GIT_COMMIT_MESSAGE=Update about pageVITE_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envVITE_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeVITE_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envVITE_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeVITE_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envVITE_VERCEL_GIT_PULL_REQUEST_ID=23VITE_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envVITE_VERCEL_ENV=productionVITE_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envVITE_VERCEL_TARGET_ENV=productionVITE_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envVITE_VERCEL_URL=my-site.vercel.appVITE_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envVITE_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appVITE_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envVITE_VERCEL_PROJECT_PRODUCTION_URL=my-site.comVITE_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envVITE_VERCEL_GIT_PROVIDER=githubVITE_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_SLUG=my-siteVITE_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_OWNER=acmeVITE_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_ID=117716146VITE_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envVITE_VERCEL_GIT_COMMIT_REF=improve-about-pageVITE_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envVITE_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081VITE_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envVITE_VERCEL_GIT_COMMIT_MESSAGE=Update about pageVITE_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envVITE_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeVITE_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envVITE_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeVITE_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envVITE_VERCEL_GIT_PULL_REQUEST_ID=23PUBLIC_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envPUBLIC_VERCEL_ENV=productionPUBLIC_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envPUBLIC_VERCEL_TARGET_ENV=productionPUBLIC_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envPUBLIC_VERCEL_URL=my-site.vercel.appPUBLIC_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envPUBLIC_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appPUBLIC_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envPUBLIC_VERCEL_PROJECT_PRODUCTION_URL=my-site.comPUBLIC_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envPUBLIC_VERCEL_GIT_PROVIDER=githubPUBLIC_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envPUBLIC_VERCEL_GIT_REPO_SLUG=my-sitePUBLIC_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envPUBLIC_VERCEL_GIT_REPO_OWNER=acmePUBLIC_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envPUBLIC_VERCEL_GIT_REPO_ID=117716146PUBLIC_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envPUBLIC_VERCEL_GIT_COMMIT_REF=improve-about-pagePUBLIC_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envPUBLIC_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081PUBLIC_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envPUBLIC_VERCEL_GIT_COMMIT_MESSAGE=Update about pagePUBLIC_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envPUBLIC_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoePUBLIC_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envPUBLIC_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoePUBLIC_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envPUBLIC_VERCEL_GIT_PULL_REQUEST_ID=23VITE_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envVITE_VERCEL_ENV=productionVITE_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envVITE_VERCEL_TARGET_ENV=productionVITE_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envVITE_VERCEL_URL=my-site.vercel.appVITE_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envVITE_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appVITE_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envVITE_VERCEL_PROJECT_PRODUCTION_URL=my-site.comVITE_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envVITE_VERCEL_GIT_PROVIDER=githubVITE_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_SLUG=my-siteVITE_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_OWNER=acmeVITE_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_ID=117716146VITE_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envVITE_VERCEL_GIT_COMMIT_REF=improve-about-pageVITE_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envVITE_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081VITE_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envVITE_VERCEL_GIT_COMMIT_MESSAGE=Update about pageVITE_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envVITE_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeVITE_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envVITE_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeVITE_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envVITE_VERCEL_GIT_PULL_REQUEST_ID=23VUE_APP_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envVUE_APP_VERCEL_ENV=productionVUE_APP_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envVUE_APP_VERCEL_TARGET_ENV=productionVUE_APP_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envVUE_APP_VERCEL_URL=my-site.vercel.appVUE_APP_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envVUE_APP_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appVUE_APP_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envVUE_APP_VERCEL_PROJECT_PRODUCTION_URL=my-site.comVUE_APP_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envVUE_APP_VERCEL_GIT_PROVIDER=githubVUE_APP_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envVUE_APP_VERCEL_GIT_REPO_SLUG=my-siteVUE_APP_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envVUE_APP_VERCEL_GIT_REPO_OWNER=acmeVUE_APP_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envVUE_APP_VERCEL_GIT_REPO_ID=117716146VUE_APP_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envVUE_APP_VERCEL_GIT_COMMIT_REF=improve-about-pageVUE_APP_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envVUE_APP_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081VUE_APP_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envVUE_APP_VERCEL_GIT_COMMIT_MESSAGE=Update about pageVUE_APP_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envVUE_APP_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeVUE_APP_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envVUE_APP_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeVUE_APP_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envVUE_APP_VERCEL_GIT_PULL_REQUEST_ID=23REDWOOD_ENV_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envREDWOOD_ENV_VERCEL_ENV=productionREDWOOD_ENV_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envREDWOOD_ENV_VERCEL_TARGET_ENV=productionREDWOOD_ENV_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envREDWOOD_ENV_VERCEL_URL=my-site.vercel.appREDWOOD_ENV_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envREDWOOD_ENV_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appREDWOOD_ENV_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envREDWOOD_ENV_VERCEL_PROJECT_PRODUCTION_URL=my-site.comREDWOOD_ENV_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envREDWOOD_ENV_VERCEL_GIT_PROVIDER=githubREDWOOD_ENV_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envREDWOOD_ENV_VERCEL_GIT_REPO_SLUG=my-siteREDWOOD_ENV_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envREDWOOD_ENV_VERCEL_GIT_REPO_OWNER=acmeREDWOOD_ENV_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envREDWOOD_ENV_VERCEL_GIT_REPO_ID=117716146REDWOOD_ENV_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envREDWOOD_ENV_VERCEL_GIT_COMMIT_REF=improve-about-pageREDWOOD_ENV_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envREDWOOD_ENV_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081REDWOOD_ENV_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envREDWOOD_ENV_VERCEL_GIT_COMMIT_MESSAGE=Update about pageREDWOOD_ENV_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envREDWOOD_ENV_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeREDWOOD_ENV_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envREDWOOD_ENV_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeREDWOOD_ENV_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envREDWOOD_ENV_VERCEL_GIT_PULL_REQUEST_ID=23PUBLIC_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envPUBLIC_VERCEL_ENV=productionPUBLIC_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envPUBLIC_VERCEL_TARGET_ENV=productionPUBLIC_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envPUBLIC_VERCEL_URL=my-site.vercel.appPUBLIC_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envPUBLIC_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appPUBLIC_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envPUBLIC_VERCEL_PROJECT_PRODUCTION_URL=my-site.comPUBLIC_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envPUBLIC_VERCEL_GIT_PROVIDER=githubPUBLIC_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envPUBLIC_VERCEL_GIT_REPO_SLUG=my-sitePUBLIC_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envPUBLIC_VERCEL_GIT_REPO_OWNER=acmePUBLIC_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envPUBLIC_VERCEL_GIT_REPO_ID=117716146PUBLIC_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envPUBLIC_VERCEL_GIT_COMMIT_REF=improve-about-pagePUBLIC_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envPUBLIC_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081PUBLIC_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envPUBLIC_VERCEL_GIT_COMMIT_MESSAGE=Update about pagePUBLIC_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envPUBLIC_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoePUBLIC_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envPUBLIC_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoePUBLIC_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envPUBLIC_VERCEL_GIT_PULL_REQUEST_ID=23VITE_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envVITE_VERCEL_ENV=productionVITE_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envVITE_VERCEL_TARGET_ENV=productionVITE_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envVITE_VERCEL_URL=my-site.vercel.appVITE_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envVITE_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appVITE_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envVITE_VERCEL_PROJECT_PRODUCTION_URL=my-site.comVITE_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envVITE_VERCEL_GIT_PROVIDER=githubVITE_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_SLUG=my-siteVITE_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_OWNER=acmeVITE_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envVITE_VERCEL_GIT_REPO_ID=117716146VITE_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envVITE_VERCEL_GIT_COMMIT_REF=improve-about-pageVITE_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envVITE_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081VITE_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envVITE_VERCEL_GIT_COMMIT_MESSAGE=Update about pageVITE_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envVITE_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeVITE_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envVITE_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeVITE_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envVITE_VERCEL_GIT_PULL_REQUEST_ID=23SANITY_STUDIO_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envSANITY_STUDIO_VERCEL_ENV=productionSANITY_STUDIO_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envSANITY_STUDIO_VERCEL_TARGET_ENV=productionSANITY_STUDIO_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envSANITY_STUDIO_VERCEL_URL=my-site.vercel.appSANITY_STUDIO_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envSANITY_STUDIO_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appSANITY_STUDIO_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envSANITY_STUDIO_VERCEL_PROJECT_PRODUCTION_URL=my-site.comSANITY_STUDIO_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envSANITY_STUDIO_VERCEL_GIT_PROVIDER=githubSANITY_STUDIO_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envSANITY_STUDIO_VERCEL_GIT_REPO_SLUG=my-siteSANITY_STUDIO_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envSANITY_STUDIO_VERCEL_GIT_REPO_OWNER=acmeSANITY_STUDIO_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envSANITY_STUDIO_VERCEL_GIT_REPO_ID=117716146SANITY_STUDIO_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envSANITY_STUDIO_VERCEL_GIT_COMMIT_REF=improve-about-pageSANITY_STUDIO_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envSANITY_STUDIO_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081SANITY_STUDIO_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envSANITY_STUDIO_VERCEL_GIT_COMMIT_MESSAGE=Update about pageSANITY_STUDIO_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envSANITY_STUDIO_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeSANITY_STUDIO_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envSANITY_STUDIO_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeSANITY_STUDIO_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envSANITY_STUDIO_VERCEL_GIT_PULL_REQUEST_ID=23SANITY_STUDIO_VERCEL_ENVThe environment that the app is deployed and running on. The value can be either production, preview, or development..envSANITY_STUDIO_VERCEL_ENV=productionSANITY_STUDIO_VERCEL_TARGET_ENVThe system or custom environment that the app is deployed and running on. The value can be either production, preview, development, or the name of a custom environment..envSANITY_STUDIO_VERCEL_TARGET_ENV=productionSANITY_STUDIO_VERCEL_URLThe domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol scheme https://..envSANITY_STUDIO_VERCEL_URL=my-site.vercel.appSANITY_STUDIO_VERCEL_BRANCH_URLThe domain name of the generated Git branch URL. Example: -git-.vercel.app. The value does not include the protocol scheme https://..envSANITY_STUDIO_VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.appSANITY_STUDIO_VERCEL_PROJECT_PRODUCTION_URLA production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://..envSANITY_STUDIO_VERCEL_PROJECT_PRODUCTION_URL=my-site.comSANITY_STUDIO_VERCEL_GIT_PROVIDERThe Git Provider the deployment is triggered from..envSANITY_STUDIO_VERCEL_GIT_PROVIDER=githubSANITY_STUDIO_VERCEL_GIT_REPO_SLUGThe origin repository the deployment is triggered from..envSANITY_STUDIO_VERCEL_GIT_REPO_SLUG=my-siteSANITY_STUDIO_VERCEL_GIT_REPO_OWNERThe account that owns the repository the deployment is triggered from..envSANITY_STUDIO_VERCEL_GIT_REPO_OWNER=acmeSANITY_STUDIO_VERCEL_GIT_REPO_IDThe ID of the repository the deployment is triggered from..envSANITY_STUDIO_VERCEL_GIT_REPO_ID=117716146SANITY_STUDIO_VERCEL_GIT_COMMIT_REFThe git branch of the commit the deployment was triggered by..envSANITY_STUDIO_VERCEL_GIT_COMMIT_REF=improve-about-pageSANITY_STUDIO_VERCEL_GIT_COMMIT_SHAThe git SHA of the commit the deployment was triggered by..envSANITY_STUDIO_VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081SANITY_STUDIO_VERCEL_GIT_COMMIT_MESSAGEThe message attached to the commit the deployment was triggered by. The message is truncated if it exceeds 2048 bytes..envSANITY_STUDIO_VERCEL_GIT_COMMIT_MESSAGE=Update about pageSANITY_STUDIO_VERCEL_GIT_COMMIT_AUTHOR_LOGINThe username attached to the author of the commit that the project was deployed by..envSANITY_STUDIO_VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoeSANITY_STUDIO_VERCEL_GIT_COMMIT_AUTHOR_NAMEThe name attached to the author of the commit that the project was deployed by..envSANITY_STUDIO_VERCEL_GIT_COMMIT_AUTHOR_NAME=John DoeSANITY_STUDIO_VERCEL_GIT_PULL_REQUEST_IDThe pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string..envSANITY_STUDIO_VERCEL_GIT_PULL_REQUEST_ID=23Was this helpful? supported.Send

production

Pattern 5: MenuConfiguring a BuildCopy pageAsk AI about this pageLast updated September 24, 2025When you make a deployment, Vercel builds your project. During this time, Vercel performs a "shallow clone" on your Git repository using the command and fetches ten levels of git commit history. This means that only the latest ten commits are pulled and not the entire repository history. Vercel automatically configures the build settings for many front-end frameworks, but you can also customize the build according to your requirements. To configure your Vercel build with customized settings, choose a project from the dashboard and go to its Settings tab. The Build and Deployment section of the Settings tab offers the following options to customize your build settings: Framework Settings Root Directory Node.js Version Prioritizing Production Builds On-Demand Concurrent Builds Framework Settings If you'd like to override the settings or specify a different framework, you can do so from the Build & Development Settings section. Framework settings. Framework Preset You have a wide range of frameworks to choose from, including Next.js, Svelte, and Nuxt. In several use cases, Vercel automatically detects your project's framework and sets the best settings for you. Inside the Framework Preset settings, use the drop-down menu to select the framework of your choice. This selection will be used for all deployments within your Project. The available frameworks are listed below: Show More However, if no framework is detected, "Other" will be selected. In this case, the Override toggle for the Build Command will be enabled by default so that you can enter the build command manually. The remaining deployment process is that for default frameworks. If you would like to override Framework Preset for a specific deployment, add to your configuration. Build Command Vercel automatically configures the Build Command based on the framework. Depending on the framework, the Build Command can refer to the project’s file. For example, if Next.js is your framework: Vercel checks for the command in and uses this to build the project If not, the will be triggered as the default Build Command If you'd like to override the Build Command for all deployments in your Project, you can turn on the Override toggle and specify the custom command. If you would like to override the Build Command for a specific deployment, add to your configuration. If you update the Override setting, it will be applied on your next deployment. Output Directory After building a project, most frameworks output the resulting build in a directory. Only the contents of this Output Directory will be served statically by Vercel. If Vercel detects a framework, the output directory will automatically be configured. If you update the Override setting, it will be applied on your next deployment. For projects that do not require building, you might want to serve the files in the root directory. In this case, do the following: Choose "Other" as the Framework Preset. This sets the output directory as if it exists or (root directory of the project) otherwise If your project doesn’t have a directory, it will serve the files from the root directory Alternatively, you can turn on the Override toggle and leave the field empty (in which case, the build step will be skipped) If you would like to override the Output Directory for a specific deployment, add to your configuration. Install Command Vercel auto-detects the install command during the build step. It installs dependencies from , including (which can be excluded). The install path is set by the root directory. The install command can be managed in two ways: through a project override, or per-deployment. See manually specifying a package manager for more details. To learn what package managers are supported on Vercel, see the package manager support documentation. Corepack Corepack is considered experimental and therefore, breaking changes or removal may occur in any future release of Node.js. Corepack is an experimental tool that allows a Node.js project to pin a specific version of a package manager. You can enable Corepack by adding an environment variable with name and value to your Project. Then, set the property in the file in the root of your repository. For example: A package.json file with pnpm version 7.5.1 Custom Install Command for your API The Install Command defined in the Project Settings will be used for front-end frameworks that support Vercel functions for APIs. If you're using Vercel functions defined in the natively supported directory, a different Install Command will be used depending on the language of the Vercel Function. You cannot customize this Install Command. Development Command This setting is relevant only if you’re using locally to develop your project. Use only if you need to use Vercel platform features like Vercel functions. Otherwise, it's recommended to use the development command your framework provides (such as for Next.js). The Development Command settings allow you to customize the behavior of . If Vercel detects a framework, the development command will automatically be configured. If you’d like to use a custom command for vercel dev, you can turn on the Override toggle. Please note the following: If you specify a custom command, your command must pass your framework's variable (which contains the port number). For example, in Next.js you should use: If the development command is not specified, will fail. If you've selected "Other" as the framework preset, the default development command will be empty You must create a deployment and have your local project linked to the project on Vercel (using ). Otherwise, will not work correctly If you would like to override the Development Command, add to your configuration. Skip Build Step Some static projects do not require building. For example, a website with only HTML/CSS/JS source files can be served as-is. In such cases, you should: Specify "Other" as the framework preset Enable the Override option for the Build Command Leave the Build Command empty This prevents running the build, and your content is served directly. Root Directory In some projects, the top-level directory of the repository may not be the root directory of the app you’d like to build. For example, your repository might have a front-end directory containing a stand-alone Next.js app. For such cases, you can specify the project Root Directory. If you do so, please note the following: Your app will not be able to access files outside of that directory. You also cannot use to move up a level This setting also applies to Vercel CLI. Instead of running to deploy, specify here so you can just run To configure the Root Directory: Navigate to the Build and Deployment page of your Project Settings Scroll down to Root Directory Enter the path to the root directory of your app Click Save to apply the changes If you update the root directory setting, it will be applied on your next deployment. Skipping unaffected projects In a monorepo, you can skip deployments for projects that were not affected by a commit. To configure: Navigate to the Build and Deployment page of your Project Settings Scroll down to Root Directory Enable the Skip deployment switch Was this helpful? supported.Send

package.json

Pattern 6: MenuUsing the Python Runtime with Vercel FunctionsCopy pageAsk AI about this pageLast updated November 3, 2025The Python runtime is available in Beta on all plans The Python runtime enables you to write Python code, including using FastAPI, Django, and Flask, with Vercel Functions. You can create your first function, available at the route, as follows: A hello world Python API using Vercel functions. Python version The current available version is Python 3.12. This cannot be changed. Dependencies You can install dependencies for your Python projects by defining them in a with or without a corresponding , , or a with corresponding . An example requirements.txt file that defines FastAPI as a dependency. An example pyproject.toml file that defines FastAPI as a dependency. Streaming Python functions Vercel Functions support streaming responses when using the Python runtime. This allows you to render parts of the UI as they become ready, letting users interact with your app before the entire page finishes loading. Controlling what gets bundled By default, Python Vercel Functions include all files from your project that are reachable at build time. Unlike the Node.js runtime, there is no automatic tree-shaking to remove dead code or unused dependencies. You should make sure your or only lists packages necessary for runtime and you should also explicitly exclude files you don't need in your functions to keep bundles small and avoid hitting size limits. Python functions have a maximum uncompressed bundle size of 250 MB. See the bundle size limits. To exclude unnecessary files (for example: tests, static assets, and test data), configure in under the key. The pattern is a glob relative to your project root. Exclude common development and static folders from all Python functions to stay under the 250 MB bundle limit. Using FastAPI with Vercel FastAPI is a modern, high-performance, web framework for building APIs with Python. For information on how to use FastAPI with Vercel, review this guide. Using Flask with Vercel Flask is a lightweight WSGI web application framework. For information on how to use Flask with Vercel, review this guide. Other Python Frameworks For FastAPI, Flask, or basic usage of the Python runtime, no configuration is required. Usage of the Python runtime with other frameworks, including Django, requires some configuration. The entry point of this runtime is a glob matching source files with one of the following variables defined: that inherits from the class that exposes a WSGI or ASGI Application Reading Relative Files in Python Python uses the current working directory when a relative file is passed to open(). The current working directory is the base of your project, not the directory. For example, the following directory structure: With the above directory structure, your function in can read the contents of in a couple different ways. You can use the path relative to the project's base directory. Or you can use the path relative to the current file's directory. Web Server Gateway Interface The Web Server Gateway Interface (WSGI) is a calling convention for web servers to forward requests to web applications written in Python. You can use WSGI with frameworks such as Flask or Django. Deploy an example with Flask Deploy an example with Django Asynchronous Server Gateway Interface The Asynchronous Server Gateway Interface (ASGI) is a calling convention for web servers to forward requests to asynchronous web applications written in Python. You can use ASGI with frameworks such as Sanic. Instead of defining a , define an variable in your Python file. For example, define a file as follows: An example api/index.py file, using Sanic for a ASGI application. Inside define: An example requirements.txt file, listing sanic as a dependency.Was this helpful? supported.Send

requirements.txt

Pattern 7: To exclude unnecessary files (for example: tests, static assets, and test data), configure in under the key. The pattern is a glob relative to your project root.

api/index.py

Pattern 8: MenuConfiguring the Runtime for Vercel FunctionsCopy pageAsk AI about this pageLast updated May 21, 2025The runtime of your function determines the environment in which your function will execute. Vercel supports various runtimes including Node.js, Python, Ruby, and Go. You can also configure other runtimes using the file. Here's how to set up each: Node.js By default, a function with no additional configuration will be deployed as a Vercel Function on the Node.js runtime. If you're not using a framework, you must either add "type": "module" to your package.json or change your JavaScript Functions' file extensions from .js to .mjs Go For Go, expose a single HTTP handler from a file within an directory at your project's root. For example: Python For Python, create a function by adding the following code to : Ruby For Ruby, define an HTTP handler from files within an directory at your project's root. Ruby files must have one of the following variables defined: proc that matches the signature class that inherits from the class For example: Don't forget to define your dependencies inside a : Other runtimes You can configure other runtimes by using the property in your file. For example: In this case, the function at would use the custom runtime specified. For more information, see Community runtimesWas this helpful? supported.Send

"type": "module"

Example Code Patterns

Example 1 (bash):

VERCEL_ENV=production

Example 2 (bash):

VERCEL_ENV=production

Reference Files

This skill includes comprehensive documentation in references/:

cli.md - Cli documentation
configuration.md - Configuration documentation
deployments.md - Deployments documentation
domains.md - Domains documentation
frameworks.md - Frameworks documentation
functions.md - Functions documentation
getting_started.md - Getting Started documentation
monitoring.md - Monitoring documentation
other.md - Other documentation
security.md - Security documentation
storage.md - Storage documentation

Use view to read specific reference files when detailed information is needed.

Working with This Skill

For Beginners

Start with the getting_started or tutorials reference files for foundational concepts.

For Specific Features

Use the appropriate category reference file (api, guides, etc.) for detailed information.

For Code Examples

The quick reference section above contains common patterns extracted from the official docs.

Resources

references/

Organized documentation extracted from official sources. These files contain:

Detailed explanations
Code examples with language annotations
Links to original documentation
Table of contents for quick navigation

scripts/

Add helper scripts here for common automation tasks.

assets/

Add templates, boilerplate, or example projects here.

Notes

This skill was automatically generated from official documentation
Reference files preserve the structure and examples from source docs
Code examples include language detection for better syntax highlighting
Quick reference patterns are extracted from common usage examples in the docs

Updating

To refresh this skill with updated documentation:

Re-run the scraper with the same configuration
The skill will be rebuilt with the latest information

vercel

SKILL.md