@astrojs/netlify

• 6.5.3

  Jul 23, 2025

  🐞 Patch Changes

  • #14120 798b5fa Thanks @ascorbic! - Adds mock feature flags in dev

  • Updated dependencies []:

    • @astrojs/underscore-redirects@1.0.0
• 6.5.2

  Jul 21, 2025

  🐞 Patch Changes

  • #14103 69d6871 Thanks @ascorbic! - Upgrades Netlify Vite plugin to fix error in edge functions.

  • Updated dependencies []:

    • @astrojs/underscore-redirects@1.0.0
• 6.5.1

  Jul 16, 2025

  🐞 Patch Changes

  • #14078 38c2255 Thanks @ascorbic! - Fixes a bug that caused remote images to sometimes not display correctly when using the Netlify Image CDN in local dev

  • #14078 38c2255 Thanks @ascorbic! - Adds a new devFeatures configuration option to control some of the behaviors introduced in @astrojs/netlify@6.5.0, which introduced Netlify production features into the dev environment.

    You can now individually configure whether or not to populate your environment with the variables from your linked Netlify site (now disabled by default), and use a local version of the Netlify Image CDN for images (still enabled by default) when running astro dev.

    Additionally, the adapter no longer injects environment variables from Netlify by default when running astro dev.

    @astrojs/netlify@6.5.0 introduced a potentially breaking change that enabled injecting Netlify environment variables in astro dev by default. This could lead to unexpected behavior in Astro projects that do not expect these variables to be present. This now defaults to disabled, and users can enable it by setting the devFeatures.environmentVariables option in their Astro config. Similarly, you can use devFeatures.images to disable using the Netlify Image CDN locally if needed:

    import { defineConfig } from 'astro/config';
    import netlify from '@astrojs/netlify';
    
    export default defineConfig({
      adapter: netlify({
        devFeatures: {
          environmentVariables: true,
          images: false,
        },
      }),
    });

    You can also set devFeatures to true or false to enable or disable all configurable dev features:

    import { defineConfig } from 'astro/config';
    import netlify from '@astrojs/netlify';
    export default defineConfig({
      adapter: netlify({
        devFeatures: true,
      }),
    });

  • Updated dependencies []:

    • @astrojs/underscore-redirects@1.0.0
• 6.5.0

  Jul 14, 2025

  🍿 Minor Changes

  • #13768 faa0eff Thanks @eduardoboucas! - Updates the adapter to use Netlify’s Vite plugin in development.

  This is an implementation update that does not require any change to your project code, but means that astro dev will run with an environment closer to a production deploy on Netlify. This brings several benefits you’ll now notice working in dev mode!

  For example, your project running in development mode will now use local versions of the Netlify Image CDN for images, and a local Blobs server for sessions. It will also populate your environment with the variables from your linked Netlify site.

  While not required for fully static, prerendered web sites, you may still wish to add this for the additional benefits of now working in a dev environment closer to your Netlify production deploy, as well as to take advantage of Netlify-exclusive features such as the Netlify Image CDN.

  🐞 Patch Changes

  • Updated dependencies []:
    • @astrojs/underscore-redirects@1.0.0
• 6.4.1

  Jul 3, 2025

  🐞 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.
  • Updated dependencies []:
    • @astrojs/underscore-redirects@1.0.0
• 6.4.0

  Jun 17, 2025

  🍿 Minor Changes

  • #13952 de82ef2 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 netlify from '@astrojs/netlify';
    
    export default defineConfig({
      adapter: netlify({
        experimentalStaticHeaders: true,
      }),
      experimental: {
        cps: true,
      },
    });

  🐞 Patch Changes

  • Updated dependencies [de82ef2, de82ef2, de82ef2]:
    • @astrojs/underscore-redirects@1.0.0
• 6.3.4

  May 21, 2025

  🐞 Patch Changes

  • #13799 7036b05 Thanks @Lofty-Brambles! - Fixes an issue where the adapter didn’t take into consideration the outDir configuration.

  • #13830 9371a67 Thanks @Lofty-Brambles! - Fixes an issue with SVGs not rendering with image-cdn enabled, due to invalid source path parsing.

  • Updated dependencies []:

    • @astrojs/underscore-redirects@0.6.1
• 6.3.3

  May 13, 2025

  🐞 Patch Changes

  • #13792 7910fea Thanks @alexeyzimarev! - Unify imported images detection across adapters

  • Updated dependencies []:

    • @astrojs/underscore-redirects@0.6.1
• 6.3.2

  Apr 30, 2025

  🐞 Patch Changes

  • #13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

  • Updated dependencies []:

    • @astrojs/underscore-redirects@0.6.1
• 6.3.1

  Apr 23, 2025

  🐞 Patch Changes

  • #13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

  • Updated dependencies [5dd2d3f]:

    • @astrojs/underscore-redirects@0.6.1
• 6.3.0

  Apr 15, 2025

  🍿 Minor Changes

  • #13527 2fd6a6b Thanks @ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.

    Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:

    ---
    export const prerender = false; // Not needed with 'server' output
    const cart = await Astro.session.get('cart');
    ---
    
    <a href="/checkout">🛒 {cart?.length ?? 0} items</a>

    Configuring session storage

    Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.

    If you are using an adapter that doesn’t have a default driver, or if you want to choose a different driver, you can configure it using the session configuration option:

    import { defineConfig } from 'astro/config';
    import vercel from '@astrojs/vercel';
    
    export default defineConfig({
      adapter: vercel(),
      session: {
        driver: 'upstash',
      },
    });

    Using sessions

    Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.

    In pages and components, you can access the session using Astro.session:

    ---
    const cart = await Astro.session.get('cart');
    ---
    
    <a href="/checkout">🛒 {cart?.length ?? 0} items</a>

    In endpoints, actions, and middleware, you can access the session using context.session:

    export async function GET(context) {
      const cart = await context.session.get('cart');
      return Response.json({ cart });
    }

    If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be undefined and an error will be logged in the console:

    ---
    export const prerender = true;
    const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined
    ---

    Upgrading from Experimental to Stable

    If you were previously using the experimental API, please remove the experimental.session flag from your configuration:

    import { defineConfig } from 'astro/config';
    import node from '@astrojs/node';
    
    export default defineConfig({
       adapter: node({
         mode: "standalone",
       }),
      experimental: {
        session: true,
      },
    });

    See the sessions guide for more information.

  🐞 Patch Changes

  • Updated dependencies []:
    • @astrojs/underscore-redirects@0.6.0
• 6.2.6

  Apr 14, 2025

  🐞 Patch Changes

  • #13596 3752519 Thanks @jsparkdev! - update vite to latest version to fix CVE

  • #13547 360cb91 Thanks @jsparkdev! - Updates vite to the latest version

  • Updated dependencies []:

    • @astrojs/underscore-redirects@0.6.0
• 6.2.5

  Mar 31, 2025

  🐞 Patch Changes

  • #13526 ff9d69e Thanks @jsparkdev! - update vite to the latest version

  • Updated dependencies []:

    • @astrojs/underscore-redirects@0.6.0
• 6.2.4

  Mar 26, 2025

  🐞 Patch Changes

  • #13505 a98ae5b Thanks @ematipico! - Updates the dependency vite to the latest.

  • Updated dependencies []:

    • @astrojs/underscore-redirects@0.6.0
• 6.2.3

  Mar 11, 2025

  🐞 Patch Changes

  • Updated dependencies [042d1de]:
    • @astrojs/internal-helpers@0.6.1
    • @astrojs/underscore-redirects@0.6.0
• 6.2.2

  Feb 27, 2025

  🐞 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
    • @astrojs/underscore-redirects@0.6.0
• 6.2.1

  Feb 24, 2025

  🐞 Patch Changes

  • #13299 2e1321e Thanks @bluwy! - Uses tinyglobby for globbing files

  • Updated dependencies []:

    • @astrojs/underscore-redirects@0.6.0
• 6.2.0

  Feb 13, 2025

  🍿 Minor Changes

  • #13194 1b5037b Thanks @dfdez! - Adds includedFiles and excludedFiles configuration options to customize SSR function bundle contents.

    The includeFiles property allows you to explicitly specify additional files that should be bundled with your function. This is useful for files that aren’t automatically detected as dependencies, such as:

    • Data files loaded using fs operations
    • Configuration files
    • Template files

    Similarly, you can use the excludeFiles property to prevent specific files from being bundled that would otherwise be included. This is helpful for:

    • Reducing bundle size
    • Excluding large binaries
    • Preventing unwanted files from being deployed

    import { defineConfig } from 'astro/config';
    import netlify from '@astrojs/netlify';
    
    export default defineConfig({
      // ...
      output: 'server',
      adapter: netlify({
        includeFiles: ['./my-data.json'],
        excludeFiles: ['./node_modules/package/**/*', './src/**/*.test.js'],
      }),
    });

    See the Netlify adapter documentation for detailed usage instructions and examples.

  • #13145 8d4e566 Thanks @ascorbic! - Automatically configures Netlify Blobs storage when experimental session enabled

    If the experimental.session flag is enabled when using the Netlify adapter, Astro will automatically configure the session storage using the Netlify Blobs driver. You can still manually configure the session storage if you need to use a different driver or want to customize the session storage configuration.

    See the experimental session docs for more information on configuring session storage.

  🐞 Patch Changes

  • Updated dependencies []:
    • @astrojs/underscore-redirects@0.6.0
• 3.0.2

  Sep 25, 2023

  🐞 Patch Changes

  • #8661 008f7647c Thanks @Skn0tt! - fix build failures because of CJS builds and top-level await

  • Updated dependencies [69fbf95b2]:

    • astro@3.1.4
    • @astrojs/underscore-redirects@0.3.0
• 3.0.1

  Sep 1, 2023

  🐞 Patch Changes

  • #8346 b74dacdb6 Thanks @delucis! - Update README

  • Updated dependencies [c5633434f, 405ad9501, 6b1e79814]:

    • astro@3.0.7
    • @astrojs/underscore-redirects@0.3.0