Infrastructure/astro
0
Fork 0
mirror of https://github.com/withastro/astro.git synced 2024-12-23 21:53:55 -05:00
Code Issues Activity
astro/packages/integrations/vercel
History
Chris Swithinbank 1f9e4857ff
Integration README fixes (#3865) 
* Remove stray XML tag in sitemap integration README

* Fix link errors

* Add changeset
2022-07-08 21:56:24 +02:00
..
src Enables eslint on the full repo and adds a rule for no only() tests (#3659) 2022-06-22 15:59:49 +00:00
CHANGELOG.md [ci] release (#3774) 2022-06-30 11:39:44 -07:00
package.json [ci] release (#3774) 2022-06-30 11:39:44 -07:00
README.md Integration README fixes (#3865) 2022-07-08 21:56:24 +02:00
tsconfig.json Basic Filesystem API 2022-03-28 10:05:55 -03:00

README.md

@astrojs/vercel

This adapter allows Astro to deploy your SSR site to Vercel.

Why Astro Vercel

If you're using Astro as a static site builder—its behavior out of the box—you don't need an adapter.

If you wish to use server-side rendering (SSR), Astro requires an adapter that matches your deployment runtime.

Vercel 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

First, install the @astrojs/vercel package using your package manager. If you're using npm or aren't sure, run this in the terminal:

npm install @astrojs/vercel

Then, install this adapter in your astro.config.* file using the adapter property (note the import from @astrojs/vercel/serverless - see targets).

astro.config.mjs

import { defineConfig } from 'astro/config';
import vercel from '@astrojs/vercel/serverless';

export default defineConfig({
	adapter: vercel()
});

Targets

You can deploy to different targes:

  • edge: SSR inside an Edge function.
  • serverless: SSR inside a Node.js function.
  • static: generates a static website following Vercel's output formats, redirects, etc.

Note

: deploying to the Edge has its limitations. An edge function can't be more than 1 MB in size and they don't support native Node.js APIs, among others.

You can change where to target by changing the import:

import vercel from '@astrojs/vercel/edge';
import vercel from '@astrojs/vercel/serverless';
import vercel from '@astrojs/vercel/static';

Usage

📚 Read the full deployment guide here.

You can deploy by CLI (vercel deploy) or by connecting your new repo in the Vercel Dashboard. Alternatively, you can create a production build locally:

ENABLE_VC_BUILD=1 astro build
vercel deploy --prebuilt

Vercel's Build Output API must be enabled. You must enable it yourself by setting the environment variable: ENABLE_VC_BUILD=1.

// vercel.json
{
  "build": {
    "env": {
      "ENABLE_VC_BUILD": "1"
    }
  }
}

Learn more about setting enviroment variables in Vercel.

Configuration

This adapter does not expose any configuration options.

Examples

Troubleshooting

A few known complex packages (example: puppeteer) do not support bundling and therefore will not work properly with this adapter. By default, Vercel doesn't include npm installed files & packages from your project's ./node_modules folder. To address this, the @astrojs/vercel adapter automatically bundles your final build output using esbuild.

Contributing

This package is maintained by Astro's Core team. You're welcome to submit an issue or PR!

Changelog