chore(deps): update astro monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/svelte (source)	7.0.4 -> 7.0.5
@astrojs/vue (source)	5.0.6 -> 5.0.7
astro (source)	5.3.0 -> 5.4.1

---

Release Notes

withastro/astro (@​astrojs/svelte)

v7.0.5

Compare Source

Patch Changes

• #​13323 80926fa Thanks @​ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

withastro/astro (@​astrojs/vue)

v5.0.7

Compare Source

Patch Changes

• #​13251 3842ce5 Thanks @​florian-lefebvre! - Fixes a case where the compiler could not be resolved automatically

withastro/astro (astro)

v5.4.1

Compare Source

Patch Changes

• #​13336 8f632ef Thanks @​ematipico! - Fixes a regression where some asset utilities were move across monorepo, and not re-exported anymore.

• #​13320 b5dabe9 Thanks @​{! - Adds support for typing experimental session data

  You can add optional types to your session data by creating a src/env.d.ts file in your project that extends the global App.SessionData interface. For example:

  declare namespace App {
    interface SessionData {
  
        id: string;
        email: string;
      };
      lastLogin: Date;
    }
  }

  Any keys not defined in this interface will be treated as any.

  Then when you access Astro.session in your components, any defined keys will be typed correctly:

v5.4.0

Compare Source

Minor Changes

• #​12052 5be12b2 Thanks @​Fryuni! - Exposes extra APIs for scripting and testing.

Config helpers

Two new helper functions exported from astro/config:

• mergeConfig() allows users to merge partially defined Astro configurations on top of a base config while following the merge rules of updateConfig() available for integrations.
• validateConfig() allows users to validate that a given value is a valid Astro configuration and fills in default values as necessary.

These helpers are particularly useful for integration authors and for developers writing scripts that need to manipulate Astro configurations programmatically.

Programmatic build

The build API now receives a second optional BuildOptions argument where users can specify:

• devOutput (default false): output a development-based build similar to code transformed in astro dev.
• teardownCompiler (default true): teardown the compiler WASM instance after build.

These options provide more control when running Astro builds programmatically, especially for testing scenarios or custom build pipelines.

• #​13278 4a43c4b Thanks @​ematipico! - Adds a new configuration option server.allowedHosts and CLI option --allowed-hosts.

  Now you can specify the hostnames that the dev and preview servers are allowed to respond to. This is useful for allowing additional subdomains, or running the dev server in a web container.

  allowedHosts checks the Host header on HTTP requests from browsers and if it doesn't match, it will reject the request to prevent CSRF and XSS attacks.

  astro dev --allowed-hosts=foo.bar.example.com,bar.example.com

  astro preview --allowed-hosts=foo.bar.example.com,bar.example.com

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  
  export default defineConfig({
    server: {
      allowedHosts: ['foo.bar.example.com', 'bar.example.com'],
    },
  });

  This feature is the same as Vite's server.allowHosts configuration.

• #​13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown files

  Previously, Astro only allowed local images to be optimized when included using ![]() syntax in plain Markdown files. Astro's image service could only display remote images without any processing.

  Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

  No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the HTML <img> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

• #​13256 509fa67 Thanks @​p0lyw0lf! - Adds experimental responsive image support in Markdown

  Previously, the experimental.responsiveImages feature could only provide responsive images when using the <Image /> and <Picture /> components.

  Now, images written with the ![]() Markdown syntax in Markdown and MDX files will generate responsive images by default when using this experimental feature.

  To try this experimental feature, set experimental.responsiveImages to true in your astro.config.mjs file:

  {
     experimental: {
        responsiveImages: true,
     },
  }

  Learn more about using this feature in the experimental responsive images feature reference.

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

• #​13323 80926fa Thanks @​ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

• #​13313 9e7c71d Thanks @​martrapp! - Fixes an issue where a form field named "attributes" shadows the form.attributes property.

• #​12052 5be12b2 Thanks @​Fryuni! - Fixes incorrect config update when calling updateConfig from astro:build:setup hook.

  The function previously called a custom update config function made for merging an Astro config. Now it calls the appropriate mergeConfig() utility exported by Vite that updates functional options correctly.

• #​13303 5f72a58 Thanks @​ematipico! - Fixes an issue where the dev server was applying second decoding of the URL of the incoming request, causing issues for certain URLs.

• Updated dependencies [1e11f5e, 1e11f5e]:

  • @​astrojs/internal-helpers@​0.6.0
  • @​astrojs/markdown-remark@​6.2.0

v5.3.1

Compare Source

Patch Changes

• #​13233 32fafeb Thanks @​joshmkennedy! - Ensures consistent behaviour of Astro.rewrite/ctx.rewrite when using base and trailingSlash options.

• #​13003 ea79054 Thanks @​chaegumi! - Fixes a bug that caused the vite.base value to be ignored when running astro dev

• #​13299 2e1321e Thanks @​bluwy! - Uses tinyglobby for globbing files

• #​13233 32fafeb Thanks @​joshmkennedy! - Ensures that Astro.url/ctx.url is correctly updated with the base path after rewrites.

  This change fixes an issue where Astro.url/ctx.url did not include the configured base path after Astro.rewrite was called. Now, the base path is correctly reflected in Astro.url.

  Previously, any rewrites performed through Astro.rewrite/ctx.rewrite failed to append the base path to Astro.url/ctx.rewrite, which could lead to incorrect URL handling in downstream logic. By fixing this, we ensure that all routes remain consistent and predictable after a rewrite.

  If you were relying on the work around of including the base path in astro.rewrite you can now remove it from the path.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.