Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
11 KiB
@astrojs/vercel
2.0.0
Major Changes
1.0.2
Patch Changes
- #4558
742966456
Thanks @tony-sull! - Adding thewithastro
keyword to include the adapters on the Integrations Catalog
1.0.1
Patch Changes
- #4421
7820096e1
Thanks @bholmesdev! - Fix react-dom on Vercel edge
1.0.0
Major Changes
-
04ad44563
- > Astro v1.0 is out! Read the official announcement post.No breaking changes. This package is now officially stable and compatible with
astro@1.0.0
!
Patch Changes
- Updated dependencies [
04ad44563
]:- @astrojs/webapi@1.0.0
0.4.0
Minor Changes
0.3.0
Minor Changes
-
#4015
6fd161d76
Thanks @matthewp! - Newoutput
configuration optionThis change introduces a new "output target" configuration option (
output
). Setting the output target lets you decide the format of your final build, either:"static"
(default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host."server"
: A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.
If
output
is omitted from your config, the default value"static"
will be used.When using the
"server"
output target, you must also include a runtime adapter via theadapter
configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).To migrate: No action is required for most users. If you currently define an
adapter
, you will need to also addoutput: 'server'
to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:import { defineConfig } from 'astro/config'; import netlify from '@astrojs/netlify/functions'; export default defineConfig({ adapter: netlify(), + output: 'server', });
-
#3973
5a23483ef
Thanks @matthewp! - Adds support for Astro.clientAddressThe new
Astro.clientAddress
property allows you to get the IP address of the requested user.This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.
- #4020
1666fdb4c
Thanks @JuanM04! - Removed requirement forENABLE_VC_BUILD=1
, since Build Output v3 is now stable. Learn more.
0.2.6
Patch Changes
0.2.5
Patch Changes
- #3854
b012ee55
Thanks @bholmesdev! - [astro add] Support adapters and third party packages
0.2.4
Patch Changes
0.2.3
Patch Changes
- Updated dependencies [
4de53ecc
]:- @astrojs/webapi@0.12.0
0.2.2
Patch Changes
- #3368
9d01f93b
Thanks @JuanM04! - RemovenodeVersion
option forserverless
target. Now it is inferred from Vercel
0.2.1
Patch Changes
0.2.0
Minor Changes
-
#3216
114bf63e
Thanks @JuanM04! - [BREAKING] Now with Build Output API (v3)! See the README to get started.trailingSlash
redirects works without avercel.json
file: just configure them inside yourastro.config.mjs
- Multiple deploy targets:
edge
,serverless
andstatic
! - When building to
serverless
, your code isn't transpiled to CJS anymore.
Migrate from v0.1
- Change the import inside
astro.config.mjs
:- import vercel from '@astrojs/vercel'; + import vercel from '@astrojs/vercel/serverless';
- Rename the
ENABLE_FILE_SYSTEM_API
environment variable toENABLE_VC_BUILD
, as Vercel changed it. - The output folder changed from
.output
to.vercel/output
— you may need to update your.gitignore
.
0.1.4
Patch Changes
cafd36ef
Thanks @FredKSchott! - Update README
0.1.3
Patch Changes
0.1.2
Patch Changes
0.1.1
Patch Changes
815d62f1
Thanks @FredKSchott! - no changes.
0.1.0
Patch Changes
- #3008
8bd49c95
Thanks @JuanM04! - Updated integrations'astro:build:done
hook: now it matches the client dist when using SSR
0.0.3-beta.1
Patch Changes
0.0.3-beta.0
Patch Changes
- #3008
8bd49c95
Thanks @JuanM04! - Updated integrations'astro:build:done
hook: now it matches the client dist when using SSR