0
Fork 0
mirror of https://github.com/withastro/astro.git synced 2024-12-23 21:53:55 -05:00
astro/packages/integrations/vercel/README.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

27 lines
1.1 KiB
Markdown
Raw Normal View History

2022-03-29 21:11:27 -05:00
# @astrojs/vercel
2022-03-28 08:05:55 -05:00
2022-03-29 21:11:27 -05:00
Deploy your server-side rendered (SSR) Astro app to [Vercel](https://www.vercel.com/).
2022-03-28 08:05:55 -05:00
2022-03-29 21:11:27 -05:00
Use this integration in your Astro configuration file:
2022-03-28 08:05:55 -05:00
```js
import { defineConfig } from 'astro/config';
2022-03-29 21:11:27 -05:00
import vercel from '@astrojs/vercel';
2022-03-28 08:05:55 -05:00
export default defineConfig({
2022-03-31 13:12:43 -05:00
adapter: vercel()
2022-03-28 08:05:55 -05:00
});
```
After you build your site the `.output/` folder will contain your server-side rendered app. Since this feature is still in beta, you'll **need to add this Enviroment Variable to your Vercel project**: `ENABLE_FILE_SYSTEM_API=1`. [Learn how to set enviroment variables](https://vercel.com/docs/concepts/projects/environment-variables).
2022-03-28 08:05:55 -05:00
Now you can deploy!
```shell
2022-03-29 21:11:27 -05:00
vercel
2022-03-28 08:05:55 -05:00
```
2022-04-21 16:24:09 -05:00
## Limitations
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`. There is no action needed on your part to enable this, but be aware that some complex packages (example: [puppeteer](https://github.com/puppeteer/puppeteer)) do not support bundling and therefore will not work properly with this adapter.