chore(deps): update dependency astro to v5.16.15 #56

renovate · 2025-12-03T17:44:35Z

This PR contains the following updates:

Package	Change	Age	Confidence
astro (source)	`5.16.3` → `5.16.15`

Release Notes

withastro/astro (astro)

`v5.16.15`

Compare Source

Patch Changes

#15286 0aafc83 Thanks @florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

`v5.16.14`

Compare Source

Patch Changes

#15213 c775fce Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Updates how the local provider must be used when using the experimental Fonts API

Previously, there were 2 kinds of font providers: remote and local.

Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

-import { defineConfig } from "astro/config";
+import { defineConfig, fontProviders } from "astro/config";

export default defineConfig({
    experimental: {
        fonts: [{
            name: "Custom",
            cssVariable: "--font-custom",
-            provider: "local",
+            provider: fontProviders.local(),
+            options: {
            variants: [
                {
                    weight: 400,
                    style: "normal",
                    src: ["./src/assets/fonts/custom-400.woff2"]
                },
                {
                    weight: 700,
                    style: "normal",
                    src: ["./src/assets/fonts/custom-700.woff2"]
                }
                // ...
            ]
+            }
        }]
    }
});

Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

See the experimental Fonts API docs for more information.

#15213 c775fce Thanks @florian-lefebvre! - Exposes root on FontProvider init() context

When building a custom FontProvider for the experimental Fonts API, the init() method receives a context. This context now exposes a root URL, useful for resolving local files:
```
import type { FontProvider } from "astro";

export function registryFontProvider(): FontProvider {
  return {
    // ...
-    init: async ({ storage }) => {
+    init: async ({ storage, root }) => {
        // ...
    },
  };
}
```
#15185 edabeaa Thanks @EricGrill! - Add .vercel to .gitignore when adding the Vercel adapter via astro add vercel

`v5.16.13`

Compare Source

Patch Changes

#15182 cb60ee1 Thanks @florian-lefebvre! - Adds a new getFontBuffer() method to retrieve font file buffers when using the experimental Fonts API

The getFontData() helper function from astro:assets was introduced in 5.14.0 to provide access to font family data for use outside of Astro. One of the goals of this API was to be able to retrieve buffers using URLs.

However, it turned out to be impactical and even impossible during prerendering.

Astro now exports a new getFontBuffer() helper function from astro:assets to retrieve font file buffers from URL returned by getFontData(). For example, when using satori to generate OpenGraph images:

// src/pages/og.png.ts

import type{ APIRoute } from "astro"
-import { getFontData } from "astro:assets"
+import { getFontData, getFontBuffer } from "astro:assets"
import satori from "satori"

export const GET: APIRoute = (context) => {
  const data = getFontData("--font-roboto")

  const svg = await satori(
    <div style={{ color: "black" }}>hello, world</div>,
    {
      width: 600,
      height: 400,
      fonts: [
        {
          name: "Roboto",
-          data: await fetch(new URL(data[0].src[0].url, context.url.origin)).then(res => res.arrayBuffer()),
+          data: await getFontBuffer(data[0].src[0].url),
          weight: 400,
          style: "normal",
        },
      ],
    },
  )

  // ...
}

See the experimental Fonts API documentation for more information.

`v5.16.12`

Compare Source

Patch Changes

#15175 47ae148 Thanks @florian-lefebvre! - Allows experimental Font providers to specify family options

Previously, an Astro FontProvider could only accept options at the provider level when called. That could result in weird data structures for family-specific options.

Astro FontProviders can now declare family-specific options, by specifying a generic:

// font-provider.ts
import type { FontProvider } from "astro";
import { retrieveFonts, type Fonts } from "./utils.js",

interface Config {
  token: string;
}

+interface FamilyOptions {
+    minimal?: boolean;
+}

-export function registryFontProvider(config: Config): FontProvider {
+export function registryFontProvider(config: Config): FontProvider<FamilyOptions> {
  let data: Fonts = {}

  return {
    name: "registry",
    config,
    init: async () => {
      data = await retrieveFonts(token);
    },
    listFonts: () => {
      return Object.keys(data);
    },
-    resolveFont: ({ familyName, ...rest }) => {
+    // options is typed as FamilyOptions
+    resolveFont: ({ familyName, options, ...rest }) => {
      const fonts = data[familyName];
      if (fonts) {
        return { fonts };
      }
      return undefined;
    },
  };
}

Once the font provider is registered in the Astro config, types are automatically inferred:

// astro.config.ts
import { defineConfig } from "astro/config";
import { registryFontProvider } from "./font-provider";

export default defineConfig({
    experimental: {
        fonts: [{
            provider: registryFontProvider({
              token: "..."
            }),
            name: "Custom",
            cssVariable: "--font-custom",
+            options: {
+                minimal: true
+            }
        }]
    }
});

#15175 47ae148 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Updates how options are passed to the Google and Google Icons font providers when using the experimental Fonts API

Previously, the Google and Google Icons font providers accepted options that were specific to given font families.

These options must now be set using the options property instead. For example using the Google provider:

import { defineConfig, fontProviders } from "astro/config";

export default defineConfig({
    experimental: {
        fonts: [{
            name: 'Inter',
            cssVariable: '--astro-font-inter',
            weights: ['300 900'],
-            provider: fontProviders.google({
-                experimental: {
-                    variableAxis: {
-                        Inter: { opsz: ['14..32'] }
-                    }
-                }
-            }),
+            provider: fontProviders.google(),
+            options: {
+                experimental: {
+                    variableAxis: { opsz: ['14..32'] }
+                }
+            }
        }]
    }
})

#15200 c0595b3 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Removes getFontData() exported from astro:assets with fontData when using the experimental Fonts API

Accessing font data can be useful for advanced use cases, such as generating meta tags or Open Graph images. Before, we exposed a getFontData() helper function to retrieve the font data for a given cssVariable. That was however limiting for programmatic usages that need to access all font data.

The getFontData() helper function is removed and replaced by a new fontData object:
```
-import { getFontData } from "astro:assets";
-const data = getFontData("--font-roboto")

+import { fontData } from "astro:assets";
+const data = fontData["--font-roboto"]
```
We may reintroduce getFontData() later on for a more friendly DX, based on your feedback.
#15254 8d84b30 Thanks @lamalex! - Fixes CSS assetsPrefix with remote URLs incorrectly prepending a forward slash

When using build.assetsPrefix with a remote URL (e.g., https://cdn.example.com) for CSS assets, the generated <link> elements were incorrectly getting a / prepended to the full URL, resulting in invalid URLs like /https://cdn.example.com/assets/style.css.

This fix checks if the stylesheet link is a remote URL before prepending the forward slash.
#15178 731f52d Thanks @kedarvartak! - Fixes an issue where stopping the dev server with q+enter incorrectly created a dist folder and copied font files when using the experimental Fonts API
#15230 3da6272 Thanks @rahuld109! - Fixes greedy regex in error message markdown rendering that caused link syntax examples to capture extra characters
#15253 2a6315a Thanks @matthewp! - Fixes hydration for React components nested inside HTML elements in MDX files
#15227 9a609f4 Thanks @matthewp! - Fixes styles not being included for conditionally rendered Svelte 5 components in production builds
#14607 ee52160 Thanks @simensfo! - Reintroduces css deduplication for hydrated client components. Ensures assets already added to a client chunk are not flagged as orphaned

`v5.16.11`

Compare Source

Patch Changes

#15017 9e7a3c8 Thanks @ixchio! - Fixes CSS double-bundling when the same CSS file is imported in both a page's frontmatter and a component's script tag
#15225 6fe62e1 Thanks @ematipico! - Updates to the latest version of devalue

`v5.16.10`

Compare Source

Patch Changes

2fa19c4 - Improved error handling in the rendering phase

Added defensive validation in App.render() and #renderError() to provide a descriptive error message when a route module doesn't have a valid page function.
#15199 d8e64ef Thanks @ArmandPhilippot! - Fixes the links to Astro Docs so that they match the current docs structure.
#15169 b803d8b Thanks @rururux! - fix: fix image 500 error when moving dist directory in standalone Node
#14622 9b35c62 Thanks @aprici7y! - Fixes CSS url() references to public assets returning 404 in dev mode when base path is configured
#15219 43df4ce Thanks @matthewp! - Upgrades the diff package to v8

`v5.16.9`

Compare Source

Patch Changes

#15174 37ab65a Thanks @florian-lefebvre! - Adds Google Icons to built-in font providers

To start using it, access it on fontProviders:

import { defineConfig, fontProviders } from 'astro/config';

export default defineConfig({
  experimental: {
    fonts: [
      {
        name: 'Material Symbols Outlined',
        provider: fontProviders.googleicons(),
        cssVariable: '--font-material',
      },
    ],
  },
});

#15150 a77c4f4 Thanks @matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.
#15130 9b726c4 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Changes how font providers are implemented with updates to the FontProvider type

This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

What should I do?

If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

// astro.config.ts
import { defineConfig } from "astro/config";
import { acmeProvider, type AcmeOptions } from '@&#8203;acme/unifont-provider'
+import type { FontProvider } from "astro";
+import type { InitializedProvider } from 'unifont';

+function acme(config?: AcmeOptions): FontProvider {
+	const provider = acmeProvider(config);
+	let initializedProvider: InitializedProvider | undefined;
+	return {
+		name: provider._name,
+		config,
+		async init(context) {
+			initializedProvider = await provider(context);
+		},
+		async resolveFont({ familyName, ...rest }) {
+			return await initializedProvider?.resolveFont(familyName, rest);
+		},
+		async listFonts() {
+			return await initializedProvider?.listFonts?.();
+		},
+	};
+}

export default defineConfig({
    experimental: {
        fonts: [{
-            provider: acmeProvider({ /* ... */ }),
+            provider: acme({ /* ... */ }),
            name: "Material Symbols Outlined",
            cssVariable: "--font-material"
        }]
    }
});

#15147 9cd5b87 Thanks @matthewp! - Fixes scripts in components not rendering when a sibling <Fragment slot="..."> exists but is unused

`v5.16.8`

Compare Source

Patch Changes

#15124 81db3c0 Thanks @leonace924! - Fixes an issue where requests with query parameters to the base path would return a 404 if trailingSlash was not 'ignore' in development
#15152 39ee41f Thanks @rururux! - Fixes a case where context.cookies.set() would be overriden when setting cookies via response headers in development
#15140 6f6f8f8 Thanks @cameronraysmith! - Fixes esbuild warning due to dead code in assets virtual module
#15127 2cff904 Thanks @Princesseuh! - Updates "Unsupported page types found" error to only appear in more realistic cases
#15149 34f84c2 Thanks @rahuld109! - Skips "Use the Image component" audit warning for images inside framework components (React, Vue, Svelte, etc.)

`v5.16.7`

Compare Source

Patch Changes

#15122 b137946 Thanks @florian-lefebvre! - Improves JSDoc annotations for AstroGlobal, AstroSharedContext and APIContext types
#15123 3f58fa2 Thanks @43081j! - Improves rendering performance by grouping render chunks when emitting from async iterables to avoid encoding costs
#14954 7bec4bd Thanks @volpeon! - Fixes remote images Etag header handling by disabling internal cache
#15052 b2bcd5a Thanks @Princesseuh! - Fixes images not working in development when using setups with port forwarding
#15028 87b19b8 Thanks @Princesseuh! - Fixes certain aliases not working when using images in JSON files with the content layer

#15118 cfa382b Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Removes the defineAstroFontProvider() type helper.

If you are building a custom font provider, remove any occurrence of defineAstroFontProvider() and use the FontProvider type instead:

-import { defineAstroFontProvider } from 'astro/config';

-export function myProvider() {
-    return defineAstroFontProvider({
-        entrypoint: new URL('./implementation.js', import.meta.url)
-    });
-};

+import type { FontProvider } from 'astro';

+export function myProvider(): FontProvider {
+    return {
+        entrypoint: new URL('./implementation.js', import.meta.url)
+    },
+}

#15055 4e28db8 Thanks @delucis! - Reduces Astro’s install size by around 8 MB
#15088 a19140f Thanks @martrapp! - Enables the ClientRouter to preserve the original hash part of the target URL during server side redirects.
#15117 b1e8e32 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Changes the font format downloaded by default when using the experimental Fonts API. Additionally, adds a new formats configuration option to specify which font formats to download.

Previously, Astro was opinionated about which font sources would be kept for usage, mainly keeping woff2 and woff files.

You can now specify what font formats should be downloaded (if available). Only woff2 files are downloaded by default.

What should I do?

If you were previously relying on Astro downloading the woff format, you will now need to specify this explicitly with the new formats configuration option. Additionally, you may also specify any additional file formats to download if available:

// astro.config.mjs
import { defineConfig, fontProviders } from 'astro/config'

export default defineConfig({
    experimental: {
        fonts: [{
            name: 'Roboto',
            cssVariable: '--font-roboto',
            provider: fontProviders.google(),
+            formats: ['woff2', 'woff', 'otf']
        }]
    }
})

#15034 8115752 Thanks @florian-lefebvre! - Fixes a vite warning log during builds when using npm

`v5.16.6`

Compare Source

Patch Changes

#14982 6849e38 Thanks @Princesseuh! - Fixes images outside the project directory not working when using astro:assets in development mode
#14987 9dd9fca Thanks @Princesseuh! - Fixes SVGs not working in dev mode when using the passthrough image service
#15014 a178422 Thanks @delucis! - Adds support for extending the type of the props accepted by Astro’s <Image> component, <Picture> component, and getImage() API.

`v5.16.5`

Compare Source

Patch Changes

#14985 c016f10 Thanks @florian-lefebvre! - Fixes a case where JSDoc annotations wouldn't show for fonts related APIs in the Astro config
#14973 ed7cc2f Thanks @amankumarpandeyin! - Fixes performance regression and OOM errors when building medium-sized blogs with many content entries. Replaced O(n²) object spread pattern with direct mutation in generateLookupMap.
#14958 70eb542 Thanks @ascorbic! - Gives a helpful error message if a user sets output: "hybrid" in their Astro config.

The option was removed in Astro 5, but lots of content online still references it, and LLMs often suggest it. It's not always clear that the replacement is output: "static", rather than output: "server". This change adds a helpful error message to guide humans and robots.
#14901 ef53716 Thanks @Darknab! - Updates the glob() loader to log a warning when duplicated IDs are detected
Updated dependencies [d8305f8]:
- @astrojs/markdown-remark@6.3.10

`v5.16.4`

Compare Source

Patch Changes

#14940 2cf79c2 Thanks @ematipico! - Fixes a bug where Astro didn't properly combine CSP resources from the csp configuration with those added using the runtime API (Astro.csp.insertDirective()) to form grammatically correct CSP headers

Now Astro correctly deduplicate CSP resources. For example, if you have a global resource in the configuration file, and then you add a
a new one using the runtime APIs.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

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

coderabbitai · 2025-12-03T17:44:40Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

renovate bot force-pushed the renovate/astro-monorepo branch from 95e2553 to 681a7e8 Compare December 10, 2025 19:09

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.4~~ chore(deps): update dependency astro to v5.16.5 Dec 10, 2025

renovate bot force-pushed the renovate/astro-monorepo branch from 681a7e8 to 69fd42e Compare December 16, 2025 12:46

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.5~~ chore(deps): update dependency astro to v5.16.6 Dec 16, 2025

renovate bot force-pushed the renovate/astro-monorepo branch from 69fd42e to 390e6a4 Compare December 31, 2025 13:34

renovate bot force-pushed the renovate/astro-monorepo branch from 390e6a4 to 664e6c5 Compare January 7, 2026 17:35

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.6~~ chore(deps): update dependency astro to v5.16.7 Jan 7, 2026

renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 692857a to 734796d Compare January 9, 2026 14:02

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.7~~ chore(deps): update dependency astro to v5.16.8 Jan 9, 2026

renovate bot force-pushed the renovate/astro-monorepo branch from 734796d to 21f5ed9 Compare January 12, 2026 16:32

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.8~~ chore(deps): update dependency astro to v5.16.9 Jan 12, 2026

renovate bot force-pushed the renovate/astro-monorepo branch from 21f5ed9 to 2d7fd28 Compare January 16, 2026 03:15

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.9~~ chore(deps): update dependency astro to v5.16.10 Jan 16, 2026

renovate bot force-pushed the renovate/astro-monorepo branch from 2d7fd28 to c7338bf Compare January 16, 2026 16:28

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.10~~ chore(deps): update dependency astro to v5.16.11 Jan 16, 2026

renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 1e33fef to 3786571 Compare January 21, 2026 14:43

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.11~~ chore(deps): update dependency astro to v5.16.12 Jan 21, 2026

renovate bot force-pushed the renovate/astro-monorepo branch from 3786571 to d74a3e7 Compare January 22, 2026 09:24

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.12~~ chore(deps): update dependency astro to v5.16.13 Jan 22, 2026

renovate bot force-pushed the renovate/astro-monorepo branch from d74a3e7 to 4c4493c Compare January 22, 2026 17:15

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.13~~ chore(deps): update dependency astro to v5.16.14 Jan 22, 2026

renovate bot force-pushed the renovate/astro-monorepo branch from 4c4493c to 21dc98c Compare January 23, 2026 11:02

renovate bot changed the title ~~chore(deps): update dependency astro to v5.16.14~~ chore(deps): update dependency astro to v5.16.15 Jan 23, 2026

chore(deps): update dependency astro to v5.16.15

f3bbaa7

renovate bot force-pushed the renovate/astro-monorepo branch from 21dc98c to f3bbaa7 Compare January 23, 2026 17:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency astro to v5.16.15 #56

chore(deps): update dependency astro to v5.16.15 #56

renovate bot commented Dec 3, 2025 •

edited

Loading

Uh oh!

coderabbitai bot commented Dec 3, 2025

Review skipped

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore(deps): update dependency astro to v5.16.15 #56

Are you sure you want to change the base?

chore(deps): update dependency astro to v5.16.15 #56

Conversation

renovate bot commented Dec 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

What should I do?

Patch Changes

Patch Changes

What should I do?

Patch Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

coderabbitai bot commented Dec 3, 2025

Review skipped

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Dec 3, 2025 •

edited

Loading