@astrojs/ vercel
This content is not available in your language yet.
This adapter allows Astro to deploy your hybrid
or server
rendered site to Vercel.
If you’re using Astro as a static site builder, you don’t need an adapter.
Learn how to deploy your Astro site in our Vercel deployment guide.
Why Astro Vercel
Section titled Why Astro VercelVercel is a deployment platform that allows you to host your site by connecting directly to your GitHub repository. This adapter enhances the Astro build process to prepare your project for deployment through Vercel.
Installation
Section titled InstallationAstro includes an astro add
command to automate the setup of official integrations. If you prefer, you can install integrations manually instead.
Add the Vercel adapter to enable SSR in your Astro project with the following astro add
command. This will install @astrojs/vercel
and make the appropriate changes to your astro.config.mjs
file in one step.
Manual Install
Section titled Manual InstallFirst, add the @astrojs/vercel
adapter to your project’s dependencies using your preferred package manager:
Then, add the adapter and your desired on-demand rendering mode to your astro.config.*
file:
Choosing a Target
Section titled Choosing a TargetYou can deploy to different targets:
serverless
: SSR inside a Node.js function.static
: generates a static website following Vercel’s output formats, redirects, etc.
You can change where to target by changing the import:
Usage
Section titled UsageYou can deploy by CLI (vercel deploy
) or by connecting your new repo in the Vercel Dashboard. Alternatively, you can create a production build locally:
Configuration
Section titled ConfigurationTo configure this adapter, pass an object to the vercel()
function call in astro.config.mjs
:
Web Analytics
Section titled Web AnalyticsType: VercelWebAnalyticsConfig
Available for: Serverless, Static
@astrojs/vercel@3.8.0
You can enable Vercel Web Analytics by setting webAnalytics: { enabled: true }
. This will inject Vercel’s tracking scripts into all of your pages.
imagesConfig
Section titled imagesConfigType: VercelImageConfig
Available for: Serverless, Static
@astrojs/vercel@3.3.0
Configuration options for Vercel’s Image Optimization API. See Vercel’s image configuration documentation for a complete list of supported parameters.
The domains
and remotePatterns
properties will automatically be filled using the Astro corresponding image
settings.
imageService
Section titled imageServiceType: boolean
Available for: Serverless, Static
@astrojs/vercel@3.3.0
When enabled, an Image Service powered by the Vercel Image Optimization API will be automatically configured and used in production. In development, the image service specified by devImageService
will be used instead.
devImageService
Section titled devImageServiceType: 'sharp' | 'squoosh' | string
Available for: Serverless, Static
@astrojs/vercel@3.8.0
Default: ‘sharp’
Allows you to configure which image service to use in development when imageService is enabled. This can be useful if you cannot install Sharp’s dependencies on your development machine, but using another image service like Squoosh would allow you to preview images in your dev environment. Build is unaffected and will always use Vercel’s Image Optimization.
It can also be set to any arbitrary value in order to use a custom image service instead of Astro’s built-in ones.
includeFiles
Section titled includeFilesType: string[]
Available for: Serverless
Use this property to force files to be bundled with your function. This is helpful when you notice missing files.
excludeFiles
Section titled excludeFilesType: string[]
Available for: Serverless
Use this property to exclude any files from the bundling process that would otherwise be included.
maxDuration
Section titled maxDurationType: number
Available for: Serverless
Use this property to extend or limit the maximum duration (in seconds) that Serverless Functions can run before timing out. See the Vercel documentation for the default and maximum limit for your account plan.
Function bundling configuration
Section titled Function bundling configurationThe Vercel adapter combines all of your routes into a single function by default.
You also have the option to split builds into a separate function for each route using the functionPerRoute
option. This reduces the size of each function, meaning you are less likely to exceed the size limit for an individual function. Also, code starts are faster.
Verify that your Vercel plan includes an appropriate number of functions before enabling functionPerRoute
. For example, Vercel’s free tier limits each deployment to no more than 12 functions. If your Vercel plan is insufficient for the number of routes in your project, you will receive an error message during deployment.
Vercel Edge Middleware
Section titled Vercel Edge MiddlewareYou can use Vercel Edge middleware to intercept a request and redirect before sending a response. Vercel middleware can run for Edge, SSR, and Static deployments. You may not need to install this package for your middleware. @vercel/edge
is only required to use some middleware features such as geolocation. For more information see Vercel’s middleware documentation.
-
Add a
middleware.js
file to the root of your project: -
While developing locally, you can run
vercel dev
to run middleware. In production, Vercel will handle this for you.
Trying to rewrite? Currently rewriting a request with middleware only works for static files.
Vercel Edge Middleware with Astro middleware
Section titled Vercel Edge Middleware with Astro middlewareThe @astrojs/vercel/serverless
adapter can automatically create the Vercel Edge middleware from an Astro middleware in your code base.
This is an opt-in feature, and the edgeMiddleware
option needs to be set to true
:
Optionally, you can create a file recognized by the adapter named vercel-edge-middleware.(js|ts)
in the srcDir
folder to create Astro.locals
.
Typings requires the @vercel/edge
package.
If you use TypeScript, you can type the function as follows:
The data returned by this function will be passed to Astro middleware.
The function:
- must export a default function;
- must return an
object
; - accepts an object with a
request
andcontext
as properties; request
is typed asRequest
;context
is typed asRequestContext
;
Limitations and constraints
Section titled Limitations and constraintsWhen you opt in to this feature, there are few constraints to note:
- The Vercel Edge middleware will always be the first function to receive the
Request
and the last function to receiveResponse
. This an architectural constraint that follows the boundaries set by Vercel. - Only
request
andcontext
may be used to produce anAstro.locals
object. Operations like redirects, etc. should be delegated to Astro middleware. Astro.locals
must be serializable. Failing to do so will result in a runtime error. This means that you cannot store complex types likeMap
,function
,Set
, etc.
Node.js Version Support
Section titled Node.js Version SupportThe @astrojs/vercel
adapter supports specific Node.js versions for deploying your Astro project on Vercel. To view the supported Node.js versions on Vercel, click on the settings tab for a project and scroll down to “Node.js Version” section.
Check out the Vercel documentation to learn more.