public-backup/astro
1
0
Fork 0
mirror of https://github.com/withastro/astro.git synced 2025-12-05 18:56:38 -06:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
astro/packages/integrations/vercel/CHANGELOG.md
Houston (Bot) 09bbdbb1e6 [ci] release (#14845) 
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2025-11-26 11:30:07 +01:00

133 KiB
Raw Permalink Blame History

@astrojs/vercel

9.0.2

Patch Changes

9.0.1

Patch Changes

  • Updated dependencies [9e9c528, 0f75f6b]:
    • @astrojs/internal-helpers@0.7.5

9.0.0

Major Changes

Minor Changes

  • #14543 9b3241d Thanks @matthewp! - Enables skew protection for Astro sites deployed on Vercel. Skew protection ensures that your site's client and server versions stay synchronized during deployments, preventing issues where users might load assets from a newer deployment while the server is still running the older version.

    Skew protection is automatically enabled on Vercel deployments when the VERCEL_SKEW_PROTECTION_ENABLED environment variable is set to 1. The deployment ID is automatically included in both asset requests and API calls, allowing Vercel to serve the correct version to every user.

8.2.11

Patch Changes

  • #14570 c96711d Thanks @matthewp! - Fix regression in 8.2.7: validate densities-based srcset widths against configured sizes

    When using densities with the Vercel image adapter, calculated widths were not being validated against Vercel's configured sizes list. This caused images to fail when using densities, as Vercel would reject the invalid widths.

    This fix ensures densities-calculated widths are mapped to valid configured sizes, matching the behavior already implemented for the widths prop.

8.2.10

Patch Changes

8.2.9

Patch Changes

8.2.8

Patch Changes

  • Updated dependencies [1e2499e]:
    • @astrojs/internal-helpers@0.7.3

8.2.7

Patch Changes

  • #14039 da4182d Thanks @ematipico! - Fixes a bug where experimentalStaticHeaders did not work as expected.

  • #14289 ed493a6 Thanks @ascorbic! - Fixes a bug that caused invalid image sizes to be generated when the requested widths were larger than the source image

8.2.6

Patch Changes

  • Updated dependencies [4d16de7]:
    • @astrojs/internal-helpers@0.7.2

8.2.5

Patch Changes

  • Updated dependencies [0567fb7]:
    • @astrojs/internal-helpers@0.7.1

8.2.4

Patch Changes

  • Updated dependencies [f4e8889]:
    • @astrojs/internal-helpers@0.7.0

8.2.3

Patch Changes

8.2.2

Patch Changes

  • #14063 de5a253 Thanks @RobbieTheWagner! - Allow setting domains to undefined in imagesConfig so that remotePatterns can be better utilized for images from a variety of domains.

8.2.1

Patch Changes

  • #13972 db8f8be Thanks @ematipico! - Fixes the internal implementation of the new feature experimentalStaticHeaders, where dynamic routes were mapped to use always the same header.

8.2.0

Minor Changes

  • #13965 95ece06 Thanks @ematipico! - Adds support for the experimental static headers Astro feature.

    When the feature is enabled via option experimentalStaticHeaders, and experimental Content Security Policy is enabled, the adapter will generate Response headers for static pages, which allows support for CSP directives that are not supported inside a <meta> tag (e.g. frame-ancestors).

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

export default defineConfig({
  adapter: vercel({
    experimentalStaticHeaders: true,
  }),
  experimental: {
    cps: true,
  },
});

Patch Changes

  • #13917 e615216 Thanks @ascorbic! - The responsive images feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.

    The new responsive images feature in Astro automatically generates optimized images for different screen sizes and resolutions, and applies the correct attributes to ensure that images are displayed correctly on all devices.

    Enable the image.responsiveStyles option in your Astro config. Then, set a layout attribute on any or component, or configure a default image.layout, for instantly responsive images with automatically generated srcset and sizes attributes based on the image's dimensions and the layout type.

    Displaying images correctly on the web can be challenging, and is one of the most common performance issues seen in sites. This new feature simplifies the most challenging part of the process: serving your site visitor an image optimized for their viewing experience, and for your website's performance.

    For full details, see the updated Image guide.

    Migration from Experimental Responsive Images

    The experimental.responsiveImages flag has been removed, and all experimental image configuration options have been renamed to their final names.

    If you were using the experimental responsive images feature, you'll need to update your configuration:

    Remove the experimental flag
    export default defineConfig({
   experimental: {
-    responsiveImages: true,
   },
});
    Update image configuration options

    During the experimental phase, default styles were applied automatically to responsive images. Now, you need to explicitly set the responsiveStyles option to true if you want these styles applied.

    export default defineConfig({
  image: {
+    responsiveStyles: true,
  },
});

    The experimental image configuration options have been renamed:

    Before:

    export default defineConfig({
  image: {
    experimentalLayout: 'constrained',
    experimentalObjectFit: 'cover',
    experimentalObjectPosition: 'center',
    experimentalBreakpoints: [640, 750, 828, 1080, 1280],
    experimentalDefaultStyles: true,
  },
  experimental: {
    responsiveImages: true,
  },
});

    After:

    export default defineConfig({
  image: {
    layout: 'constrained',
    objectFit: 'cover',
    objectPosition: 'center',
    breakpoints: [640, 750, 828, 1080, 1280],
    responsiveStyles: true, // This is now *false* by default
  },
});
    Component usage remains the same

    The layout, fit, and position props on <Image> and <Picture> components work exactly the same as before:

    <Image
  src={myImage}
  alt="A responsive image"
  layout="constrained"
  fit="cover"
  position="center"
/>

    If you weren't using the experimental responsive images feature, no changes are required.

    Please see the Image guide for more information on using responsive images in Astro.

  • Updated dependencies []:

    • @astrojs/underscore-redirects@1.0.0

8.1.5

Patch Changes

8.1.4

Patch Changes

8.1.3

Patch Changes

8.1.2

Patch Changes

  • Updated dependencies [042d1de]:
    • @astrojs/internal-helpers@0.6.1

8.1.1

Patch Changes

8.1.0

Minor Changes

  • #13211 7ea0aba Thanks @slawekkolodziej! - Adds support for regular expressions in ISR exclude list

    Previously, excluding a page from ISR required explicitly listing it in isr.exclude. As websites grew larger, maintaining this list became increasingly difficult, especially for multiple API routes and pages that needed server-side rendering.

    To address this, ISR exclusions now support regular expressions, allowing for more flexible and scalable configurations.

    // astro.config.mjs
import vercel from '@astrojs/vercel/serverless';

export default defineConfig({
  output: 'server',
  adapter: vercel({
    isr: {
      exclude: [
        '/preview', // Excludes a specific route (e.g., pages/preview.astro)
        '/auth/[page]', // Excludes a dynamic route (e.g., pages/auth/[page].astro)
        /^\/api\/.+/, // Excludes all routes starting with /api/
      ],
    },
  }),
});

Patch Changes

  • #13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

  • Updated dependencies [1e11f5e]:

    • @astrojs/internal-helpers@0.6.0

8.0.8

Patch Changes

8.0.7

Patch Changes

8.0.6

Patch Changes

8.0.5

Patch Changes

8.0.4

Patch Changes

  • #516 3fe04eb Thanks @ascorbic! - Fixes a bug that prevented integration-generated static assets from being deployed with non-static sites

8.0.3

Patch Changes

  • #508 af69a12 Thanks @ascorbic! - Fixes a bug that prevented static assets generated by integrations from being deployed

8.0.2

Patch Changes

8.0.1

Patch Changes

  • #472 d9eed7e Thanks @bluwy! - Add back support for Node 22 on Vercel serverless that was fixed in v7 but lost in v8

8.0.0

Major Changes

Minor Changes

  • #424 3351348 Thanks @ematipico! - Deprecates the entrypoints @astrojs/vercel/serverless and @astrojs/vercel/static. These will continue to work but are no longer documented and will be removed in a future version. We recommend updating to the @astrojs/vercel entrypoint as soon as you are able:

    -import vercel from "@astrojs/vercel/static"
+import vercel from "@astrojs/vercel"

    -import vercel from "@astrojs/vercel/serverless"
+import vercel from "@astrojs/vercel"

  • #447 7d9835f Thanks @laymonage! - Add support for Node 22 on Vercel serverless

  • #385 bb725b7 Thanks @florian-lefebvre! - Cleans up astro:env support

Patch Changes

  • #437 b725b49 Thanks @ematipico! - Fixes a regression where the @astrojs/vercel single entry point for the adapter was causing some regressions in users projects.

8.0.0-beta.4

Patch Changes

  • #437 b725b49 Thanks @ematipico! - Fixes a regression where the @astrojs/vercel single entry point for the adapter was causing some regressions in users projects.

8.0.0-beta.3

Major Changes

Minor Changes

  • #424 3351348 Thanks @ematipico! - Deprecates the entrypoints @astrojs/vercel/serverless and @astrojs/vercel/static. These will continue to work but are no longer documented and will be removed in a future version. We recommend updating to the @astrojs/vercel entrypoint as soon as you are able:

    -import vercel from "@astrojs/vercel/static"
+import vercel from "@astrojs/vercel"

    -import vercel from "@astrojs/vercel/serverless"
+import vercel from "@astrojs/vercel"

8.0.0-beta.2

Major Changes

  • #375 e7881f7 Thanks @Princesseuh! - Updates internal code to works with Astro 5 changes to hybrid rendering. No changes are necessary to your project, apart from using Astro 5

  • #397 776a266 Thanks @Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

    Starting from this release, no breaking changes will be introduced unless absolutely necessary.

    To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

  • #377 b77f99c Thanks @alexanderniebuhr! - Updates the adapter to use new IntegrationRouteData type

  • #392 3a49eb7 Thanks @Princesseuh! - Updates internal code for Astro 5 changes. No changes is required to your project, apart from using Astro 5

Minor Changes

7.8.2

Patch Changes

7.8.1

Patch Changes

8.0.0-alpha.1

Major Changes

  • #11679 ea71b90 Thanks @florian-lefebvre! - Adds stable support for astro:env

  • #11770 cfa6a47 Thanks @Princesseuh! - Removed support for the Squoosh image service. As the underlying library libsquoosh is no longer maintained, and the image service sees very little usage we have decided to remove it from Astro.

    Our recommendation is to use the base Sharp image service, which is more powerful, faster, and more actively maintained.

    - import { squooshImageService } from "astro/config";
import { defineConfig } from "astro/config";

export default defineConfig({
-  image: {
-    service: squooshImageService()
-  }
});

    If you are using this service, and cannot migrate to the base Sharp image service, a third-party extraction of the previous service is available here: https://github.com/Princesseuh/astro-image-service-squoosh

Patch Changes

  • #11783 fc81b01 Thanks @matthewp! - Prevent race condition with Node 18

    Using Node 18 there can be a race condition where polyfill for the crypto global is not applied in time. This change ensures the polyfills run first.

8.0.0-alpha.0

Major Changes

  • #11714 8a53517 Thanks @matthewp! - Remove support for functionPerRoute

    This change removes support for the functionPerRoute option both in Astro and @astrojs/vercel.

    This option made it so that each route got built as separate entrypoints so that they could be loaded as separate functions. The hope was that by doing this it would decrease the size of each function. However in practice routes use most of the same code, and increases in function size limitations made the potential upsides less important.

    Additionally there are downsides to functionPerRoute, such as hitting limits on the number of functions per project. The feature also never worked with some Astro features like i18n domains and request rewriting.

    Given this, the feature has been removed from Astro.

Patch Changes

7.8.0

Minor Changes

  • #11728 5ea02b1 Thanks @matthewp! - Deprecates the functionPerRoute option

    This option is now deprecated, and will be removed entirely in Astro v5.0. We suggest removing this option from your configuration as soon as you are able to:

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

export default defineConfig({
  // ...
  output: 'server',
  adapter: vercel({
-     functionPerRoute: true,
  }),
});

Patch Changes

  • #11783 fc81b01 Thanks @matthewp! - Prevent race condition with Node 18

    Using Node 18 there can be a race condition where polyfill for the crypto global is not applied in time. This change ensures the polyfills run first.

7.7.2

Patch Changes

7.7.1

Patch Changes

7.7.0

Minor Changes

7.6.0

Minor Changes

7.5.4

Patch Changes

  • #10833 8d5f3e8 Thanks @renovate! - Updates esbuild dependency to v0.20. This should not affect projects in most cases.

7.5.3

Patch Changes

7.5.2

Patch Changes

7.5.1

Patch Changes

7.5.0

Minor Changes

  • #10513 a573cc199a00d35410197ba4117c97764a984dc0 Thanks @tk04! - The isr.exclude configuration can now include routes with dynamic and spread parameters. 
    export default defineConfig({
    adapter: vercel({
        isr: {
            exclude: [
                "/blog/[title]"
                "/api/[...slug]",
            ]
        }
    })
})

7.4.1

Patch Changes

7.4.0

Minor Changes

  • #10476 cfbaa8a767b8794c2dcd8e164672195378be396a Thanks @lilnasy! - The special-case handling of src/vercel-edge-middleware.js file is now deprecated. This file allowed you to access the edge runtime's RequestContext object, and create the middleware locals from its fields. However, this object includes only one field - the waitUntil() function - which is now available directly as ctx.locals.vercel.edge.waitUntil().

7.3.6

Patch Changes

7.3.5

Patch Changes

7.3.4

Patch Changes

7.3.3

Patch Changes

7.3.2

Patch Changes

7.3.1

Patch Changes

7.3.0

Minor Changes

  • #9987 0699f34d5c4481c027c4d29d73944f79f97008df Thanks @lilnasy! - Implements verification for edge middleware. This is a security measure to ensure that your serverless functions are only ever called by your edge middleware and not a third party.

    When edgeMiddleware is enabled, the serverless function will now respond with 403 Forbidden for requests that are not verified to have come from the generated edge middleware. No user action is necessary.

7.2.0

Minor Changes

  • #9714 e2fe51c828dc7ea8204788e59e3953fe36c97836 Thanks @lilnasy! - Introduces a new config option, isr, that allows you to deploy your project as an ISR function. ISR (Incremental Static Regeneration) 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:

    export default defineConfig({
  output: 'server',
  adapter: vercel({ isr: true }),
});

    Cache invalidation options

    By default, ISR responses are cached for the duration of your deployment. You can further control caching by setting an expiration time or prevent caching entirely for certain routes.

    Time-based invalidation

    You can change the length of time to cache routes this by configuring an expiration value in seconds:

    export default defineConfig({
  output: 'server',
  adapter: vercel({
    isr: {
      // caches all pages on first request and saves for 1 day
      expiration: 60 * 60 * 24,
    },
  }),
});

    Manual invalidation

    To 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 the paths to exclude from caching:

    export default defineConfig({
  output: 'server',
  adapter: vercel({
    isr: {
      // A secret random string that you create.
      bypassToken: '005556d774a8',
      // Paths that will always be served fresh.
      exclude: ['/api/invalidate'],
    },
  }),
});

7.1.1

Patch Changes

7.1.0

Minor Changes

Patch Changes

  • #9885 49e0c24d7f90d00e986533fcf546665967540ce7 Thanks @matthewp! - Better ignores for Vercel file-tracer

    The Vercel adapter has a file-tracer it uses to detect which files should be moved over to the dist/ folder. When it's done, it prints warnings for things that it detected that maybe should be moved.

    This change expands how we do ignores so that:

    • Ignores happen within dot folders like .pnpm.
    • @libsql/client is ignored, a package we know is not bundled.

7.0.2

Patch Changes

7.0.1

Patch Changes

7.0.0

Major Changes

6.1.4

Patch Changes

6.1.3

Patch Changes

6.1.2

Patch Changes

6.1.1

Patch Changes

6.1.0

Minor Changes

Patch Changes

6.0.2

Patch Changes

6.0.1

Patch Changes

6.0.0

Major Changes

  • #9199 49aa215a0 Thanks @lilnasy! - The internals of the integration have been updated to support Astro 4.0. Make sure to upgrade your Astro version as Astro 3.0 is no longer supported.

  • #9184 a145ac07e Thanks @bluwy! - Removes deprecated analytics option. Use the webAnalytics option instead.

  • #9263 3cbd8ea75 Thanks @bluwy! - Removes the deprecated @astrojs/vercel/edge export. You should use @astrojs/vercel/serverless instead with the edgeMiddleware option.

6.0.0-beta.2

Major Changes

  • #9263 3cbd8ea75 Thanks @bluwy! - Removes the deprecated @astrojs/vercel/edge export. You should use @astrojs/vercel/serverless instead with the edgeMiddleware option.

6.0.0-beta.1

Major Changes

  • #9199 49aa215a0 Thanks @lilnasy! - The internals of the integration have been updated to support Astro 4.0. Make sure to upgrade your Astro version as Astro 3.0 is no longer supported.

6.0.0-beta.0

Major Changes

  • #9184 a145ac07e Thanks @bluwy! - Removes deprecated analytics option. Use the webAnalytics option instead.

Patch Changes

5.2.0

Minor Changes

  • #8879 754e4fd31 Thanks @lilnasy! - The Vercel adapter now streams responses!

    This brings better performance to your visitors by showing them content as it is rendered. The browser can also start loading the required stylesheets and scripts much sooner, which ultimately results in faster full page loads.

5.1.0

Minor Changes

  • #8867 b209e5335 Thanks @lilnasy! - You can now configure how long your functions can run before timing out.

    export default defineConfig({
    output: "server",
    adapter: vercel({
+       maxDuration: 60
    }),
});

Patch Changes

  • #8896 5dd1ed50b Thanks @bluwy! - Prevents the Vercel serverless adapter from generating static redirect pages in hybrid mode

  • Updated dependencies [26b77b8fe]:

    • astro@3.3.4

5.0.2

Patch Changes

5.0.1

Patch Changes

5.0.0

Major Changes

  • #8445 91380378c Thanks @Princesseuh! - Adds a configuration option devImageService to choose which of the built-in image services to use in development. Defaults to sharp.

  • #8546 b79e11f3c Thanks @matthewp! - Turn off functionPerRoute by default

    In the previous version of @astrojs/vercel, the default for functionPerRoute was changed to true. While this option has several advantages, if you're a free tier user you are likely to run into the limit of 12 functions per deployment. This will result in an error when you attempt to deploy.

    For this reason, the functionPerRoute option is now back to defaulting to false. It's still a useful option if you have a paid plan and have previously run into issues with your single function exceeding the size limits.

Minor Changes

  • #8021 2e8726fee Thanks @chriswdmr! - Enable Vercel Speed Insights and Vercel Web Analytics individually. Deprecates the analytics property in astro.config.mjs in favor of speedInsights and webAnalytics.

    If you're using the analytics property, you'll need to update your config to use the new properties:

    // astro.config.mjs
export default defineConfig({
	adapter: vercel({
-		analytics: true,
+		webAnalytics: {
+			enabled: true
+		},
+		speedInsights: {
+			enabled: true
+		}
	})
});

    Allow configuration of Web Analytics with all available configuration options. Bumps @vercel/analytics package to the latest version.

Patch Changes

4.0.5

Patch Changes

4.0.4

Patch Changes

4.0.3

Patch Changes

  • #8348 5f2c55bb5 Thanks @ematipico! - - Cache result during bundling, to speed up the process of multiple functions;

    • Avoid creating multiple symbolic links of the dependencies when building the project with functionPerRoute enabled;

  • #8354 0eb09dbab Thanks @Princesseuh! - Fix unnecessary warning about Sharp showing while building

  • Updated dependencies [d3a6f9f83, f21599671]:

    • astro@3.0.6

4.0.2

Patch Changes

4.0.1

Patch Changes

4.0.0

Major Changes

  • #8188 d0679a666 Thanks @ematipico! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.

  • #8179 6011d52d3 Thanks @matthewp! - Astro 3.0 Release Candidate

  • #8188 7511a4980 Thanks @ematipico! - When using an adapter that supports neither Squoosh or Sharp, Astro will now automatically use an image service that does not support processing, but still provides the other benefits of astro:assets such as enforcing alt, no CLS etc to users

  • #8015 9cc4e48e6 Thanks @matthewp! - Remove the Vercel Edge adapter

    @astrojs/vercel/serverless now supports Edge middleware, so a separate adapter for Edge itself (deploying your entire app to the edge) is no longer necessary. Please update your Astro config to reflect this change:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
- import vercel from '@astrojs/vercel/edge';
+ import vercel from '@astrojs/vercel/serverless';

export default defineConfig({
 output: 'server',
 adapter: vercel({
+    edgeMiddleware: true
 }),
});

    This adapter had several known limitations and compatibility issues that prevented many people from using it in production. To reduce maintenance costs and because we have a better story with Serveless + Edge Middleware, we are removing the Edge adapter.

  • #8239 52f0837bd Thanks @matthewp! - Vercel adapter now defaults to functionPerRoute.

    With this change, @astrojs/vercel/serverless now splits each route into its own function. By doing this, the size of each function is reduced and startup time is faster.

    You can disable this option, which will cause the code to be bundled into a single function, by setting functionPerRoute to false.

  • #8188 148e61d24 Thanks @ematipico! - Reduced the amount of polyfills provided by Astro. Astro will no longer provide (no-op) polyfills for several web apis such as HTMLElement, Image or Document. If you need access to those APIs on the server, we recommend using more proper polyfills available on npm.

Minor Changes

  • #8188 cd2d7e769 Thanks @ematipico! - Introduced the concept of feature map. A feature map is a list of features that are built-in in Astro, and an Adapter can tell Astro if it can support it.

    import { AstroIntegration } from './astro';

function myIntegration(): AstroIntegration {
  return {
    name: 'astro-awesome-list',
    // new feature map
    supportedAstroFeatures: {
      hybridOutput: 'experimental',
      staticOutput: 'stable',
      serverOutput: 'stable',
      assets: {
        supportKind: 'stable',
        isSharpCompatible: false,
        isSquooshCompatible: false,
      },
    },
  };
}

  • #8188 80f1494cd Thanks @ematipico! - The build.split and build.excludeMiddleware configuration options are deprecated and have been replaced by options in the adapter config.

    If your config includes the build.excludeMiddleware option, replace it with edgeMiddleware in your adapter options:

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

export default defineConfig({
     build: {
-        excludeMiddleware: true
     },
     adapter: vercel({
+        edgeMiddleware: true
     }),
});

    If your config includes the build.split option, replace it with functionPerRoute in your adapter options:

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

export default defineConfig({
     build: {
-        split: true
     },
     adapter: vercel({
+        functionPerRoute: true
     }),
});

Patch Changes

4.0.0-rc.5

Major Changes

  • #8239 52f0837bd Thanks @matthewp! - Vercel adapter now defaults to functionPerRoute.

    With this change, @astrojs/vercel/serverless now splits each route into its own function. By doing this, the size of each function is reduced and startup time is faster.

    You can disable this option, which will cause the code to be bundled into a single function, by setting functionPerRoute to false.

Patch Changes

4.0.0-rc.4

Major Changes

Patch Changes

4.0.0-beta.3

Patch Changes

4.0.0-beta.2

Patch Changes

  • Updated dependencies [2aa6d8ace]:
    • @astrojs/internal-helpers@0.2.0-beta.1
    • astro@3.0.0-beta.2

4.0.0-beta.1

Major Changes

  • #8015 9cc4e48e6 Thanks @matthewp! - Remove the Vercel Edge adapter

    @astrojs/vercel/serverless now supports Edge middleware, so a separate adapter for Edge itself (deploying your entire app to the edge) is no longer necessary. Please update your Astro config to reflect this change:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
- import vercel from '@astrojs/vercel/edge';
+ import vercel from '@astrojs/vercel/serverless';

export default defineConfig({
 output: 'server',
 adapter: vercel({
+    edgeMiddleware: true
 }),
});

    This adapter had several known limitations and compatibility issues that prevented many people from using it in production. To reduce maintenance costs and because we have a better story with Serveless + Edge Middleware, we are removing the Edge adapter.

Patch Changes

4.0.0-beta.0

Major Changes

  • 1eae2e3f7 Thanks @Princesseuh! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.

  • c022a4217 Thanks @Princesseuh! - When using an adapter that supports neither Squoosh or Sharp, Astro will now automatically use an image service that does not support processing, but still provides the other benefits of astro:assets such as enforcing alt, no CLS etc to users

  • 3dc1ca2fa Thanks @Princesseuh! - Reduced the amount of polyfills provided by Astro. Astro will no longer provide (no-op) polyfills for several web apis such as HTMLElement, Image or Document. If you need access to those APIs on the server, we recommend using more proper polyfills available on npm.

Minor Changes

  • 9b4f70a62 Thanks @ematipico! - Introduced the concept of feature map. A feature map is a list of features that are built-in in Astro, and an Adapter can tell Astro if it can support it.

    import { AstroIntegration } from './astro';

function myIntegration(): AstroIntegration {
  return {
    name: 'astro-awesome-list',
    // new feature map
    supportedAstroFeatures: {
      hybridOutput: 'experimental',
      staticOutput: 'stable',
      serverOutput: 'stable',
      assets: {
        supportKind: 'stable',
        isSharpCompatible: false,
        isSquooshCompatible: false,
      },
    },
  };
}

  • 3fdf509b2 Thanks @ematipico! - The build.split and build.excludeMiddleware configuration options are deprecated and have been replaced by options in the adapter config.

    If your config includes the build.excludeMiddleware option, replace it with edgeMiddleware in your adapter options:

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

export default defineConfig({
     build: {
-        excludeMiddleware: true
     },
     adapter: vercel({
+        edgeMiddleware: true
     }),
});

    If your config includes the build.split option, replace it with functionPerRoute in your adapter options:

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

export default defineConfig({
     build: {
-        split: true
     },
     adapter: vercel({
+        functionPerRoute: true
     }),
});

Patch Changes

3.8.2

Patch Changes

3.8.1

Patch Changes

3.8.0

Minor Changes

Patch Changes

3.7.5

Patch Changes

3.7.4

Patch Changes

3.7.3

Patch Changes

3.7.2

Patch Changes

  • #7659 57a5eff5c Thanks @natemoo-re! - Fix critical build regression. @vercel/nft is excluded from the bundle automatically.

3.7.1

Patch Changes

3.7.0

Minor Changes

  • #7532 9e5fafa2b Thanks @ematipico! - Support for Vercel Edge Middleware via Astro middleware.

    When a project uses the new option Astro build.excludeMiddleware, the @astrojs/vercel/serverless adapter will automatically create a Vercel Edge Middleware that will automatically communicate with the Astro Middleware.

    Check the documentation for more details.

Patch Changes

3.6.0

Minor Changes

  • #7514 154af8f5e Thanks @matthewp! - Split support in Vercel Serverless

    The Vercel adapter builds to a single function by default. Astro 2.7 added support for splitting your build into separate entry points per page. If you use this configuration the Vercel adapter will generate a separate function for each page. This can help reduce the size of each function so they are only bundling code used on that page.

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

export default defineConfig({
  output: 'server',
  adapter: vercel(),
  build: {
    split: true,
  },
});

Patch Changes

3.5.1

Patch Changes

3.5.0

Minor Changes

  • #7067 57f8d14c0 Thanks @matthewp! - Support for experimental redirects

    This adds support for the redirects RFC in the Vercel adapter. No changes are necessary, simply use configured redirects and the adapter will output the vercel.json file with the configuration values.

Patch Changes

3.4.1

Patch Changes

3.4.0

Minor Changes

Patch Changes

3.3.0

Minor Changes

Patch Changes

3.2.5

Patch Changes

3.2.4

Patch Changes

3.2.3

Patch Changes

3.2.2

Patch Changes

3.2.1

Patch Changes

3.2.0

Minor Changes

Patch Changes

3.1.4

Patch Changes

3.1.3

Patch Changes

3.1.2

Patch Changes

3.1.1

Patch Changes

3.1.0

Minor Changes

Patch Changes

3.0.1

Patch Changes

  • #6085 b236b5cc8 Thanks @AirBorne04! - Added second build step through esbuild, to allow framework defined build (vite build) and target defined bundling (esbuilt step)

  • Updated dependencies [9bec6bc41]:

    • astro@2.0.6

3.0.0

Major Changes

  • #5782 1f92d64ea Thanks @Princesseuh! - Remove support for Node 14. Minimum supported Node version is now >=16.12.0

  • #5707 5eba34fcc Thanks @bluwy! - Remove astro:build:start backwards compatibility code

  • #5806 7572f7402 Thanks @matthewp! - Make astro a peerDependency of integrations

    This marks astro as a peerDependency of several packages that are already getting major version bumps. This is so we can more properly track the dependency between them and what version of Astro they are being used with.

Patch Changes

3.0.0-beta.1

See changes in 3.0.0-beta.1

Major Changes

  • #5782 1f92d64ea Thanks @Princesseuh! - Remove support for Node 14. Minimum supported Node version is now >=16.12.0

  • #5806 7572f7402 Thanks @matthewp! - Make astro a peerDependency of integrations

    This marks astro as a peerDependency of several packages that are already getting major version bumps. This is so we can more properly track the dependency between them and what version of Astro they are being used with.

Patch Changes

3.0.0-beta.0

See changes in 3.0.0-beta.0

Major Changes

2.4.0

Minor Changes

2.3.6

Patch Changes

2.3.5

Patch Changes

2.3.4

Patch Changes

2.3.3

Patch Changes

2.3.2

Patch Changes

  • #5175 abf41da77 Thanks @JuanM04! - Edge adapter includes all the generated files (all files inside dist/) instead of only entry.mjs

2.3.1

Patch Changes

2.3.0

Minor Changes

2.2.0

Minor Changes

  • #5056 e55af8a23 Thanks @matthewp! - # New build configuration

    The ability to customize SSR build configuration more granularly is now available in Astro. You can now customize the output folder for server (the server code for SSR), client (your client-side JavaScript and assets), and serverEntry (the name of the entrypoint server module). Here are the defaults:

    import { defineConfig } from 'astro/config';

export default defineConfig({
  output: 'server',
  build: {
    server: './dist/server/',
    client: './dist/client/',
    serverEntry: 'entry.mjs',
  },
});

    These new configuration options are only supported in SSR mode and are ignored when building to SSG (a static site).

    Integration hook change

    The integration hook astro:build:start includes a param buildConfig which includes all of these same options. You can continue to use this param in Astro 1.x, but it is deprecated in favor of the new build.config options. All of the built-in adapters have been updated to the new format. If you have an integration that depends on this param we suggest upgrading to do this instead:

    export default function myIntegration() {
  return {
    name: 'my-integration',
    hooks: {
      'astro:config:setup': ({ updateConfig }) => {
        updateConfig({
          build: {
            server: '...',
          },
        });
      },
    },
  };
}

2.1.1

Patch Changes

2.1.0

Minor Changes

  • #4876 d3091f89e Thanks @matthewp! - Adds the Astro.cookies API

    Astro.cookies is a new API for manipulating cookies in Astro components and API routes.

    In Astro components, the new Astro.cookies object is a map-like object that allows you to get, set, delete, and check for a cookie's existence (has):

    ---
type Prefs = {
  darkMode: boolean;
};

Astro.cookies.set<Prefs>(
  'prefs',
  { darkMode: true },
  {
    expires: '1 month',
  },
);

const prefs = Astro.cookies.get<Prefs>('prefs').json();
---

<body data-theme={prefs.darkMode ? 'dark' : 'light'}></body>

    Once you've set a cookie with Astro.cookies it will automatically be included in the outgoing response.

    This API is also available with the same functionality in API routes:

    export function post({ cookies }) {
  cookies.set('loggedIn', false);

  return new Response(null, {
    status: 302,
    headers: {
      Location: '/login',
    },
  });
}

    See the RFC to learn more.

2.0.1

Patch Changes

2.0.0

Major Changes

1.0.2

Patch Changes

1.0.1

Patch Changes

1.0.0

Major Changes

Patch Changes

  • Updated dependencies [04ad44563]:
    • @astrojs/webapi@1.0.0

0.4.0

Minor Changes

0.3.0

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This 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 the adapter 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 add output: '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.clientAddress

    The 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.

0.2.6

Patch Changes

0.2.5

Patch Changes

0.2.4

Patch Changes

0.2.3

Patch Changes

0.2.2

Patch Changes

  • #3368 9d01f93b Thanks @JuanM04! - Remove nodeVersion option for serverless 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 a vercel.json file: just configure them inside your astro.config.mjs
    • Multiple deploy targets: edge, serverless and static!
    • When building to serverless, your code isn't transpiled to CJS anymore.

    Migrate from v0.1

    1. Change the import inside astro.config.mjs: 
      - import vercel from '@astrojs/vercel';
+ import vercel from '@astrojs/vercel/serverless';
    2. Rename the ENABLE_FILE_SYSTEM_API environment variable to ENABLE_VC_BUILD, as Vercel changed it.
    3. The output folder changed from .output to .vercel/output — you may need to update your .gitignore.

0.1.4

Patch Changes

0.1.3

Patch Changes

0.1.2

Patch Changes

0.1.1

Patch 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

0.0.2

Patch Changes