[email protected]

Patch Changes

• #12956 3aff68a Thanks @kaytwo! - Removes encryption of empty props to allow server island cacheability

• #12977 80067c0 Thanks @florian-lefebvre! - Fixes a case where accessing astro:env APIs or import.meta.env inside the content config file would not work

• #12839 57be349 Thanks @mtwilliams-code! - Fix Astro.currentLocale returning the incorrect locale when using fallback rewrites in SSR mode

• #12962 4b7a2ce Thanks @ascorbic! - Skips updating content layer files if content is unchanged

• #12942 f00c2dd Thanks @liruifengv! - Improves the session error messages

• #12966 d864e09 Thanks @ascorbic! - Ensures old content collection entry is deleted if a markdown frontmatter slug is changed in dev

@astrojs/[email protected]

Patch Changes

• #12739 1f9571b Thanks @gnify! - Updates displayed data to show both source and target versions

@astrojs/[email protected]

Patch Changes

• #12923 c7642fb Thanks @bluwy! - Adds the client entrypoint to optimizeDeps.include

@astrojs/[email protected]

Patch Changes

• #12923 c7642fb Thanks @bluwy! - Removes react-specific entrypoints in optimizeDeps.include and rely on @vitejs/plugin-react to add

[email protected]

Patch Changes

• #12934 673a518 Thanks @ematipico! - Fixes a regression where the Astro Container didn't work during the build, using pnpm

• #12955 db447f2 Thanks @martrapp! - Lets TypeScript know about the "blocking" and "disabled" attributes of the <link> element.

• #12922 faf74af Thanks @adamchal! - Improves performance of static asset generation by fixing a bug that caused image transforms to be performed serially. This fix ensures that processing uses all CPUs when running in a multi-core environment.

• #12947 3c2292f Thanks @ascorbic! - Fixes a bug that caused empty content collections when running dev with NODE_ENV set

@astrojs/[email protected]

Patch Changes

• #12948 51ab7b5 Thanks @bluwy! - Supports checking for React 19 components

@astrojs/[email protected]

Patch Changes

• #12959 3a267f3 Thanks @bluwy! - Reverts 9a3b48c which caused a regression for rendering inline MDX components and MDX files from content collections

@astrojs/[email protected]

Patch Changes

• #12930 a20a4d7 Thanks @bluwy! - Fixes rendering code blocks within if tags

[email protected]

Patch Changes

• #12927 ad2a752 Thanks @ematipico! - Fixes a bug where Astro attempted to decode a request URL multiple times, resulting in an unexpected behaviour when decoding the character %

• #12912 0c0c66b Thanks @florian-lefebvre! - Improves the config error for invalid combinations of context and access properties under env.schema

• #12935 3d47e6b Thanks @AirBorne04! - Fixes an issue where Astro.locals coming from an adapter weren't available in the 404.astro, when using the astro dev command,

• #12925 44841fc Thanks @ascorbic! - Ensures image styles are not imported unless experimental responsive images are enabled

• #12926 8e64bb7 Thanks @oliverlynch! - Improves remote image cache efficiency by separating image data and metadata into a binary and sidecar JSON file.

• #12920 8b9d530 Thanks @bluwy! - Processes markdown with empty body as remark and rehype plugins may add additional content or frontmatter

• #12918 fd12a26 Thanks @lameuler! - Fixes a bug where the logged output path does not match the actual output path when using build.format: 'preserve'

• #12676 2ffc0fc Thanks @koyopro! - Allows configuring Astro modules TypeScript compilation with the vite.esbuild config

• #12938 dbb04f3 Thanks @ascorbic! - Fixes a bug where content collections would sometimes appear empty when first running astro dev

• #12937 30edb6d Thanks @ematipico! - Fixes a bug where users could use Astro.request.headers during a rewrite inside prerendered routes. This an invalid behaviour, and now Astro will show a warning if this happens.

• #12937 30edb6d Thanks @ematipico! - Fixes an issue where the use of Astro.rewrite would trigger the invalid use of Astro.request.headers

@astrojs/[email protected]

Minor Changes

• #12924 3caa337 Thanks @florian-lefebvre! - Updates how the output is determined in createRedirectsFromAstroRoutes. Since v0.5.0, the output would use the buildOutput property and config.output as a fallback. It no longer uses this fallback.

• #12924 3caa337 Thanks @florian-lefebvre! - Updates the input requirements of createRedirectsFromAstroRoutes:

  • routeToDynamicTargetMap keys are IntegrationResolvedRoute instead of IntegrationRouteData (obtained from the astro:routes:resolved hook)
  • There's a new assets property, that can be obtained from the astro:build:done hook

  function myIntegration() {
    let routes;
    let buildOutput;
    let config;
  
    return {
      name: 'my-integration',
      hooks: {
        'astro:routes:resolved': (params) => {
          routes = params.routes;
        },
        'astro:config:done': (params) => {
          buildOutput = params.buildOutput;
          config = params.config;
        },
        'astro:build:done': (params) => {
          const redirects = createRedirectsFromAstroRoutes({
            config,
            buildOutput,
            routeToDynamicTargetMap: new Map(routes.map((route) => [route, ''])),
            dir: params.dir,
            assets: params.assets,
          });
        },
      },
    };
  }