Description

Update the Catppuccin theme href to https://starlight.catppuccin.com/

Changes

• The google config was not passed to the unifont provider (reported on Discord)

Testing

N/A

Docs

Changeset, withastro/docs#11484

Description

This PR is a bit of a blast from the past, as it fixes an issue I initially spotted in Astro Docs almost a year ago when copying headings with either double click (select a word) or triple click (select a paragraph/logical unit) with a different behavior between browsers.

Chrome

Double clicking and copying a heading with a single word or the last word of a multiple words heading will inject Section in the clipboard text.

For example, going to this page and double clicking and copying the heading Usage will copy UsageSection instead of Usage. Double clicking and copying the word icons in the heading Customize icons will copy iconsSection instead of icons.

Triple clicking is working as expected.

Firefox

Triple clicking a heading and copying will inject the entire heading anchor link screen reader text in the clipboard text.

For example, going to this page and triple clicking and copying the heading Customize icons will copy Customize iconsSection titled “Customize icons” instead of Customize icons.

Safari

Double clicking and copying a heading with a single word or the last word of a multiple words heading will inject Section in the clipboard text.

For example, going to this page and double clicking and copying the heading Usage will copy UsageSection instead of Usage. Double clicking and copying the word icons in the heading Customize icons will copy iconsSection instead of icons.

Triple clicking is working as expected.

Changes

The good thing is that I also fixed the issue in withastro/docs#8015 at the time. This PR uses the same approach to fix the issue in Starlight. The original PR contains a breakdown of various approaches I tried and why I used the one I did so I'm not going to repeat it here.

Changes

When running the latest version of create-astro with pnpm, I'm getting the following error:

▲  error Error
▲  error Dependencies failed to install, please run pnpm install to install them manually after setup.
✔  Project initialized!
■ Template copied
■ Dependencies installed

After adding some logging, the underlying issue seems to be:

ERR_PNPM_MISSING_PACKAGE_NAME  `pnpm add` requires the package name

In #13395, the install() function was updated to use pnpm add instead of pnpm install without a changeset so it ended up being released 2 days ago with version 4.11.2. This PR reverts that change.

The install() function seems to only be meant to install all dependencies (and never a single package) so I'm not sure if there is a reason I'm potentially missing for the change or not.

Testing

I tested locally using node create-astro.mjs but I don't know how to force a specific package manager with this method so I temporarily hardcoded pnpm. Without the fix, I properly reproduced the error. After the fix, the issue seems to be resolved.

Looks like most of the tests for create-astro are using dryRun: true so not sure if/how we should add a test for this.

Docs

This is a bug fix that does not require any documentation change.

Changes

• Add SvgComponent type as per discussion here.

Testing

No tests needed, I think?

Docs

Docs will need to mention that the SvgComponent component is available for use, similar to the mentions of other types like ImageMetadata.

/cc @withastro/maintainers-docs for feedback!

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.7.4

Patch Changes

• #13647 ffbe8f2 Thanks @ascorbic! - Fixes a bug that caused a session error to be logged when using actions without sessions

• #13646 6744842 Thanks @florian-lefebvre! - Fixes a case where extra font sources were removed when using the experimental fonts API

• #13635 d75cac4 Thanks @florian-lefebvre! - The experimental fonts API now generates optimized fallbacks for every weight and style

Changes

Currently the action API context is created by destructuring the unused properties of the context object. This was causing warnings to be logged because it copies by value, meaning the session get method was being called.

This PR switches to using Object.create and getOwnPropertyDescriptors, which preserves the accessors on the object, menaing the session getter isn't called unless the user accesses it.

Fixes #13644

Testing

Tested with the repro for #13644

Docs

Changes

• In #13594 in order to avoid too many preloads, I filtered the font sources so there are less
• However, this was not the right fix. Instead we want to preserve all sources but only add the first one to be preloaded

Testing

Manual

Docs

Changeset

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight-tailwind@4.0.1

Patch Changes

• #3132 5959919 Thanks @HiDeoo! - Fixes an issue where all border styles were not reset by the Starlight’s Tailwind compatibility package like in Tailwind base styles.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.7.3

Patch Changes

• #13643 67b7493 Thanks @tanishqmanuja! - Fixes a case where the font face src format would be invalid when using the experimental fonts API

• #13639 23410c6 Thanks @florian-lefebvre! - Fixes a case where some font families would not be downloaded when using the same font provider several times, using the experimental fonts API

Changes

Fixes issue: #13642

Testing

Docs

Description

Fixes a small mistake in the new content in pages.mdx

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

create-astro@4.11.2

Patch Changes

• #13636 a9fd03f Thanks @sarah11918! - Updates the wording for choosing the "minimal" starter template options

Changes

• Closes #13637
• Unifont deduplicates providers based on the provider name. However in our case the same provider can be called with a different config (eg. adobe), so we have some logic to hash the config and dedupe
• However, the logic AND the tests were wrong because in certain cases, the family provider name was not assigned a value and as such, the family could not be resolved by unifont

Testing

Tests updated + manual

Docs

Changeset

Changes

A trivial text change so I can add the proper changeset this time 😅

(Follow up to #13603 which added the minimal template, but didn't trigger an update to the create-astro package)

Testing

No tests.

Docs

When this is released, I can improve instructions to the tutorial in docs

Description

The Starlight Tailwind compatibility package restores only some crucial styles from Tailwind Preflight instead of using it entirely.

This previous version of the Tailwind compatibility package used to restore a rule resetting all border styles to allow adding a border to an element by just adding a border-width.

The new version is no longer restoring this rule (which still exists in Tailwind v4) which could cause updating users to have default borders on their buttons. This PR adds it back to the compatibility package.

For example, this issue was initially reported while updating the Cloudflare Docs, here is how it looks with Tailwind v4 without the fix and with the fix:

Before	After

Changes

• RFC feedback
• Before this PR, we were generating 1 fallback @font-face definition based on the first font file we found for a given family
• However, it wasn't great because the fallback would only be accurate for a given weight/style which was defeating its purpose
• Now we generate a fallback for each weight/style
• Fixes a few cases where useless duplicate fallbacks could be created

Testing

Tests updated, tested manually

Docs

Changeset

Changes

Closes #13633

A check was modified, but it turns out that it was required, in fact the tests introduced in #13598 still pass

Testing

Added a new test case

Docs

N/A

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight-tailwind@4.0.0

Major Changes

• #2322 f14eb0c Thanks @HiDeoo! - ⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.34.0

  Please use the @astrojs/upgrade command to upgrade your project:

  npx @astrojs/upgrade

• #2322 f14eb0c Thanks @HiDeoo! - Adds support for Tailwind v4, drops support for Tailwind v3.

  ⚠️ BREAKING CHANGE: Tailwind v3 is no longer supported. Tailwind v4 support in Astro is now provided using a Vite plugin and the Astro Tailwind integration is no longer required.

  1. Remove the Astro Tailwind integration. The Astro Tailwind integration is no longer required with Tailwind v4.

      // astro.config.mjs
      import { defineConfig } from "astro/config";
      import starlight from "@astrojs/starlight";
     -import tailwind from "@astrojs/tailwind";
     
      export default defineConfig({
        integrations: [
          starlight({
            title: "Docs with Tailwind",
            customCss: ["./src/tailwind.css"],
          }),
     -    tailwind({ applyBaseStyles: false }),
        ],
      });

  2. Install Tailwind v4. Install the latest version of the tailwindcss and @tailwindcss/vite packages.

     Use the astro add tailwind command to install and configure both packages:

     npx astro add tailwind

  3. Update Tailwind base styles. Tailwind CSS base styles needs to be updated for Tailwind v4 and also to use Starlight Tailwind CSS.

     /* src/tailwind.css */
     -@tailwind base;
     -@tailwind components;
     -@tailwind utilities;
     +@layer base, starlight, theme, components, utilities;
     +
     +@import '@astrojs/starlight-tailwind';
     +@import 'tailwindcss/theme.css' layer(theme);
     +@import 'tailwindcss/utilities.css' layer(utilities);
     +
     +@theme {
     +	/*
     +	Configure your Tailwind theme that will be used by Starlight.
     +	https://starlight.astro.build/guides/css-and-tailwind/#styling-starlight-with-tailwind
     +	*/
     +}
     +
     +/*
     +Add additional Tailwind styles to this file:
     +https://tailwindcss.com/docs/adding-custom-styles#using-custom-css
     +*/

  4. Update Tailwind customizations. If you previously customized your Tailwind theme configuration in the tailwind.config.mjs file, such customizations are now defined through CSS using the @theme block in your Tailwind base styles.

     1. Locate existing customizations in your tailwind.config.mjs file. The following example defines customizations for the accent colors, gray scale, and font families used by Starlight:

        // tailwind.config.mjs
        import starlightPlugin from '@astrojs/starlight-tailwind';
        import colors from 'tailwindcss/colors';
        
        /** @type {import('tailwindcss').Config} */
        export default {
          content: ['./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}'],
          theme: {
            extend: {
              colors: {
                // Custom accent colors.
                accent: colors.fuchsia,
                // Custom gray scale.
                gray: colors.slate,
              },
              fontFamily: {
                // Custom text font.
                sans: ['"Atkinson Hyperlegible"'],
                // Custom code font.
                mono: ['"IBM Plex Mono"'],
              },
            },
          },
          plugins: [starlightPlugin()],
        };

     2. The above customizations can be migrated to the new @theme block in the file containing your Tailwind base styles as follows:

        /* src/tailwind.css */
        @layer base, starlight, theme, components, utilities;
        
        @import '@astrojs/starlight-tailwind';
        @import 'tailwindcss/theme.css' layer(theme);
        @import 'tailwindcss/utilities.css' layer(utilities);
        
        @theme {
          /* Custom accent colors. */
          --color-accent-50: var(--color-fuchsia-50);
          --color-accent-100: var(--color-fuchsia-100);
          --color-accent-200: var(--color-fuchsia-200);
          --color-accent-300: var(--color-fuchsia-300);
          --color-accent-400: var(--color-fuchsia-400);
          --color-accent-500: var(--color-fuchsia-500);
          --color-accent-600: var(--color-fuchsia-600);
          --color-accent-700: var(--color-fuchsia-700);
          --color-accent-800: var(--color-fuchsia-800);
          --color-accent-900: var(--color-fuchsia-900);
          --color-accent-950: var(--color-fuchsia-950);
          /* Custom gray scale. */
          --color-gray-50: var(--color-slate-50);
          --color-gray-100: var(--color-slate-100);
          --color-gray-200: var(--color-slate-200);
          --color-gray-300: var(--color-slate-300);
          --color-gray-400: var(--color-slate-400);
          --color-gray-500: var(--color-slate-500);
          --color-gray-600: var(--color-slate-600);
          --color-gray-700: var(--color-slate-700);
          --color-gray-800: var(--color-slate-800);
          --color-gray-900: var(--color-slate-900);
          --color-gray-950: var(--color-slate-950);
          /* Custom text font. */
          --font-sans: 'Atkinson Hyperlegible';
          /* Custom code font. */
          --font-mono: 'IBM Plex Mono';
        }

  We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.

  For full details about upgrading from Tailwind v3 to v4, see the official upgrade guide.

@astrojs/starlight-markdoc@0.4.0

Minor Changes

• #3033 8c19678 Thanks @delucis! - Adds support for generating clickable anchor links for headings.

  By default, the Starlight Markdoc preset now includes a default heading node, which renders an anchor link beside headings in your Markdoc content.

  If you want to disable this new feature, pass headingLinks: false in your Markdoc config:

  export default defineMarkdocConfig({
    // Disable the default heading anchor link support
    extends: [starlightMarkdoc({ headingLinks: false })],
  });

  ⚠️ BREAKING CHANGE: The minimum supported peer version of Starlight is now v0.34.0.

  Please update Starlight and the Starlight Markdoc preset together:

  npx @astrojs/upgrade

@astrojs/starlight@0.34.0

Minor Changes

• #2322 f14eb0c Thanks @HiDeoo! - Groups all of Starlight's CSS declarations into a single starlight cascade layer.

  This change allows for easier customization of Starlight's CSS as any custom unlayered CSS will override the default styles. If you are using cascade layers in your custom CSS, you can use the @layer CSS at-rule to define the order of precedence for different layers including the ones used by Starlight.

  We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.

• #3122 3a087d8 Thanks @delucis! - Removes default attrs and content values from head entries parsed using Starlight’s schema.

  Previously when adding head metadata via frontmatter or user config, Starlight would automatically add values for attrs and content if not provided. Now, these properties are left undefined.

  This makes it simpler to add tags in route middleware for example as you no longer need to provide empty values for attrs and content:

  head.push({
    tag: 'style',
    content: 'div { color: red }'
  - attrs: {},
  });
  head.push({
    tag: 'link',
  - content: ''
    attrs: { rel: 'me', href: 'https://example.com' },
  });

  This is mostly an internal API but if you are overriding Starlight’s Head component or processing head entries in some way, you may wish to double check your handling of Astro.locals.starlightRoute.head is compatible with attrs and content potentially being undefined.

• #3033 8c19678 Thanks @delucis! - Adds support for generating clickable anchor links for headings.

  By default, Starlight now renders an anchor link beside headings in Markdown and MDX content. A new <AnchorHeading> component is available to achieve the same thing in custom pages built using <StarlightPage>.

  If you want to disable this new Markdown processing set the markdown.headingLinks option in your Starlight config to false:

  starlight({
    title: 'My docs',
    markdown: {
      headingLinks: false,
    },
  }),

  ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now v5.5.0.

  Please update Starlight and Astro together:

  npx @astrojs/upgrade

• #2322 f14eb0c Thanks @HiDeoo! - Removes Shiki css-variables theme fallback.

  ⚠️ Breaking change:

  Previously, Starlight used to automatically provide a fallback theme for Shiki, the default syntax highlighter built into Astro if the configured Shiki theme was not github-dark.

  This fallback was only relevant when the default Starlight code block renderer, Expressive Code, was disabled and Shiki was used. Starlight no longer provides this fallback.

  If you were relying on this behavior, you now manually need to update your Astro configuration to use the Shiki css-variables theme to match the previous behavior.

  import { defineConfig } from 'astro/config';
  
  export default defineConfig({
  + markdown: {
  +   shikiConfig: {
  +     theme: 'css-variables',
  +   },
  + },
  });

  Additionally, you can use custom CSS to control the appearance of the code blocks. Here are the previously used CSS variables for the fallback theme:

  :root {
    --astro-code-foreground: var(--sl-color-white);
    --astro-code-background: var(--sl-color-gray-6);
    --astro-code-token-constant: var(--sl-color-blue-high);
    --astro-code-token-string: var(--sl-color-green-high);
    --astro-code-token-comment: var(--sl-color-gray-2);
    --astro-code-token-keyword: var(--sl-color-purple-high);
    --astro-code-token-parameter: var(--sl-color-red-high);
    --astro-code-token-function: var(--sl-color-red-high);
    --astro-code-token-string-expression: var(--sl-color-green-high);
    --astro-code-token-punctuation: var(--sl-color-gray-2);
    --astro-code-token-link: var(--sl-color-blue-high);
  }

Patch Changes

• #3118 77a1104 Thanks @delucis! - Fixes passing imported SVGs to the frontmatter prop of the <StarlightPage> component in Astro ≥5.7.0

Changes

• Improves the generated fallback name. It now takes names with quotes into account by removing the quotes to avoid creating invalid strings
• Refactors font face declaration generation so the logic is shared
• Improves the quality of fallbacks by pulling system metrics (RFC feedback):
  • I didn't notice that initially but to get better fallbacks, you need to provide the metrics of the target font file (done by reading the font file) as well as the metrics of the fallback font (system font eg. Arial)
  • So now, the metrics of system fonts used as fallbacks are put in a constant to avoid having to add the @capsizecss/metrics package (which is huge and was removed in #13626)
• Makes changes to implementation copied from nuxt/fonts and capsize to simplify things

Testing

Tests added

Docs

Changesets

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.7.2

Patch Changes

• #13632 cb05cfb Thanks @florian-lefebvre! - Improves the optimized fallback name generated by the experimental Fonts API

• #13630 3e7db4f Thanks @florian-lefebvre! - Fixes a case where fonts using a local provider would not work because of an invalid generated src

• #13634 516de7d Thanks @ematipico! - Fixes a regression where using next('/') didn't correctly return the requested route.

• #13632 cb05cfb Thanks @florian-lefebvre! - Improves the quality of optimized fallbacks generated by the experimental Fonts API

• #13616 d475afc Thanks @lfilho! - Fixes a regression where relative static redirects didn't work as expected.

Description

• Removes default values for attrs and content from the schema used to parse head entries (previously these were {} and "" respectively).
• This makes it simpler to add new entries directly to the parsed head array without types saying you must set these default values.
• Made this a minor as it could technically be breaking for users or plugins who are overriding or processing head in some way, although for the average site this should be basically an internal API change.
• No docs change needed as we already document head by linking to HeadConfig, which shows these properties as optional.

Changes

• Closes #13624

Testing

Added

Docs

Changeset

Changes

Upgraded drizzle-orm to latest v0.42.0

Testing

Docs

Changeset

Description

• Closes #3114
• Changes how we mock Astro’s image() schema function to account for the new SVG import shape which is stable in Astro 5.7.0

Changes

• Exposes virtual module on the client

Testing

Using the preview release

Docs

Changeset

Changes

• RFC feedback
• Removes @capsizecss/metrics because it's heavy. Instead, we read the font files directly
• Simplifies the cache util

Testing

Should pass

Docs

Changeset

Changes

• According to capo, preload link should come before style tags
• Updated after feedback on the RFC

Testing

N/A

Docs

Changeset

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.7.1

Patch Changes

• #13594 dc4a015 Thanks @florian-lefebvre! - Reduces the number of font files downloaded

• #13627 7f1a624 Thanks @florian-lefebvre! - Fixes a case where using the <Font /> component would throw a Rollup error during the build

• #13626 3838efe Thanks @florian-lefebvre! - Updates fallback font generation to always read font files returned by font providers

• #13625 f1311d2 Thanks @florian-lefebvre! - Updates the <Font /> component so that preload links are generated before the style tag if preload is passed

• #13622 a70d32a Thanks @ascorbic! - Improve autocomplete for session keys

Changes

Use the | (string & {}) trick to ensure that key autocomplete always works

Testing

Docs

Changes

• Fixed mistake in changelog

Changes

The 5.7.0 changelog includes <h2> headings in the sessions details which is inconsistent with other headings in the changelog and is breaking some automated tooling that attempts to display a version’s notes (see e.g. this Renovate PR: withastro/astro.build#1529)

Testing

n/a

Docs

n/a

Changes

As per #13607, redirects had a regression with relative redirects introduced in #12979. This PR fixes it.

Fixes #13607

Testing

• Unit tests
• Tested with my local side project using the new changes

Docs

/cc @withastro/maintainers-docs for feedback! This was never documented but always worked since early versions of Astro so as mentioned by @ematipico on #13607 we should probaly update the docs. Happy to have a stab at it if you want too.

{ minHeadingLevel: 2; maxHeadingLevel: 3; } was throwing an error.

Changed it to { minHeadingLevel: 2, maxHeadingLevel: 3 } and it worked fine.

Description

• Closes #
• What does this PR change? Give us a brief description.
• Did you change something visual? A before/after screenshot can be helpful.

Changes

This adds the @message property (and message to the ErrorData object) for one of the new error messages. @florian-lefebvre or someone please correct/verify the actual content!

Testing

Not tested, but the @message property is the one that generates the error message block in docs. Without it, we only get a "What went wrong?" section. (This might also affect the error message people see?)

e.g. without: (we had one slip by earlier!)

vs most other error messages:

Docs

All for docs!

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.7.0

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.

• #12775 b1fe521 Thanks @florian-lefebvre! - Adds a new, experimental Fonts API to provide first-party support for fonts in Astro.

  This experimental feature allows you to use fonts from both your file system and several built-in supported providers (e.g. Google, Fontsource, Bunny) through a unified API. Keep your site performant thanks to sensible defaults and automatic optimizations including fallback font generation.

  To enable this feature, configure an experimental.fonts object with one or more fonts:

  import { defineConfig, fontProviders } from "astro/config"
  
  export default defineConfig({
      experimental: {
          fonts: [{
              provider: fontProviders.google(),
        `      name: "Roboto",
              cssVariable: "--font-roboto",
          }]
      }
  })

  Then, add a <Font /> component and site-wide styling in your <head>:

  ---
  import { Font } from 'astro:assets';
  ---
  
  <Font cssVariable="--font-roboto" preload />
  <style>
    body {
      font-family: var(--font-roboto);
    }
  </style>

  Visit the experimental Fonts documentation for the full API, how to get started, and even how to build your own custom AstroFontProvider if we don't yet support your preferred font service.

  For a complete overview, and to give feedback on this experimental API, see the Fonts RFC and help shape its future.

• #13560 df3fd54 Thanks @ematipico! - The virtual module astro:config introduced behind a flag in v5.2.0 is no longer experimental and is available for general use.

  This virtual module exposes two sub-paths for type-safe, controlled access to your configuration:

  • astro:config/client: exposes config information that is safe to expose to the client.
  • astro:config/server: exposes additional information that is safe to expose to the server, such as file and directory paths.

  Access these in any file inside your project to import and use select values from your Astro config:

  // src/utils.js
  import { trailingSlash } from 'astro:config/client';
  
  function addForwardSlash(path) {
    if (trailingSlash === 'always') {
      return path.endsWith('/') ? path : path + '/';
    } else {
      return path;
    }
  }

  If you were previously using this feature, please remove the experimental flag from your Astro config:

  // astro.config.mjs
  export default defineConfig({
  -  experimental: {
  -    serializeConfig: true
  -  }
  })

  If you have been waiting for feature stabilization before using configuration imports, you can now do so.

  Please see the astro:config reference for more about this feature.

• #13578 406501a Thanks @stramel! - The SVG import feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.

  This feature allows you to import SVG files directly into your Astro project as components and inline them into your HTML.

  To use this feature, import an SVG file in your Astro project, passing any common SVG attributes to the imported component.

  ---
  import Logo from './path/to/svg/file.svg';
  ---
  
  <Logo <Logo width={64} height={64} fill="currentColor" />

  If you have been waiting for stabilization before using the SVG Components feature, you can now do so.

  If you were previously using this feature, please remove the experimental flag from your Astro config:

  import { defineConfig } from 'astro'
  
  export default defineConfig({
  -  experimental: {
  -    svg: true,
  -  }
  })

  Additionally, a few features that were available during the experimental stage were removed in a previous release. Please see the v5.6.0 changelog for details if you have not yet already updated your project code for the experimental feature accordingly.

  Please see the SVG Components guide in docs for more about this feature.

Patch Changes

• #13602 3213450 Thanks @natemoo-re! - Updates the Audit dev toolbar app to automatically strip data-astro-source-file and data-astro-source-loc attributes in dev mode.

• #13598 f5de51e Thanks @dreyfus92! - Fix routing with base paths when trailingSlash is set to 'never'. This ensures requests to '/base' are correctly matched when the base path is set to '/base', without requiring a trailing slash.

• #13603 d038030 Thanks @sarah11918! - Adds the minimal starter template to the list of create astro options

  Good news if you're taking the introductory tutorial in docs, making a minimal reproduction, or just want to start a project with as little to rip out as possible. Astro's minimal (empty) template is now back as one of the options when running create astro@latest and starting a new project!

@astrojs/cloudflare@12.5.0

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

@astrojs/markdoc@0.14.0

Minor Changes

• #13578 406501a Thanks @stramel! - The SVG import feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.

  This feature allows you to import SVG files directly into your Astro project as components and inline them into your HTML.

  To use this feature, import an SVG file in your Astro project, passing any common SVG attributes to the imported component.

  ---
  import Logo from './path/to/svg/file.svg';
  ---
  
  <Logo <Logo width={64} height={64} fill="currentColor" />

  If you have been waiting for stabilization before using the SVG Components feature, you can now do so.

  If you were previously using this feature, please remove the experimental flag from your Astro config:

  import { defineConfig } from 'astro'
  
  export default defineConfig({
  -  experimental: {
  -    svg: true,
  -  }
  })

  Additionally, a few features that were available during the experimental stage were removed in a previous release. Please see the v5.6.0 changelog for details if you have not yet already updated your project code for the experimental feature accordingly.

  Please see the SVG Components guide in docs for more about this feature.

@astrojs/netlify@6.3.0

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

@astrojs/node@9.2.0

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.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@changesets/cli (source)	^2.28.1 -> ^2.29.2
@libsql/client (source)	^0.15.2 -> ^0.15.4
@playwright/test (source)	1.51.1 -> 1.52.0
@tailwindcss/vite (source)	^4.1.3 -> ^4.1.4
eslint (source)	^9.24.0 -> ^9.25.0
open	^10.1.0 -> ^10.1.1
open-props	^1.7.14 -> ^1.7.15
package-manager-detector	^1.1.0 -> ^1.2.0
publint (source)	^0.3.10 -> ^0.3.12
shiki (source)	^3.2.1 -> ^3.2.2
smol-toml	^1.3.1 -> ^1.3.3
svelte (source)	^5.25.7 -> ^5.28.1
tailwindcss (source)	^4.1.3 -> ^4.1.4
typescript-eslint (source)	^8.29.0 -> ^8.30.1
vite (source)	^6.2.6 -> ^6.3.2
zod (source)	^3.24.2 -> ^3.24.3

Release Notes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Description

• Closes #3108
• This PR updates the version of the package astro-expressive-code from v0.40 to v0.41. This also replaces Shiki v1 dependencies with Shiki v3.

Changes

• (Potentially) fixes a regression introduced by #13519
• User on Discord reported a build failure introduced between 5.6.0 and 5.6.1. The cause seemed to be astro-icon chunks, which should only be prerendered, were leaking into the server bundle.
  Looking through the commits, the only suspicious commit seems to be #13519, which ported over the following lines.
• Originally, this change was introduced by an ecosystem patch to improve Rolldown compat, but we don't have insight into what bug was being fixed. We're asking around for the context!
• Patch changeset added

Testing

Going to confirm the fix with a preview release, but it would be a good idea to make a prerender chunk test to prevent future regressions

Docs

N/A, bug fix

Description

This PR updates the comparison data of different docs frameworks visible on the environmental impact page with up-to-date 12. April 2025 data fetches.

There are some things to consider:

• Shall we include all these frameworks or leave some out to make the table smaller? If we drop some, which ones?
• Either the Zola calculation is bugged or really respectable, which is very plausible cause it's built with Rust :)

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight-markdoc@0.3.1

Patch Changes

• #3090 fc3ffa8 Thanks @delucis! - Adds support for newer versions of @astrojs/markdoc

• #3109 b5cc1b4 Thanks @dhruvkb! - Updates Expressive Code to v0.41.1

@astrojs/starlight@0.33.2

Patch Changes

• #3090 fc3ffa8 Thanks @delucis! - Updates internal @astrojs/mdx, @astrojs/sitemap, and astro-expressive-code dependencies

• #3109 b5cc1b4 Thanks @dhruvkb! - Updates Expressive Code to v0.41.1

Updates Astro and related dependencies across the monorepo.

A lot of these are just development versions, but these two changes theoretically impact users:

• Updates to @astrojs/mdx, @astrojs/sitemap, and astro-expressive-code in the core Starlight package. The new versions were already covered by our ^ range, but this change ensures people update to the latest versions. Particularly important for the MDX integration as we had some reports of errors for users upgrading Astro, which included a newer version of @astrojs/markdown-remark that conflicted with the older @astrojs/mdx.

• A loosening of our peer dependency version range for @astrojs/markdoc in the Starlight Markdoc preset. This adds support for the newer 0.13.x releases of @astrojs/markdoc.

Changes

Update the list of available choices when running create astro to include the minimal starter.

This is useful for people taking the introductory tutorial in docs, creating minimal reproductions, and for experienced users starting projects from scratch.

In particular, it avoids needing to document workarounds to installing the minimal template for the tutorial via a template flag. (For example, Powershell users cannot follow the command as provided. This leads to them choosing the wrong template at the start of the tutorial, and is confusing when their code doesn't match the tutorial instructions.)

Closes Docs Issue withastro/docs#10843

Testing

Not tested!

Docs

The tutorial docs will be updated (simplified) to no longer require installing the minimal starter using a template flag. (Can be updated separately, as the existing instructions will still work.)

Description

This PR fixes a regression in #2927 where I entirely skipped over the logic to include the description and links to language alternates for multilingual websites to the <head> of the page.

Changes

• To support the Audit dev toolbar app, Astro's compiler injects data-astro-source-file and data-astro-source-loc attributes on every element in dev mode.
• In this PR, the Audit app has been updated to extract the data from these attributes, store them in a WeakMap that is keyed by each Element, and then remove the attributes.
• This should improve the dev mode experience by simplifying the markup when inspecting the page.
• Changeset added.

Impact

This admittedly might break some third-party dev toolbar apps that rely on these annotations. Ideally we would expose a public API to get the annotation info for an element.

Searching all of GitHub for data-astro-source-file yields a decent number of repos, but the vast majority of uses are workarounds to remove the attributes.

Testing

Tested manually because it involves dev mode-specific client-side script behavior, which would be flaky to run in CI.

Docs

As far as I can tell, this is an internal API that we've never documented!

These attributes were added in #9016 and first released in astro@3.5.0 in November 2023. I assume users have gotten used to ignoring them, but they're still visual noise. Since this approach allows us to reduce noise without removing functionality, I think we should.

Changes

• Adds jsdocs

Testing

Docs

Changes

Closes: #13585

• What does this change?

Fixes routing with base paths when trailingSlash is set to 'never', ensuring requests to '/base' are correctly matched when the base path is set to '/base'. The fix also maintains compatibility with rewrites, with all rewrite tests passing successfully.

Testing

I've added 2 🤏🏻 tests 🫡

Docs

Changes

• Addresses feedback from T&D
• Renames Font component family to cssVariable
• Renames font configuration automaticFallback to optimizedFallbacks

Testing

Should pass

Docs

RFC updated

Changes

Update vite to 6.2.6 to fix GHSA-356w-63v5-8wf4

Testing

should pass

Docs

N/A

Description

• Adds my first own theme called Starlight NextJS Theme to the theme.mdx showcase

Changes

• Updates unifont
• Filters fonts so we avoid useless fallbacks
• The patch is removed because it's being contributed upstream (unjs/unifont#154) and it only works in the context of the repo, not once published on NPM

Testing

Manual

Docs

Changeset

Description

• This PR adds the website Starlight Changelog which is built upon Starlog template from Astro to the community content page.
• I'm not sure tho, if the Articles and Reviews section is the right place to add this website...

Changes

• adjusts svg handling to fix a memory leak
• see #12694 for original workaround, Erika's suggestion on #12067
• unblocks #13578

Testing

1. Tested with a modified version of the benchmark script that included 10,000 svg files.
2. Tested against the real-world cloudflare-docs repo, where the original bug report was surfaced. It generates 5K+ page and has 1100+ .svg files. Before this change, I got an OOM error. After this change, I was able to build the site successfully. See Discord thread for full fix verification updates

Docs

Bug fix only

Changes

Avoiding preserve data-astro-* attrs other than data-astro-transition and data-astro-transition-fallback when using swapRootAttributes #135577

Fixes #13577

Testing

Running packages/astro/e2e/view-transitions.test.js

Docs

It' s a patch
martrapp: bug fix, n/a

Description

This PR replaces all z.B. and z. B. with the consistent and recommended spelling notation¹, z. B..
Therefore the i18nIgnore, because this should not mark pages as completed in any way.
Request review from native speaker (@delucis?)!

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight@0.33.1

Patch Changes

• #3088 1885049 Thanks @HiDeoo! - Fixes a regression in Starlight version 0.33.0 that caused the description and links to language alternates for multilingual websites to be missing from the <head> of the page.

• #3065 463adf5 Thanks @HiDeoo! - Updates the social configuration option TSDoc example to match the shape of the expected value.

Description

Following the changes in #3025, this PR updates the social configuration option TSDoc example to reflect the new format.

The example content is the same one as the documentation.

Before	After

Loads '-extras' for CSS, JS and PHP to add more tokens for styling.

Changes

When highlighting CSS, JS and PHP with Prism load the -extras for these to add additional tokens.

CSS example:

code[class*="language-"] .token {
...
}

Without css-extras:

<span class="token selector">
    code[class*="language-"] .token
</span>

With css-extras:

<span class="token selector">
    code
    <span class="token attribute">
        <span class="token punctuation">[</span>
        <span class="token attr-name">class</span>
        <span class="token operator">*=</span>
        <span class="token attr-value">"language-"</span>
        <span class="token punctuation">]</span>
    </span>
    <span class="token class">.token</span>
</span>

Testing

Tested with a local project using pnpm link.

Docs

I don't believe this will break anything since it seems to just add some extras <span class="token ..."></span> inside
the existing ones. Any theme styling applied to outer existing <span>s would still apply even if not using the extra inner ones.

Changes

Unflagging the SVG Component feature!

Testing

Ran against the test fixture

Docs

Will need to remove this section from the experimental docs and likely move it to the standard location
/cc @withastro/maintainers-docs for feedback!

Description

• This PR replaces translations of the English word icon from the German translation Icon to Symbol so it is consistent across all pages. Therefore the i18nIgnore, because this should not mark pages as completed in any way.
• This is a follow-up PR of #2949 where Chris and I agreed on making the translation consistent the other way around (initially I wanted to replace all Symbol with Icon, but Wikipedia says, Symbol is the generally more acceptable translation of icon
• I again ask a native speaker to review this PR, maybe @delucis wants to step up again and help out as always 💜 (I think I didn't miss any Icons with my global VS Code search...)

Description

• Closes #2696
• What does this PR change? #2704 improved the cosmetic of focus ring in site title, however there were a couple of remaining issues as described here. This PR eliminates the overflow: hidden and applies min-width to ensure the title-wrapper is constrained to available space by flexbox. Additionally, it styles the title text (if its displayed) with elipses providing an improved UI so that text is no longer abruptly cut-off but rather gives an indication that there is more text that just isn't visible. If a logo is present, it will be automatically scaled and therefore doesn't require a container with overflow: hidden. Tested in Edge, Chrome & Firefox.
• Did you change something visual? A before/after screenshot can be helpful.

With a forced outline of 10px solid green:

Before Desktop:

Before Mobile:

After Desktop:

After Mobile:

Changes

Currently, each server island includes a script to load its own content. That includes quite a bit of logic that could be shared between islands. This PR extracts that into a function that can be reused by each island, and includes it only once. This runtime script is defined as a classic, non-module script so that we can guarantee that it has always executed before any of the module scripts runs.

Testing

Added and updated tests

Docs

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight@0.33.0

Minor Changes

• #3026 82deb84 Thanks @HiDeoo! - Fixes a potential list styling issue if the last element of a list item is a <script> tag.

  ⚠️ BREAKING CHANGE:

  This release drops official support for Chromium-based browsers prior to version 105 (released 30 August 2022) and Firefox-based browsers prior to version 121 (released 19 December 2023). You can find a list of currently supported browsers and their versions using this browserslist query.

  With this release, Starlight-generated sites will still work fine on those older browsers except for this small detail in list item styling, but future releases may introduce further breaking changes for impacted browsers, including in patch releases.

• #3025 f87e9ac Thanks @delucis! - Makes social configuration more flexible.

  ⚠️ BREAKING CHANGE: The social configuration option has changed syntax. You will need to update this in astro.config.mjs when upgrading.

  Previously, a limited set of platforms were supported using a shorthand syntax with labels built in to Starlight. While convenient, this approach was less flexible and required dedicated code for each social platform added.

  Now, you must specify the icon and label for each social link explicitly and you can use any of Starlight’s built-in icons for social links.

  The following example shows updating the old social syntax to the new:

  - social: {
  -   github: 'https://github.com/withastro/starlight',
  -   discord: 'https://astro.build/chat',
  - },
  + social: [
  +   { icon: 'github', label: 'GitHub', href: 'https://github.com/withastro/starlight' },
  +   { icon: 'discord', label: 'Discord', href: 'https://astro.build/chat' },
  + ],

• #2927 c46904c Thanks @HiDeoo! - Adds the head route data property which contains an array of all tags to include in the <head> of the current page.

  Previously, the <Head> component was responsible for generating a list of tags to include in the <head> of the current page and rendering them.
  This data is now available as Astro.locals.starlightRoute.head instead and can be modified using route data middleware.
  The <Head> component now only renders the tags provided in Astro.locals.starlightRoute.head.

• #2924 6a56d1b Thanks @HiDeoo! - ⚠️ BREAKING CHANGE: Ensures that the <Badge> and <Icon> components no longer render with a trailing space.

  In Astro, components that include styles render with a trailing space which can prevent some use cases from working as expected, e.g. when using such components inlined with text. This change ensures that the <Badge> and <Icon> components no longer render with a trailing space.

  If you were previously relying on that implementation detail, you may need to update your code to account for this change. For example, considering the following code:

  <Badge text="New" />
  Feature

  The rendered text would previously include a space between the badge and the text due to the trailing space automatically added by the component:

  New Feature
  

  Such code will now render the badge and text without a space:

  NewFeature
  

  To fix this, you can add a space between the badge and the text:

  - <Badge text="New" />Feature
  + <Badge text="New" /> Feature

• #2727 7c8fa30 Thanks @techfg! - Updates mobile menu toggle styles to display a close icon while the menu is open

Patch Changes

• #2927 c46904c Thanks @HiDeoo! - Fixes an issue where overriding the canonical URL of a page using the head configuration option or head frontmatter field would strip any other <link> tags from the <head>.

• #2927 c46904c Thanks @HiDeoo! - Fixes an issue where generated canonical URLs would include a trailing slash when using the trailingSlash Astro option is set to 'never'.

• #3025 f87e9ac Thanks @delucis! - Fixes Starlight’s autogenerated <meta name="twitter:site"> tags when a Twitter link is set in social config. Previously these incorrectly rendered content="/username" and now correctly render content="@username".

Changes

• Google and Fontsource unifont providers download too much files if a variable font is present
• Until unjs/unifont#108 is addressed, this adds a patch

Testing

Manual

Docs

N/A

Changes

• Removes the default provider to reduce confusion and improve consistency
• Now, google must be used like fontProviders.google()
• Simplifies the code by a lot

Testing

Updated

Docs

RFC updated

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@libsql/client (source)	^0.15.1 -> ^0.15.2
@preact/signals (source)	^2.0.2 -> ^2.0.3
@tailwindcss/vite (source)	^4.0.17 -> ^4.1.3
@types/react-dom (source)	^18.3.5 -> ^18.3.6
eslint (source)	^9.23.0 -> ^9.24.0
fast-xml-parser	^5.0.9 -> ^5.2.0
preact (source)	^10.26.4 -> ^10.26.5
publint (source)	^0.3.9 -> ^0.3.10
remark-rehype	^11.1.1 -> ^11.1.2
sass	^1.86.0 -> ^1.86.3
svelte (source)	^5.25.3 -> ^5.25.7
tailwindcss (source)	^4.0.17 -> ^4.1.3
turbo (source)	^2.4.4 -> ^2.5.0
typescript (source)	^5.8.2 -> ^5.8.3
typescript (source)	~5.8.2 -> ~5.8.3
typescript-eslint (source)	^8.28.0 -> ^8.29.0
vitest (source)	^3.0.9 -> ^3.1.1

Release Notes

{
  "code": "InvalidAttr",
  "msg":  "Attribute 'abc' is repeated.",
  "line": 1,
  "col": 22
}

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Changes

Fix build errors being ignored when using concurrency, by using Promise.all instead of Promise.allSettled

Testing

Added a test fixture that throws an error when built.

Docs

N/A (expected behaviour)

Added our starlight-full-view-mode community plugin

Description

• Closes #
• What does this PR change? Give us a brief description.
• Did you change something visual? A before/after screenshot can be helpful.

This PR will change the community plugins by adding my own plugin to the website.

Before

After

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight@0.32.6

Patch Changes

• #3030 5bdf139 Thanks @trueberryless! - Updates the type of the isFallback field in route data from true to boolean, keeping it optional but allowing false as a possible value.

• #3018 188b8cf Thanks @trueberryless! - Adds validation for user config routeMiddleware so it does not conflict with Astro's middleware.

Changes

This PR makes astro:config stable.

Testing

Updated the existing tests.

Docs

withastro/docs#11380

/cc @withastro/maintainers-docs for feedback!

Description

• Closes #1239
• This PR adds built-in support for rendering clickable anchor links alongside headings.

Where does this apply?

1. For Markdown and MDX files, anchor links are added using rehype plugins. This can be disabled with markdown: { headingLinks: false } in Starlight config.
2. For Markdoc files, anchor links are added with a custom renderer for the heading node. This can be disabled by passing { headingLinks: false } to the Starlight Markdoc preset.
3. In Astro components, anchor links can be added with a new <AnchorHeading> component.

The anchor link approach

The HTML mark-up approach the anchor links follow is based on Amber Wilson’s Are your Anchor Links Accessible? blog post. (Thank you for sharing your research, Amber!)

The output looks a little like this:

<div>
  <h2 id="a-heading">A heading</h2>
  <a href="#a-heading">
    <span class="sr-only">Section titled “A heading”</span>
    <svg>...</svg>
  </a>
</div>

• The <a> link is placed after the heading element rather than inside it or even wrapping it as some sites do. This ensures that the heading doesn’t contain any additional text (for screenreaders listing headings for example) and also avoids the potentially confusing situation of a link which links to itself.
• The accessible “Section titled…” label uses Starlight’s internationalization APIs so it can be localized.
• The heading and link are wrapped in a <div> so that we can position the icon link inline at the end of the heading as desired.
• There are more notes about the actual styles for the layout in anchor-links.css in this PR.

To-do

• Write tests for the rehype plugins.
• Write tests to assert that component and plugin markup matches.
• Fix the use of rehypeSlug and use Astro’s built-in heading slugger instead.
• Add changesets

Changes

• Addresses feedback from Chris
• With this PR, we don't throw an error in dev if a local font file used is deleted. Instead we show a warning in the terminal
• Allows to remove a bunch of code

Testing

Updated and manual

Docs

N/A

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.6.2

Patch Changes

• #13606 793ecd9 Thanks @natemoo-re! - Fixes a regression that allowed prerendered code to leak into the server bundle.

• #13576 1c60ec3 Thanks @ascorbic! - Reduces duplicate code in server islands scripts by extracting shared logic into a helper function.

• #13588 57e59be Thanks @natemoo-re! - Fixes a memory leak when using SVG assets.

• #13589 5a0563d Thanks @ematipico! - Deprecates the asset utility function emitESMImage() and adds a new emitImageMetadata() to be used instead

  The function
  emitESMImage() is now deprecated. It will continue to function, but it is no longer recommended nor supported. This function will be completely removed in a next major release of Astro.

  Please replace it with the new functionemitImageMetadata() as soon as you are able to do so:

  - import { emitESMImage } from "astro/assets/utils";
  + import { emitImageMetadata } from "astro/assets/utils";

  The new function returns the same signature as the previous one. However, the new function removes two deprecated arguments that were not meant to be exposed for public use: _watchMode and experimentalSvgEnabled. Since it was possible to access these with the old function, you may need to verify that your code still works as intended with emitImageMetadata().

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

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

• #13548 e588527 Thanks @ryuapp! - Support for Deno to install npm pacakges.

  Deno requires npm prefix to install packages on npm. For example, to install react, we need to run deno add npm:react. But currently the command executed is deno add react, which doesn't work. So, we change the package names to have an npm prefix if you are using Deno.

• #13587 a0774b3 Thanks @robertoms99! - Fixes an issue with the client router where some attributes of the root element were not updated during swap, including the transition scope.

@astrojs/db@0.14.11

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 [3752519, 360cb91]:

  • @astrojs/studio@0.1.7

@astrojs/alpinejs@0.4.6

Patch Changes

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

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

@astrojs/cloudflare@12.4.1

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

@astrojs/markdoc@0.13.4

Patch Changes

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

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

@astrojs/mdx@4.2.4

Patch Changes

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

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

@astrojs/netlify@6.2.6

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

@astrojs/preact@4.0.9

Patch Changes

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

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

@astrojs/react@4.2.4

Patch Changes

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

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

@astrojs/solid-js@5.0.8

Patch Changes

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

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

@astrojs/svelte@7.0.10

Patch Changes

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

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

@astrojs/vue@5.0.10

Patch Changes

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

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

@astrojs/studio@0.1.7

Patch Changes

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

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

Changes

• See https://github.com/withastro/astro/actions/runs/14262214393/job/39976145237#step:8:15

Testing

Docs

Changes

• Adds support for entrypoints in local families variants.src: path relative to the root, urls and package imports are now supported
• Adds support for font techs: variants.src can also contain objects with url (same rules as line above) and optional tech
• Fixes a bug where default fallbacks would not be applied

Testing

Updated

Docs

RFC updated

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.6.1

Patch Changes

• #13519 3323f5c Thanks @florian-lefebvre! - Refactors some internals to improve Rolldown compatibility

• #13545 a7aff41 Thanks @stramel! - Prevent empty attributes from appearing in the SVG output

• #13552 9cd0fd4 Thanks @ematipico! - Fixes an issue where Astro validated the i18n configuration incorrectly, causing false positives in downstream libraries.

Changes

• Addresses feedback from Chris
• Updates the shape of the local font family: src becomes variants, src.paths becomes variants.src
• Moves the transforms to resolveFontFamily so they also apply to fonts added through integrations

Testing

Updated

Docs

RFC updated

Changes

• Deno requires a prefix when installing packages
• So, if you use Deno as your package manager, prepend npm: to the library name

Before deno task astro add react

After deno task astro add react

Testing

It was manually tested on local. We can install and try out this PR's astro.

Docs

I think Astro don't officially supports Deno as a package manager, so I'll write about it if necessary.

Changes

Update vite to 6.2.5 to resolve GHSA-xcj6-pq6g-qj4x

Testing

should pass

Docs

N/A

Changes

Updating to the latest 1.6.0 which fixes the issue and brings in some optimizations to the regexes it uses.
Fixes #13496

Testing

Added a test to assert that there were no empty attributes ="" in the resultant html with an SVG known to produce it.

Docs

Not necessary as this is just a bug fix.

Changes

• Addresses feedback from the API bash
• Removes the as prop. Instead, we generate a new nameWithHash (hash computed from the family config object) property to avoid conflicts if the same font name is specified more than once
• Adds a new required cssVariable property. That gives control to the user and avoids having to guess. There's minimal validation, that should handle most mistakes
• It simplifies a lot of things by removing some checks and errors that are now unecessary

Testing

Manual and automated

Docs

RFC updated

Changes

Updates the formatting of the changeset for the SVG API breaking changes

Testing

no tests, just docs

Docs

only docs!

Description

This is rather a question / discussion of the decision why the isFallback type is defined as type true instead of boolean:

This has the consequence that my editor gives me the warning (when I use <StarlightPage>:

My var isFallback is of type boolean:

I'm not sure if this is an oversight or has a specific reason, therefore I'm creating this as a draft PR...

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.6.0

Minor Changes

• #13403 dcb9526 Thanks @yurynix! - Adds a new optional prerenderedErrorPageFetch option in the Adapter API to allow adapters to provide custom implementations for fetching prerendered error pages.

  Now, adapters can override the default fetch() behavior, for example when fetch() is unavailable or when you cannot call the server from itself.

  The following example provides a custom fetch for 500.html and 404.html, reading them from disk instead of performing an HTTP call:

  return app.render(request, {
    prerenderedErrorPageFetch: async (url: string): Promise<Response> => {
      if (url.includes("/500")) {
          const content = await fs.promises.readFile("500.html", "utf-8");
          return new Response(content, {
            status: 500,
            headers: { "Content-Type": "text/html" },
          });
      }
      const content = await fs.promises.readFile("404.html", "utf-8");
        return new Response(content, {
          status: 404,
          headers: { "Content-Type": "text/html" },
        });
  });

  If no value is provided, Astro will fallback to its default behavior for fetching error pages.

  Read more about this feature in the Adapter API reference.

• #13482 ff257df Thanks @florian-lefebvre! - Updates Astro config validation to also run for the Integration API. An error log will specify which integration is failing the validation.

  Now, Astro will first validate the user configuration, then validate the updated configuration after each integration astro:config:setup hook has run. This means updateConfig() calls will no longer accept invalid configuration.

  This fixes a situation where integrations could potentially update a project with a malformed configuration. These issues should now be caught and logged so that you can update your integration to only set valid configurations.

• #13405 21e7e80 Thanks @Marocco2! - Adds a new eagerness option for prefetch() when using experimental.clientPrerender

  With the experimental clientPrerender flag enabled, you can use the eagerness option on prefetch() to suggest to the browser how eagerly it should prefetch/prerender link targets.

  This follows the same API described in the Speculation Rules API and allows you to balance the benefit of reduced wait times against bandwidth, memory, and CPU costs for your site visitors.

  For example, you can now use prefetch() programmatically with large sets of links and avoid browser limits in place to guard against over-speculating (prerendering/prefetching too many links). Set eagerness: 'moderate' to take advantage of First In, First Out (FIFO) strategies and browser heuristics to let the browser decide when to prerender/prefetch them and in what order:

  <a class="link-moderate" href="/nice-link-1">A Nice Link 1</a>
  <a class="link-moderate" href="/nice-link-2">A Nice Link 2</a>
  <a class="link-moderate" href="/nice-link-3">A Nice Link 3</a>
  <a class="link-moderate" href="/nice-link-4">A Nice Link 4</a>
  ...
  <a class="link-moderate" href="/nice-link-20">A Nice Link 20</a>
  <script>
    import { prefetch } from 'astro:prefetch';
    const linkModerate = document.getElementsByClassName('link-moderate');
    linkModerate.forEach((link) => prefetch(link.getAttribute('href'), { eagerness: 'moderate' }));
  </script>

• #13482 ff257df Thanks @florian-lefebvre! - Improves integrations error handling

  If an error is thrown from an integration hook, an error log will now provide information about the concerned integration and hook

Patch Changes

• #13539 c43bf8c Thanks @ascorbic! - Adds a new session.load() method to the experimental session API that allows you to load a session by ID.

  When using the experimental sessions API, you don't normally need to worry about managing the session ID and cookies: Astro automatically reads the user's cookies and loads the correct session when needed. However, sometimes you need more control over which session to load.

  The new load() method allows you to manually load a session by ID. This is useful if you are handling the session ID yourself, or if you want to keep track of a session without using cookies. For example, you might want to restore a session from a logged-in user on another device, or work with an API endpoint that doesn't use cookies.

  // src/pages/api/cart.ts
  import type { APIRoute } from 'astro';
  
  export const GET: APIRoute = async ({ session, request }) => {
    // Load the session from a header instead of cookies
    const sessionId = request.headers.get('x-session-id');
    await session.load(sessionId);
    const cart = await session.get('cart');
    return Response.json({ cart });
  };

  If a session with that ID doesn't exist, a new one will be created. This allows you to generate a session ID in the client if needed.

  For more information, see the experimental sessions docs.

• #13488 d777420 Thanks @stramel! - BREAKING CHANGE to the experimental SVG Component API only

  Removes some previously available prop, attribute, and configuration options from the experimental SVG API. These items are no longer available and must be removed from your code:

  • The title prop has been removed until we can settle on the correct balance between developer experience and accessibility. Please replace any title props on your components with aria-label:

    - <Logo title="My Company Logo" />
    + <Logo aria-label="My Company Logo" />

  • Sprite mode has been temporarily removed while we consider a new implementation that addresses how this feature was being used in practice. This means that there are no longer multiple mode options, and all SVGs will be inline. All instances of mode must be removed from your project as you can no longer control a mode:

    - <Logo mode="inline" />
    + <Logo />

    import { defineConfig } from 'astro'
    
    export default defineConfig({
      experimental: {
    -    svg: {
    -      mode: 'sprite'
    -    },
    +   svg: true
      }
    });

  • The default role is no longer applied due to developer feedback. Please add the appropriate role on each component individually as needed:

    - <Logo />
    + <Logo role="img" /> // To keep the role that was previously applied by default

  • The size prop has been removed to better work in combination with viewBox and additional styles/attributes. Please replace size with explicit width and height attributes:

    - <Logo size={64} />
    + <Logo width={64} height={64} />

Changes

Adds support for loading a session by ID

Adds a new session.load() method to the experimental session API that allows you to load a session by ID. In normal use a session is loaded automatically from the session cookie. This method allows a session to be loaded manually instead. This has been requested in the RFC, and is useful for cases where the session ID has been persisted somewhere other than the browser cookie. For example, a session ID might be stored in a user database. This would allow that user's session to be loaded when logging-in on another device or in a different browser. It would also allow a session to be loaded in an API when cookies can't be set, such as when loading across domains.

Testing

Added tests

Docs

I will do a separate docs PR

Changes

• Depends on #13515
• In development, only log if there's an error. That also means the download font error is not thrown anymore so someone with connectivity issues can keep developing
• During builds, only one log is added to show something fonts related is happening

Testing

Manual

Docs

N/A

Changes

• Depends on #13533
• Passes the family name as is. If the family name should contain wrapping quotes, then it has to be passed in the config (eg. family: '"Roboto"')

Testing

N/A

Docs

N/A

Changes

• Feedback from the API bash. Renames defineFontProvider to defineAstroFontProvider to avoid the confusion with defineFontProvider from unifont
• Depends on #13515

Testing

N/A

Docs

Later

Changes

Update vite to 6.2.4 to resolve GHSA-4r4m-qw57-chr8

Testing

should pass

Docs

N/A

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@preact/signals (source)	^2.0.1 -> ^2.0.2
@types/react (source)	^18.3.19 -> ^18.3.20
svelte (source)	^5.23.2 -> ^5.25.3

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@codspeed/vitest-plugin (source)	4.0.0 -> 4.0.1
@libsql/client (source)	^0.15.0 -> ^0.15.1
@preact/signals (source)	^2.0.1 -> ^2.0.2
@tailwindcss/vite (source)	^4.0.15 -> ^4.0.17
@types/estree (source)	^1.0.6 -> ^1.0.7
@types/react (source)	^18.3.19 -> ^18.3.20
@types/semver (source)	^7.5.8 -> ^7.7.0
eslint (source)	^9.22.0 -> ^9.23.0
svelte (source)	^5.23.2 -> ^5.25.3
tailwindcss (source)	^4.0.15 -> ^4.0.17
typescript-eslint (source)	^8.27.0 -> ^8.28.0