@astrojs/ vercel
Ta treść nie jest jeszcze dostępna w Twoim języku.
This adapter allows Astro to deploy your on-demand rendered routes to Vercel.
If you’re using Astro as a static site builder, you only need this adapter if you are using additional Vercel services (e.g. Vercel Web Analytics, Vercel Image Optimization). Otherwise, you do not need an adapter to deploy your static
site.
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:
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
:
webAnalytics
Section titled webAnalyticsType: 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' | 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.
Type: boolean | VercelISRConfig
Available for: Serverless
@astrojs/vercel@7.2.0
Default: false
Allows your project to be deployed as an ISR (Incremental Static Regeneration) function, which caches your on-demand rendered pages in the same way as prerendered pages after first request.
To enable this feature, set isr
to true in your Vercel adapter configuration in astro.config.mjs
:
Note that ISR function requests do not include search params, similar to requests in static mode.
ISR cache invalidation
Section titled ISR cache invalidationBy default, an ISR function caches for the duration of your deployment. You can further control caching by setting an expiration time, or by excluding particular routes from caching entirely.
Time-based invalidation
Section titled Time-based invalidationYou can change the length of time to cache routes this by configuring an expiration
value in seconds:
Excluding paths from caching
Section titled Excluding paths from cachingTo implement Vercel’s Draft mode, or On-Demand Incremental Static Regeneration (ISR), you can create a bypass token and provide it to the isr
config along with any routes to exclude from caching:
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.
skewProtection
Section titled skewProtectionType: boolean
Available for: Serverless
@astrojs/vercel@7.6.0
Use this property to enable Vercel Skew protection (available with Vercel Pro and Enterprise accounts).
Running Astro middleware on Vercel Edge Functions
Section titled Running Astro middleware on Vercel Edge FunctionsThe @astrojs/vercel
adapter can create an edge function from an Astro middleware in your code base. When edgeMiddleware
is enabled, an edge function will execute your middleware code for all requests including static assets, prerendered pages, and on-demand rendered pages.
For on-demand rendered pages, the context.locals
object is serialized using JSON and sent in a header for the serverless function, which performs the rendering. As a security measure, the serverless function will refuse to serve requests with a 403 Forbidden
response unless they come from the generated edge function.
This is an opt-in feature. To enable it, set edgeMiddleware
to true
:
The edge middleware has access to Vercel’s RequestContext
as ctx.locals.vercel.edge
. If you’re using TypeScript, you can get proper typings by updating src/env.d.ts
to use EdgeLocals
:
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.