build(deps): bump the npm-production group across 1 directory with 3 updates

[dependabot]

Bumps the npm-production group with 3 updates in the / directory: @astrojs/vercel, @astrojs/node and astro.

Updates @astrojs/vercel from 9.0.2 to 9.0.4

Release notes

Sourced from @​astrojs/vercel's releases.

@​astrojs/vercel@​9.0.4

Patch Changes

• #14863 29fd188 Thanks @​drwpow! - Improves error message when using Node builtins inside Edge middlewares

@​astrojs/vercel@​9.0.3

Patch Changes

• #15116 9fc4562 Thanks @​Raanelom! - Updates Node versions data to account for v24 as the default

Changelog

Sourced from @​astrojs/vercel's changelog.

9.0.4

Patch Changes

• #14863 29fd188 Thanks @​drwpow! - Improves error message when using Node builtins inside Edge middlewares

9.0.3

Patch Changes

• #15116 9fc4562 Thanks @​Raanelom! - Updates Node versions data to account for v24 as the default

Commits

• 44f4e78 [ci] release (#15188)
• 8068bad [ci] format
• 29fd188 Revert fix: Allow node: prefix for Node builtins for Vercel middleware (#14863)
• fc1f331 fix(deps): update astro adapters (#15173)
• e73deb8 [ci] release (#15031)
• 9fc4562 Feature/allow node 24 vercel adapter (#15116)
• 5fdd541 fix(deps): update astro adapters (#15084)
• See full diff in compare view

Updates @astrojs/node from 9.5.1 to 9.5.2

Release notes

Sourced from @​astrojs/node's releases.

@​astrojs/node@​9.5.2

Patch Changes

• #15196 a8317c1 Thanks @​ematipico! - Fixes an issue where some prendered pages weren't correctly rendered when using the Node.js adapter in middleware mode.

• #15169 b803d8b Thanks @​rururux! - fix: fix image 500 error when moving dist directory in standalone Node

Changelog

Sourced from @​astrojs/node's changelog.

9.5.2

Patch Changes

• #15196 a8317c1 Thanks @​ematipico! - Fixes an issue where some prendered pages weren't correctly rendered when using the Node.js adapter in middleware mode.

• #15169 b803d8b Thanks @​rururux! - fix: fix image 500 error when moving dist directory in standalone Node

Commits

• 44f4e78 [ci] release (#15188)
• 2fa19c4 fix(core): add defensive validation for mod.page in App.render (#15148)
• 8d74e9e [ci] format
• a8317c1 fix(node): hash URL stripping (#15196)
• 9b4fe82 [ci] format
• b803d8b fix: fix image 500 error when moving dist directory in standalone Node (#15169)
• 5fdd541 fix(deps): update astro adapters (#15084)
• 4db7902 fix(deps): update astro adapters (#14880)
• See full diff in compare view

Updates astro from 5.16.6 to 5.16.13

Release notes

Sourced from astro's releases.

astro@5.16.13

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 =&gt; res.arrayBuffer()),
  
  
  
  
  
       data: await getFontBuffer(data[0].src[0].url),
      weight: 400,
      style: &quot;normal&quot;,
    },
  ],
  
  },
  )
  // ...
  }

See the experimental Fonts API documentation for more information.

astro@5.16.12

Patch Changes

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

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.13

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 =&gt; res.arrayBuffer()),
  
  
  
  
  
       data: await getFontBuffer(data[0].src[0].url),
      weight: 400,
      style: &quot;normal&quot;,
    },
  ],
  
  },
  )
  // ...
  }

See the experimental Fonts API documentation for more information.

5.16.12

Patch Changes

... (truncated)

Commits

• ce0c346 [ci] release (#15270)
• 60d1045 clear fonts test cache (#15274)
• c4a15a8 [ci] format
• cb60ee1 feat(fonts): getFontBuffer() (#15182)
• d14dfc2 Add a --db-app-token flag to "astro db" execute, push, and verify commands (#...
• dc5bcd9 [ci] release (#15228)
• 47ae148 feat(fonts)!: family options (#15175)
• c0595b3 feat(fonts)!: fontData instead of getFontData() (#15200)
• 096c331 fix: typo in comment (#15232)
• 2a6315a React / MDX nested regression (#15253)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions