fix(deps): update astrojs packages

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/mdx (source)	1.1.3 -> 1.1.4
astro (source)	3.4.4 -> 3.5.3

---

Release Notes

withastro/astro (@​astrojs/mdx)

v1.1.4

Compare Source

Patch Changes

• Updated dependencies [c5010aad3]:
  • @​astrojs/markdown-remark@​3.4.0

withastro/astro (astro)

v3.5.3

Compare Source

Patch Changes

• #​9069 50164f5e3 Thanks @​natemoo-re! - Fix a regression introduced in 3.5.0 related to content collection styles

v3.5.2

Compare Source

Patch Changes

• #​9057 1bc331968 Thanks @​ematipico! - Correctly infer the presence of an user middleware

v3.5.1

Compare Source

Patch Changes

• #​9037 ea71975ec Thanks @​sarah11918! - Updates i18n configuration reference

• #​9051 15b84ccb9 Thanks @​ematipico! - Fix a regression where endpoints were incorrectly processed during SSG build when trailingSlash: "always"

• #​9042 7dedd17fc Thanks @​rishi-raj-jain! - Safely bail when the xclip command does not exist on Linux when trying to copy to clipboard with astro info

• #​9050 bf0286e50 Thanks @​Princesseuh! - Fix --verbose flag not working

• #​9049 49b82edb2 Thanks @​Princesseuh! - Fix image errors when images were used on the client

v3.5.0

Compare Source

Minor Changes

• #​8869 f5bdfa272 Thanks @​matthewp! - ## Integration Hooks to add Middleware

  It's now possible in Astro for an integration to add middleware on behalf of the user. Previously when a third party wanted to provide middleware, the user would need to create a src/middleware.ts file themselves. Now, adding third-party middleware is as easy as adding a new integration.

  For integration authors, there is a new addMiddleware function in the astro:config:setup hook. This function allows you to specify a middleware module and the order in which it should be applied:

  // my-package/middleware.js
  import { defineMiddleware } from 'astro:middleware';
  
  export const onRequest = defineMiddleware(async (context, next) => {
    const response = await next();
  
    if (response.headers.get('content-type') === 'text/html') {
      let html = await response.text();
      html = minify(html);
      return new Response(html, {
        status: response.status,
        headers: response.headers,
      });
    }
  
    return response;
  });

  You can now add your integration's middleware and specify that it runs either before or after the application's own defined middleware (defined in src/middleware.{js,ts})

  // my-package/integration.js
  export function myIntegration() {
    return {
      name: 'my-integration',
      hooks: {
        'astro:config:setup': ({ addMiddleware }) => {
          addMiddleware({
            entrypoint: 'my-package/middleware',
            order: 'pre',
          });
        },
      },
    };
  }

• #​8854 3e1239e42 Thanks @​natemoo-re! - Provides a new, experimental build cache for Content Collections as part of the Incremental Build RFC. This includes multiple refactors to Astro's build process to optimize how Content Collections are handled, which should provide significant performance improvements for users with many collections.

  Users building a static site can opt-in to preview the new build cache by adding the following flag to your Astro config:

  // astro.config.mjs
  export default {
    experimental: {
      contentCollectionCache: true,
    },
  };

  When this experimental feature is enabled, the files generated from your content collections will be stored in the cacheDir (by default, node_modules/.astro) and reused between builds. Most CI environments automatically restore files in node_modules/ by default.

  In our internal testing on the real world Astro Docs project, this feature reduces the bundling step of astro build from 133.20s to 10.46s, about 92% faster. The end-to-end astro build process used to take 4min 58s and now takes just over 1min for a total reduction of 80%.

  If you run into any issues with this experimental feature, please let us know!

  You can always bypass the cache for a single build by passing the --force flag to astro build.

  astro build --force
  

• #​8963 fda3a0213 Thanks @​matthewp! - Form support in View Transitions router

  The <ViewTransitions /> router can now handle form submissions, allowing the same animated transitions and stateful UI retention on form posts that are already available on <a> links. With this addition, your Astro project can have animations in all of these scenarios:

  • Clicking links between pages.
  • Making stateful changes in forms (e.g. updating site preferences).
  • Manually triggering navigation via the navigate() API.

  This feature is opt-in for semver reasons and can be enabled by adding the handleForms prop to the ` component:

---

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 has been generated by Mend Renovate. View repository job log here.