fix(deps): update astro monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/mdx (source)	4.0.7 -> 4.0.8
astro (source)	5.1.10 -> 5.2.5

---

Release Notes

withastro/astro (@​astrojs/mdx)

v4.0.8

Compare Source

Patch Changes

• Updated dependencies [db252e0]:
  • @​astrojs/markdown-remark@​6.1.0

withastro/astro (astro)

v5.2.5

Compare Source

Patch Changes

• #​13133 e76aa83 Thanks @​ematipico! - Fixes a bug where Astro was failing to build an external redirect when the middleware was triggered

• #​13119 ac43580 Thanks @​Hacksore! - Adds extra guidance in the terminal when using the astro add tailwind CLI command

  Now, users are given a friendly reminder to import the stylesheet containing their Tailwind classes into any pages where they want to use Tailwind. Commonly, this is a shared layout component so that Tailwind styling can be used on multiple pages.

v5.2.4

Compare Source

Patch Changes

• #​13130 b71bd10 Thanks @​ascorbic! - Fixes a bug that caused duplicate slashes inside query params to be collapsed

• #​13131 d60c742 Thanks @​ascorbic! - Ignores trailing slashes for endpoints with file extensions in the route

• Updated dependencies [b71bd10]:

  • @​astrojs/internal-helpers@​0.5.1

v5.2.3

Compare Source

Patch Changes

• #​13113 3a26e45 Thanks @​unprintable123! - Fixes the bug that rewrite will pass encoded url to the dynamic routing and cause params mismatch.

• #​13111 23978dd Thanks @​ascorbic! - Fixes a bug that caused injected endpoint routes to return not found when trailingSlash was set to always

• #​13112 0fa5c82 Thanks @​ematipico! - Fixes a bug where the i18n middleware was blocking a server island request when the prefixDefaultLocale option is set to true

v5.2.2

Compare Source

Patch Changes

• #​13106 187c4d3 Thanks @​ascorbic! - Fixes a bug that caused peer dependency errors when running astro add tailwind

v5.2.1

Compare Source

Patch Changes

• #​13095 740eb60 Thanks @​ascorbic! - Fixes a bug that caused some dev server asset requests to return 404 when trailingSlash was set to "always"

v5.2.0

Compare Source

Minor Changes

• #​12994 5361755 Thanks @​ascorbic! - Redirects trailing slashes for on-demand pages

  When the trailingSlash option is set to always or never, on-demand rendered pages will now redirect to the correct URL when the trailing slash doesn't match the configuration option. This was previously the case for static pages, but now works for on-demand pages as well.

  Now, it doesn't matter whether your visitor navigates to /about/, /about, or even /about///. In production, they'll always end up on the correct page. For GET requests, the redirect will be a 301 (permanent) redirect, and for all other request methods, it will be a 308 (permanent, and preserve the request method) redirect.

  In development, you'll see a helpful 404 page to alert you of a trailing slash mismatch so you can troubleshoot routes.

• #​12979 e621712 Thanks @​ematipico! - Adds support for redirecting to external sites with the redirects configuration option.

  Now, you can redirect routes either internally to another path or externally by providing a URL beginning with http or https:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  
  export default defineConfig({
    redirects: {
      '/blog': 'https://example.com/blog',
      '/news': {
        status: 302,
        destination: 'https://example.com/news',
      },
    },
  });

• #​13084 0f3be31 Thanks @​ematipico! - Adds a new experimental virtual module astro:config that exposes a type-safe subset of your astro.config.mjs configuration

  The virtual module exposes two sub-paths for 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/dir paths.

  To enable this new virtual module, add the experimental.serializeManifest feature flag to your Astro config:

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

  Then, you can access the module in any file inside your project to import and use 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;
    }
  }

  For a complete overview, and to give feedback on this experimental API, see the Serialized Manifest RFC.

Patch Changes

• #​13049 2ed4bd9 Thanks @​florian-lefebvre! - Updates astro add tailwind to add the @tailwindcss/vite plugin instead of the @astrojs/tailwind integration

• #​12994 5361755 Thanks @​ascorbic! - Returns a more helpful 404 page in dev if there is a trailing slash mismatch between the route requested and the trailingSlash configuration

• #​12666 037495d Thanks @​Thodor12! - Added additional generated typings for the content layer

• Updated dependencies [5361755, db252e0]:

  • @​astrojs/internal-helpers@​0.5.0
  • @​astrojs/markdown-remark@​6.1.0

---

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.

👻 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.