Changelog

• 5.13.7

  Sep 9, 2025

  🐞 Patch Changes

  • #14330 72e14ab Thanks @ascorbic! - Removes pinned package that is no longer needed.

  • #14335 17c7b03 Thanks @florian-lefebvre! - Bumps sharp minimal version to 0.34.0

• 5.13.6

  Sep 8, 2025

  🐞 Patch Changes

  • #14294 e005855 Thanks @martrapp! - Restores the ability to use Google Analytics History change trigger with the <ClientRouter />.

  • #14326 c24a8f4 Thanks @jsparkdev! - Updates vite version to fix CVE

  • #14108 218e070 Thanks @JusticeMatthew! - Updates dynamic route split regex to avoid infinite retries/exponential complexity

  • #14327 c1033be Thanks @ascorbic! - Pins simple-swizzle to avoid compromised version

• 5.13.5

  Aug 29, 2025

  🐞 Patch Changes

  • #14286 09c5db3 Thanks @ematipico! - BREAKING CHANGES only to the experimental CSP feature

    The following runtime APIs of the Astro global have been renamed:

    • Astro.insertDirective to Astro.csp.insertDirective
    • Astro.insertStyleResource to Astro.csp.insertStyleResource
    • Astro.insertStyleHash to Astro.csp.insertStyleHash
    • Astro.insertScriptResource to Astro.csp.insertScriptResource
    • Astro.insertScriptHash to Astro.csp.insertScriptHash

    The following runtime APIs of the APIContext have been renamed:

    • ctx.insertDirective to ctx.csp.insertDirective
    • ctx.insertStyleResource to ctx.csp.insertStyleResource
    • ctx.insertStyleHash to ctx.csp.insertStyleHash
    • ctx.insertScriptResource to ctx.csp.insertScriptResource
    • ctx.insertScriptHash to ctx.csp.insertScriptHash

  • #14283 3224637 Thanks @ematipico! - Fixes an issue where CSP headers were incorrectly injected in the development server.

  • #14275 3e2f20d Thanks @florian-lefebvre! - Adds support for experimental CSP when using experimental fonts

    Experimental fonts now integrate well with experimental CSP by injecting hashes for the styles it generates, as well as font-src directives.

    No action is required to benefit from it.

  • #14280 4b9fb73 Thanks @ascorbic! - Fixes a bug that caused cookies to not be correctly set when using middleware sequences

  • #14276 77281c4 Thanks @ArmandPhilippot! - Adds a missing export for resolveSrc, a documented image services utility.

• 5.13.4

  Aug 27, 2025

  🐞 Patch Changes

  • #14260 86a1e40 Thanks @jp-knj! - Fixes Astro.url.pathname to respect trailingSlash: 'never' configuration when using a base path. Previously, the root path with a base would incorrectly return /base/ instead of /base when trailingSlash was set to ‘never’.

  • #14248 e81c4bd Thanks @julesyoungberg! - Fixes a bug where actions named ‘apply’ do not work due to being a function prototype method.

• 5.13.3

  Aug 22, 2025

  🐞 Patch Changes

  • #14239 d7d93e1 Thanks @wtchnm! - Fixes a bug where the types for the live content collections were not being generated correctly in dev mode

  • #14221 eadc9dd Thanks @delucis! - Fixes JSON schema support for content collections using the file() loader

  • #14229 1a9107a Thanks @jonmichaeldarby! - Ensures Astro.currentLocale returns the correct locale during SSG for pages that use a locale param (such as [locale].astro or [locale]/index.astro, which produce [locale].html)

• 4.16.19

  Aug 19, 2025

  🐞 Patch Changes

  • #14241 760acc8 Thanks @ematipico! - Fixes an issue where remote paths weren’t correctly computed when generating assets
• 5.13.2

  Aug 15, 2025

  🐞 Patch Changes

  • 4d16de7 Thanks @ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

  • Updated dependencies [4d16de7]:

    • @astrojs/internal-helpers@0.7.2
    • @astrojs/markdown-remark@6.3.6
• 5.13.1

  Aug 15, 2025

  🐞 Patch Changes

  • #14225 f2490ab Thanks @delucis! - Fixes the experimental.chromeDevtoolsWorkspace feature.
• 5.13.0

  Aug 14, 2025
  

  🍿 Minor Changes

  • #14173 39911b8 Thanks @florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

    Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

    However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro’s default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

    The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite’s handling of environment variables and for better ease of use with Astro’s current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

    Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

    The experimental.staticImportMetaEnv flag simplifies Astro’s default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

    To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

    import { defineConfig } from "astro/config";
    
    export default defineConfig({
      experimental: {
        staticImportMetaEnv: true
        rawEnvValues: false
      }
    });

    Updating your project

    If you were relying on Astro’s default coercion, you may need to update your project code to apply it manually:

     const enabled: boolean = import.meta.env.ENABLED;
     const enabled: boolean = import.meta.env.ENABLED === "true";

    If you were relying on the transformation into process.env calls, you may need to update your project code to apply it manually:

     const enabled: boolean = import.meta.env.DB_PASSWORD;
     const enabled: boolean = process.env.DB_PASSWORD;

    You may also need to update types:

    interface ImportMetaEnv {
      readonly PUBLIC_POKEAPI: string;
      readonly DB_PASSWORD: string;
      readonly ENABLED: boolean;
      readonly ENABLED: string;
    }
    
    interface ImportMeta {
      readonly env: ImportMetaEnv;
    }
    
     namespace NodeJS {
      interface ProcessEnv {
        DB_PASSWORD: string;
      }
     }

    See the experimental static import.meta.env documentation for more information about this feature. You can learn more about using environment variables in Astro, including astro:env, in the environment variables documentation.

  • #14122 41ed3ac Thanks @ascorbic! - Adds experimental support for automatic Chrome DevTools workspace folders

    This feature allows you to edit files directly in the browser and have those changes reflected in your local file system via a connected workspace folder. This allows you to apply edits such as CSS tweaks without leaving your browser tab!

    With this feature enabled, the Astro dev server will automatically configure a Chrome DevTools workspace for your project. Your project will then appear as a workspace source, ready to connect. Then, changes that you make in the “Sources” panel are automatically saved to your project source code.

    To enable this feature, add the experimental flag chromeDevtoolsWorkspace to your Astro config:

    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
      experimental: {
        chromeDevtoolsWorkspace: true,
      },
    });

    See the experimental Chrome DevTools workspace feature documentation for more information.

• 5.12.9

  Aug 8, 2025

  🐞 Patch Changes

  • #14020 9518975 Thanks @jp-knj and @asieradzk! - Prevent double-prefixed redirect paths when using fallback and redirectToDefaultLocale together

    Fixes an issue where i18n fallback routes would generate double-prefixed paths (e.g., /es/es/test/item1/) when fallback and redirectToDefaultLocale configurations were used together. The fix adds proper checks to prevent double prefixing in route generation.

  • #14199 3e4cb8e Thanks @ascorbic! - Fixes a bug that prevented HMR from working with inline styles

• 5.12.8

  Aug 1, 2025

  🐞 Patch Changes

  • 0567fb7 Thanks @ascorbic! - Adds // to list of internal path prefixes that do not have automated trailing slash handling

  • #13894 b36e72f Thanks @florian-lefebvre! - Removes Astro Studio commands from the CLI help

  • Updated dependencies [0567fb7]:

    • @astrojs/internal-helpers@0.7.1
    • @astrojs/markdown-remark@6.3.5
• 5.12.7

  Jul 31, 2025

  🐞 Patch Changes

  • #14169 f4e8889 Thanks @ascorbic! - Skips trailing slash handling for paths that start with /..

  • #14170 34e6b3a Thanks @ematipico! - Fixes an issue where static redirects couldn’t correctly generate a redirect when the destination is a prerendered route, and the output is set to "server".

  • #14169 f4e8889 Thanks @ascorbic! - Fixes a bug that prevented images from being displayed in dev when using the Netlify adapter with trailingSlash set to always

  • Updated dependencies [f4e8889]:

    • @astrojs/internal-helpers@0.7.0
    • @astrojs/markdown-remark@6.3.4
• 5.12.6

  Jul 30, 2025

  🐞 Patch Changes

  • #14153 29e9283 Thanks @jp-knj! - Fixes a regression introduced by a recent optimisation of how SVG images are emitted during the build.

  • #14156 592f08d Thanks @TheOtterlord! - Fix the client router not submitting forms if the active URL contained a hash

  • #14160 d2e25c6 Thanks @ascorbic! - Fixes a bug that meant some remote image URLs could cause invalid filenames to be used for processed images

  • #14167 62bd071 Thanks @ascorbic! - Fixes a bug that prevented destroyed sessions from being deleted from storage unless the session had been loaded

• 5.12.5

  Jul 29, 2025

  🐞 Patch Changes

  • #14059 19f53eb Thanks @benosmac! - Fixes a bug in i18n implementation, where Astro didn’t emit the correct pages when fallback is enabled, and a locale uses a catch-all route, e.g. src/pages/es/[...catchAll].astro

  • #14155 31822c3 Thanks @ascorbic! - Fixes a bug that caused an error “serverEntrypointModule[_start] is not a function” in some adapters

• 5.12.4

  Jul 28, 2025

  🐞 Patch Changes

  • #14031 e9206c1 Thanks @jp-knj! - Optimized the build pipeline for SVG images. Now, Astro doesn’t reprocess images that have already been processed.

  • #14132 976879a Thanks @ematipico! - Fixes a bug where the property Astro.routePattern/context.routePattern wasn’t updated when using a rewrite via middleware.

  • #14131 aafc4d7 Thanks @florian-lefebvre! - Fixes a case where an error occurring in a middleware would show the dev overlay instead of the custom 500.astro page

  • #14127 2309ada Thanks @florian-lefebvre! - Upgrades zod

  • #14134 186c201 Thanks @ascorbic! - Throws a more helpful error in dev if trying to use a server island without an adapter

  • #14129 3572d85 Thanks @ematipico! - Fixes a bug where the CSP headers was incorrectly added to a page when using an adapter.

• 5.12.3

  Jul 23, 2025

  🐞 Patch Changes

  • #14119 14807a4 Thanks @ascorbic! - Fixes a bug that caused builds to fail if a client directive was mistakenly added to an Astro component

  • #14001 4b03d9c Thanks @dnek! - Fixes an issue where getImage() assigned the resized base URL to the srcset URL of ImageTransform, which matched the width, height, and format of the original image.

• 5.12.2

  Jul 22, 2025

  🐞 Patch Changes

  • #14071 d2cb35d Thanks @Grisoly! - Exposes the Code component lang prop type:

    import type { CodeLanguage } from 'astro';

  • #14111 5452ee6 Thanks @ascorbic! - Fixes a bug that prevented “key” from being used as a prop for Astro components in MDX

  • #14106 b5b39e4 Thanks @ascorbic! - Exits with non-zero exit code when config has an error

  • #14112 37458b3 Thanks @ascorbic! - Fixes a bug that meant that SVG components could no longer be serialized with JSON.stringify

  • #14061 c7a7dd5 Thanks @jonasgeiler! - Add module declaration for ?no-inline asset imports

  • #14109 5a08fa2 Thanks @ascorbic! - Throw a more helpful error if defineLiveCollection is used outside of a live.config file

  • #14110 e7dd4e1 Thanks @ascorbic! - Warn if duplicate IDs are found by file loader

• 5.12.1

  Jul 21, 2025

  🐞 Patch Changes

  • #14094 22e9087 Thanks @ascorbic! - Correct types to allow priority on all images

  • #14091 26c6b6d Thanks @ascorbic! - Fixes a bug that caused a type error when defining session options without a driver

  • #14082 93322cb Thanks @louisescher! - Fixes an issue where Astro’s default 404 route would incorrectly match routes containing “/404” in dev

  • #14089 687d253 Thanks @florian-lefebvre! - Fixes a case where astro:env would not load the right environments variables in dev

  • #14092 6692c71 Thanks @ascorbic! - Improves error handling in live collections

  • #14074 144a950 Thanks @abcfy2! - Fixes a bug that caused some image service builds to fail

  • #14092 6692c71 Thanks @ascorbic! - Fixes a case where zod could not be imported from astro:content virtual module in live collection config

• 5.12.0

  Jul 17, 2025
  

  🍿 Minor Changes

  • #13971 fe35ee2 Thanks @adamhl8! - Adds an experimental flag rawEnvValues to disable coercion of import.meta.env values (e.g. converting strings to other data types) that are populated from process.env

    Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type.

    However, Astro also converts your environment variables used through import.meta.env in some cases, and this can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

    The experimental.rawEnvValues flag disables coercion of import.meta.env values that are populated from process.env, allowing you to use the raw value.

    To enable this feature, add the experimental flag in your Astro config:

    import { defineConfig } from "astro/config"
    
    export default defineConfig({
      experimental: {
        rawEnvValues: true,
      }
    })

    If you were relying on this coercion, you may need to update your project code to apply it manually:

    - const enabled: boolean = import.meta.env.ENABLED
    + const enabled: boolean = import.meta.env.ENABLED === "true"

    See the experimental raw environment variables reference docs for more information.

  • #13941 6bd5f75 Thanks @aditsachde! - Adds support for TOML files to Astro’s built-in glob() and file() content loaders.

    In Astro 5.2, Astro added support for using TOML frontmatter in Markdown files instead of YAML. However, if you wanted to use TOML files as local content collection entries themselves, you needed to write your own loader.

    Astro 5.12 now directly supports loading data from TOML files in content collections in both the glob() and the file() loaders.

    If you had added your own TOML content parser for the file() loader, you can now remove it as this functionality is now included:

    import { defineCollection } from "astro:content";
    import { file } from "astro/loaders";
     import { parse as parseToml } from "toml";
    const dogs = defineCollection({
      loader: file("src/data/dogs.toml", { parser: (text) => parseToml(text) }),
     loader: file("src/data/dogs.toml")
      schema: /* ... */
    })

    Note that TOML does not support top-level arrays. Instead, the file() loader considers each top-level table to be an independent entry. The table header is populated in the id field of the entry object.

    See Astro’s content collections guide for more information on using the built-in content loaders.

  🐞 Patch Changes

  • Updated dependencies [6bd5f75]:
    • @astrojs/markdown-remark@6.3.3
• 5.11.2

  Jul 16, 2025

  🐞 Patch Changes

  • #14064 2eb77d8 Thanks @jp-knj! - Allows using tsconfig compilerOptions.paths without setting compilerOptions.baseUrl

  • #14068 10189c0 Thanks @jsparkdev! - Fixes the incorrect CSS import path shown in the terminal message during Tailwind integration setup.