chore(deps): update astro to 5.1.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
astro (source)	4.16.18 -> 5.1.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

withastro/astro (astro)

v5.1.1

Compare Source

Patch Changes

• #​12782 f3d8385 Thanks @​fhiromasa! - update comment in packages/astro/src/types/public/common.ts

• #​12789 f632b94 Thanks @​ascorbic! - Pass raw frontmatter to remark plugins in glob loader

• #​12799 739dbfb Thanks @​ascorbic! - Upgrades Vite to pin esbuild

v5.1.0

Compare Source

Minor Changes

• #​12441 b4fec3c Thanks @​ascorbic! - Adds experimental session support

  Sessions are used to store user state between requests for server-rendered pages, such as login status, shopping cart contents, or other user-specific data.

v5.0.9

Compare Source

Patch Changes

• #​12756 95795f8 Thanks @​matthewp! - Remove debug logging from build

v5.0.8

Compare Source

Patch Changes

• #​12749 039d022 Thanks @​matthewp! - Clean server sourcemaps from static output

v5.0.7

Compare Source

Patch Changes

• #​12746 c879f50 Thanks @​matthewp! - Remove all assets created from the server build

v5.0.6

Compare Source

Patch Changes

• #​12597 564ac6c Thanks @​florian-lefebvre! - Fixes an issue where image and server islands routes would not be passed to the astro:routes:resolved hook during builds

• #​12718 ccc5ad1 Thanks @​ematipico! - Fixes an issue where Astro couldn't correctly handle i18n fallback when using the i18n middleware

• #​12728 ee66a45 Thanks @​argyleink! - Adds type support for the closedby attribute for <dialog> elements

• #​12709 e3bfd93 Thanks @​mtwilliams-code! - Fixes a bug where Astro couldn't correctly parse params and props when receiving i18n fallback URLs

• #​12657 14dffcc Thanks @​darkmaga! - Trailing slash support for actions

• #​12715 029661d Thanks @​ascorbic! - Fixes a bug that caused errors in dev when editing sites with large numbers of MDX pages

• #​12729 8b1cecd Thanks @​JoeMorgan! - "Added inert to htmlBooleanAttributes"

• #​12726 7c7398c Thanks @​florian-lefebvre! - Fixes a case where failing content entries in astro check would not be surfaced

v5.0.5

Compare Source

Patch Changes

• #​12705 0d1eab5 Thanks @​ascorbic! - Fixes a bug where MDX files with certain characters in the name would cause builds to fail

• #​12707 2aaed2d Thanks @​ematipico! - Fixes a bug where the middleware was incorrectly imported during the build

• #​12697 1c4a032 Thanks @​ascorbic! - Fix a bug that caused builds to fail if an image had a quote mark in its name

• #​12694 495f46b Thanks @​ematipico! - Fixes a bug where the experimental feature experimental.svg was incorrectly used when generating ESM images

• #​12658 3169593 Thanks @​jurajkapsz! - Fixes astro info copy to clipboard process not returning to prompt in certain cases.

• #​12712 b01c74a Thanks @​ascorbic! - Fixes a bug which misidentified pages as markdown if a query string ended in a markdown extension

v5.0.4

Compare Source

Patch Changes

• #​12653 e21c7e6 Thanks @​sarah11918! - Updates a reference in an error message

• #​12585 a9373c0 Thanks @​florian-lefebvre! - Fixes a case where process.env would be frozen despite changes made to environment variables in development

• #​12695 a203d5d Thanks @​ascorbic! - Throws a more helpful error when images are missing

• Updated dependencies [f13417b, 87231b1, a71e9b9]:

  • @​astrojs/markdown-remark@​6.0.1

v5.0.3

Compare Source

Patch Changes

• #​12645 8704c54 Thanks @​sarah11918! - Updates some reference links in error messages for new v5 docs.

• #​12641 48ca399 Thanks @​ascorbic! - Fixes a bug where astro info --copy wasn't working correctly on macOS systems.

• #​12461 62939ad Thanks @​kyr0! - Removes the misleading log message telling that a custom renderer is not recognized while it clearly is and works.

• #​12642 ff18b9c Thanks @​ematipico! - Provides more information when logging a warning for accessing Astro.request.headers in prerendered pages

• #​12634 03958d9 Thanks @​delucis! - Improves error message formatting for user config and content collection frontmatter

• #​12547 6b6e18d Thanks @​mtwilliams-code! - Fixes a bug where URL search parameters weren't passed when using the i18n fallback feature.

• #​12449 e6b8017 Thanks @​apatel369! - Fixes an issue where the custom assetFileNames configuration caused assets to be incorrectly moved to the server directory instead of the client directory, resulting in 404 errors when accessed from the client side.

• #​12518 e216250 Thanks @​ematipico! - Fixes an issue where SSR error pages would return duplicated custom headers.

• #​12625 74bfad0 Thanks @​ematipico! - Fixes an issue where the experimental.svg had incorrect type, resulting in some errors in the editors.

• #​12631 dec0305 Thanks @​ascorbic! - Fixes a bug where the class attribute was rendered twice on the image component

• #​12623 0e4fecb Thanks @​ascorbic! - Correctly handles images in content collections with uppercase file extensions

• #​12633 8a551c1 Thanks @​bluwy! - Cleans up content layer sync during builds and programmatic sync() calls

• #​12640 22e405a Thanks @​ascorbic! - Fixes a bug that caused content collections to be returned empty when run in a test environment

• #​12613 306c9f9 Thanks @​matthewp! - Fix use of cloned requests in middleware with clientAddress

  When using context.clientAddress or Astro.clientAddress Astro looks up the address in a hidden property. Cloning a request can cause this hidden property to be lost.

  The fix is to pass the address as an internal property instead, decoupling it from the request.

v5.0.2

Compare Source

Patch Changes

• #​12601 0724929 Thanks @​ascorbic! - Includes "undefined" in types for getEntry

v5.0.1

Compare Source

Patch Changes

• #​12590 92c269b Thanks @​kidonng! - fix: devtools warnings about dev toolbar form fields

v5.0.0

Compare Source

Major Changes

• #​11798 e9e2139 Thanks @​matthewp! - Unflag globalRoutePriority

  The previously experimental feature globalRoutePriority is now the default in Astro 5.

  This was a refactoring of route prioritization in Astro, making it so that injected routes, file-based routes, and redirects are all prioritized using the same logic. This feature has been enabled for all Starlight projects since it was added and should not affect most users.

• #​11864 ee38b3a Thanks @​ematipico! - ### [changed]: entryPoint type inside the hook astro:build:ssr
  In Astro v4.x, the entryPoint type was RouteData.

  Astro v5.0 the entryPoint type is IntegrationRouteData, which contains a subset of the RouteData type. The fields isIndex and fallbackRoutes were removed.

What should I do?

Update your adapter to change the type of entryPoint from RouteData to IntegrationRouteData.

-import type {RouteData} from 'astro';
+import type {IntegrationRouteData} from "astro"

-function useRoute(route: RouteData) {
+function useRoute(route: IntegrationRouteData) {

}

• #​12524 9f44019 Thanks @​bluwy! - Bumps Vite to ^6.0.1 and handles its breaking changes

• #​10742 b6fbdaa Thanks @​ematipico! - The lowest version of Node supported by Astro is now Node v18.17.1 and higher.

• #​11916 46ea29f Thanks @​bluwy! - Updates how the build.client and build.server option values get resolved to match existing documentation. With this fix, the option values will now correctly resolve relative to the outDir option. So if outDir is set to ./dist/nested/, then by default:

  • build.client will resolve to <root>/dist/nested/client/
  • build.server will resolve to <root>/dist/nested/server/

  Previously the values were incorrectly resolved:

  • build.client was resolved to <root>/dist/nested/dist/client/
  • build.server was resolved to <root>/dist/nested/dist/server/

  If you were relying on the previous build paths, make sure that your project code is updated to the new build paths.

• #​11982 d84e444 Thanks @​Princesseuh! - Adds a default exclude and include value to the tsconfig presets. {projectDir}/dist is now excluded by default, and {projectDir}/.astro/types.d.ts and {projectDir}/**/* are included by default.

  Both of these options can be overridden by setting your own values to the corresponding settings in your tsconfig.json file.

• #​11861 3ab3b4e Thanks @​bluwy! - Cleans up Astro-specfic metadata attached to vfile.data in Remark and Rehype plugins. Previously, the metadata was attached in different locations with inconsistent names. The metadata is now renamed as below:

  • vfile.data.__astroHeadings -> vfile.data.astro.headings
  • vfile.data.imagePaths -> vfile.data.astro.imagePaths

  The types of imagePaths has also been updated from Set<string> to string[]. The vfile.data.astro.frontmatter metadata is left unchanged.

  While we don't consider these APIs public, they can be accessed by Remark and Rehype plugins that want to re-use Astro's metadata. If you are using these APIs, make sure to access them in the new locations.

• #​11987 bf90a53 Thanks @​florian-lefebvre! - The locals object can no longer be overridden

  Middleware, API endpoints, and pages can no longer override the locals object in its entirety. You can still append values onto the object, but you can not replace the entire object and delete its existing values.

  If you were previously overwriting like so:

  ctx.locals = {
    one: 1,
    two: 2,
  };

  This can be changed to an assignment on the existing object instead:

  Object.assign(ctx.locals, {
    one: 1,
    two: 2,
  });

• #​11908 518433e Thanks @​Princesseuh! - The image.endpoint config now allow customizing the route of the image endpoint in addition to the entrypoint. This can be useful in niche situations where the default route /_image conflicts with an existing route or your local server setup.

  import { defineConfig } from 'astro/config';
  
  defineConfig({
    image: {
      endpoint: {
        route: '/image',
        entrypoint: './src/image_endpoint.ts',
      },
    },
  });

• #​12008 5608338 Thanks @​Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

  Starting from this release, no breaking changes will be introduced unless absolutely necessary.

  To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

• #​11679 ea71b90 Thanks @​florian-lefebvre! - The astro:env feature introduced behind a flag in v4.10.0 is no longer experimental and is available for general use. If you have been waiting for stabilization before using astro:env, you can now do so.

  This feature lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client.

  To configure a schema, add the env option to your Astro config and define your client and server variables. If you were previously using this feature, please remove the experimental flag from your Astro config and move your entire env configuration unchanged to a top-level option.

  import { defineConfig, envField } from 'astro/config';
  
  export default defineConfig({
    env: {
      schema: {
        API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
        PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
        API_SECRET: envField.string({ context: 'server', access: 'secret' }),
      },
    },
  });

  You can import and use your defined variables from the appropriate /client or /server module:

---

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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @astrojs/[email protected]
npm warn Found: [email protected]
npm warn node_modules/astro
npm warn   astro@"5.1.1" from the root project
npm warn   2 more (astro-expressive-code, starlight-links-validator)
npm warn
npm warn Could not resolve dependency:
npm warn peer astro@"^4.8.0" from @astrojs/[email protected]
npm warn node_modules/@astrojs/mdx
npm warn   @astrojs/mdx@"^3.1.3" from @astrojs/[email protected]
npm warn   node_modules/@astrojs/starlight
npm warn   1 more (starlight-blog)
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/astro
npm warn   peer astro@"^4.8.0" from @astrojs/[email protected]
npm warn   node_modules/@astrojs/mdx
npm warn     @astrojs/mdx@"^3.1.3" from @astrojs/[email protected]
npm warn     node_modules/@astrojs/starlight
npm warn     1 more (starlight-blog)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @astrojs/[email protected]
npm error Found: [email protected]
npm error node_modules/astro
npm error   astro@"5.1.1" from the root project
npm error   peer astro@"^4.0.0-beta || ^5.0.0-beta || ^3.3.0" from [email protected]
npm error   node_modules/astro-expressive-code
npm error     astro-expressive-code@"^0.38.3" from @astrojs/[email protected]
npm error     node_modules/@astrojs/starlight
npm error       @astrojs/starlight@"0.29.3" from the root project
npm error       2 more (starlight-blog, starlight-links-validator)
npm error   1 more (starlight-links-validator)
npm error
npm error Could not resolve dependency:
npm error peer astro@"^4.14.0" from @astrojs/[email protected]
npm error node_modules/@astrojs/starlight
npm error   @astrojs/starlight@"0.29.3" from the root project
npm error   peer @astrojs/starlight@">=0.28.3" from [email protected]
npm error   node_modules/starlight-blog
npm error     starlight-blog@"0.15.0" from the root project
npm error   1 more (starlight-links-validator)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/astro
npm error   peer astro@"^4.14.0" from @astrojs/[email protected]
npm error   node_modules/@astrojs/starlight
npm error     @astrojs/starlight@"0.29.3" from the root project
npm error     peer @astrojs/starlight@">=0.28.3" from [email protected]
npm error     node_modules/starlight-blog
npm error       starlight-blog@"0.15.0" from the root project
npm error     1 more (starlight-links-validator)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-20T13_58_56_437Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-20T13_58_56_437Z-debug-0.log