Description

• With this PR all types of badges will be shown directly in the docs which is important to help people chose the right one for their use case.
• The current status quo is less verbose. But it puts the work on the reader to try out every badge type to see and test it. That is cumbersome, takes time and unnecessary.
• The visual appeal of the badges should be visible directly.

Deeplink: https://deploy-preview-2881--astro-starlight.netlify.app/guides/sidebar/#badge-variants-and-custom-styling

Changes

• Currently, experimental.responsiveImages only adds CSS variables to images included via the <Image /> or <Picture /> components.
• In my other PR #13254, we can only use getImage to transform images.
• I would like to have getImage participate more fully in the responsive images experiment.
• Moving the CSS variable logic inside getImage removes a lot of redundant/confusing logic anyways.

Testing

I tested this change by running my personal blog with it on. It provides a better outcome than when getImage is used on its own with this experiment turned on:

Note: the before pic has width: 100% applied to it in page styles. Without that, it looks even worse (no scaling applied based on page size)

Docs

We may need to update the doc page on this (https://docs.astro.build/en/reference/experimental-flags/responsive-images/), as well as the RFC (https://github.com/withastro/roadmap/blob/eff726cec3bf214b42ab13b819ed7b200753509e/proposals/0053-responsive-images.md). Currently, neither make mention of getImage being affected by this experiment.

/cc @withastro/maintainers-docs for feedback!

Changes

• Currently, in Markdown files, only local images get passed to the image service
  • This was because the image service only supported local files when it was first released.
• However, the image service now supports remote images
• So, this PR adds support for passing remote images in Markdown files to the image service.

Testing

I tested this change by creating a small project with a single allowed remote domain, and rendering markdown files from:

• a page
• a content collection

Both approaches work. I can provide these test files if needed, though I'm not sure how we'll want to deal with the fact it'll require an internet connection.

Known Issues

If the remote image is styled in some way, the newly added width and height attributes could mess up that styling. Ideally, we'd like to be able to modify the properties after getImage runs somehow, but seeing as this is also the case for local images transformed using this method too, I think this is more a deficiency in getImage best left addressed by the responsive image experiment.

Docs

If this change goes through, we will need to update this page to reflect that remote images are now supported in markdown files: https://docs.astro.build/en/guides/images/#images-in-markdown-files

/cc @withastro/maintainers-docs for feedback!

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! pnpm exec changeset

Testing

Docs

Changes

• Closes #12969

Testing

N/A

Docs

N/A

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! pnpm exec changeset

Testing

Docs

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! pnpm exec changeset

Testing

Docs

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! pnpm exec changeset

Testing

Docs

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/vue@5.0.7

Patch Changes

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

Changes

A test is failing because it asserted a message that we recently changed

Testing

Test should pass (checked locally, it passed)

Docs

N/A

This PR fixes #13033

Changes

After the rewrite, the URL will contain the base path and then the new pathname.

The other issue that was brought up was inconsistencies with trailingSlash and when the base was included in the Astro.rewrite call.

Testing

I have added a new fixture and have added tests to the /tests/rewrite.test.js file that test and ensure the Astro.url pathname always contains the base path. This is tested both with and without the trailingSlash, also with the base being included and excluded in argument of Astro.rewrite.

Docs

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.3.0

Minor Changes

• #13210 344e9bc Thanks @VitaliyR! - Handle HEAD requests to an endpoint when a handler is not defined.

  If an endpoint defines a handler for GET, but does not define a handler for HEAD, Astro will call the GET handler and return the headers and status but an empty body.

• #13195 3b66955 Thanks @MatthewLymer! - Improves SSR performance for synchronous components by avoiding the use of Promises. With this change, SSR rendering of on-demand pages can be up to 4x faster.

• #13145 8d4e566 Thanks @ascorbic! - Adds support for adapters auto-configuring experimental session storage drivers.

  Adapters can now configure a default session storage driver when the experimental.session flag is enabled. If a hosting platform has a storage primitive that can be used for session storage, the adapter can automatically configure the session storage using that driver. This allows Astro to provide a more seamless experience for users who want to use sessions without needing to manually configure the session storage.

Patch Changes

• #13145 8d4e566 Thanks @ascorbic! - ⚠️ BREAKING CHANGE FOR EXPERIMENTAL SESSIONS ONLY ⚠️

  Changes the experimental.session option to a boolean flag and moves session config to a top-level value. This change is to allow the new automatic session driver support. You now need to separately enable the experimental.session flag, and then configure the session driver using the top-level session key if providing manual configuration.

  defineConfig({
    // ...
    experimental: {
  -    session: {
  -      driver: 'upstash',
  -    },
  +    session: true,
    },
  +  session: {
  +    driver: 'upstash',
  +  },
  });

  You no longer need to configure a session driver if you are using an adapter that supports automatic session driver configuration and wish to use its default settings.

  defineConfig({
    adapter: node({
      mode: "standalone",
    }),
    experimental: {
  -    session: {
  -      driver: 'fs',
  -      cookie: 'astro-cookie',
  -    },
  +    session: true,
    },
  +  session: {
  +    cookie: 'astro-cookie',
  +  },
  });

  However, you can still manually configure additional driver options or choose a non-default driver to use with your adapter with the new top-level session config option. For more information, see the experimental session docs.

• #13101 2ed67d5 Thanks @corneliusroemer! - Fixes a bug where HEAD and OPTIONS requests for non-prerendered pages were incorrectly rejected with 403 FORBIDDEN

@astrojs/netlify@6.2.0

Minor Changes

• #13194 1b5037b Thanks @dfdez! - Adds includedFiles and excludedFiles configuration options to customize SSR function bundle contents.

  The includeFiles property allows you to explicitly specify additional files that should be bundled with your function. This is useful for files that aren't automatically detected as dependencies, such as:

  • Data files loaded using fs operations
  • Configuration files
  • Template files

  Similarly, you can use the excludeFiles property to prevent specific files from being bundled that would otherwise be included. This is helpful for:

  • Reducing bundle size
  • Excluding large binaries
  • Preventing unwanted files from being deployed

  import { defineConfig } from 'astro/config';
  import netlify from '@astrojs/netlify';
  
  export default defineConfig({
    // ...
    output: 'server',
    adapter: netlify({
      includeFiles: ['./my-data.json'],
      excludeFiles: ['./node_modules/package/**/*', './src/**/*.test.js'],
    }),
  });

  See the Netlify adapter documentation for detailed usage instructions and examples.

• #13145 8d4e566 Thanks @ascorbic! - Automatically configures Netlify Blobs storage when experimental session enabled

  If the experimental.session flag is enabled when using the Netlify adapter, Astro will automatically configure the session storage using the Netlify Blobs driver. You can still manually configure the session storage if you need to use a different driver or want to customize the session storage configuration.

  See the experimental session docs for more information on configuring session storage.

Patch Changes

• Updated dependencies []:
  • @astrojs/underscore-redirects@0.6.0

@astrojs/node@9.1.0

Minor Changes

• #13145 8d4e566 Thanks @ascorbic! - Automatically configures filesystem storage when experimental session enabled

  If the experimental.session flag is enabled when using the Node adapter, Astro will automatically configure session storage using the filesystem driver. You can still manually configure session storage if you need to use a different driver or want to customize the session storage configuration.

  See the experimental session docs for more information on configuring session storage.

Changes

I probably botched the multiple line command, so now I put it one line

Testing

Merge and trigger

Docs

N/A

Changes

The checkout step was missing lol

Testing

Docs

Changes

As for now, I want to hardcode the packages. We can iterate about filter once we have pkg.pr.new working.

Testing

Merge and trigger it

Docs

N/A

Changes

When handling redirects for trailing slashes, we need to skip assets. We do this by checking for a file extension. Previously the Node adapter was using its own regex for this when serving static files, and was missing some edge cases. This PR changes it to use the shared hasFileExtension helper.

Fixes #13222

Testing

Adds test cases

Docs

Changes

This PR updates the pkg.pr.new to use the same workflow steps used by the previous workflow to "trick" changesets to use the correct ref.

Testing

I copied the same code. IT should work. We should merge the PR and trigger another the workflow again.

Docs

N/A

Changes

• What does this change?
• Be short and concise. Bullet points can help!
• Before/after screenshots can help as well.
• Don't forget a changeset! pnpm exec changeset

Testing

Docs

Changes

This PR revamps the pkg.pr.new that we had disabled.

Changes:

• triggers the job only on labeled event
• uses changeset status to retrieve the upcoming releases
• uses a script to parse the JSON emitted by the previous step, and return a list of packages that have changesets. It returns a string
• if the previous string is empty, we write a message in the PR saying that no preview release was published
• if the previous string isn't empty, it's passed to the pkg pr new CLI

Testing

I tested the script locally.
This PR needs to be merged, I will enable the job again, and then open a PR to test it.

Docs

N/A

Changes

This PR removes a workflow that isn't needed anymore

Testing

N/A

Docs

N/A

Changes

Resolves this issue #13196

The paginate function allows for readonly arrays.

Testing

Just types were changed.

Docs

Just types were added

Changes

This pull request is an attempt to solve #13192

Changes the output log statement to log the output and not the buildOutput.
I have added an additional log to show if an adapter is setup for ssr, which is what I believe was the intent of this log line being changed in commit fix(core): add error log for server islands.

-		this.logger.info('build', `output: ${blue('"' + this.settings.config.output + '"')}`);
+		this.logger.info('build', `output: ${blue('"' + this.settings.buildOutput + '"')}`);

Testing

No tests were added as the only changes are to log statements

Docs

Changes

There are 2 main changes in this PR:

1. It is now possible to define ISR exclusions as regular expressions.
2. Routes excluded from ISR do not get _isr route entry in .vercel/output/config.json.

Longer answer with my reasoning:

I am using Astro at www.superside.com and our website has many different API routes. I found it quite inconvenient to add every single one of them to the isr.exclude list manually. I prefer to have this in my astro.config.mjs instead:

isr: {
  exclude: [/^\/api/]
}

We've been using this change via patched node module on production for quite some time without any issue. However, this complicates the process of upgrading Astro for us. Ideally I would love to see this change merged into the source code.

As for the second change: as I was working on a way to make isr.exclude accept regular expressions, I noticed that generated vercel/output/config.json file has a lot of unnecessary entries in it (our website has a many excluded api routes). This change helped me investigate Vercel build outputs.

Testing

I adjusted existing tests to handle new use cases.

Docs

/cc @withastro/maintainers-docs for feedback!

If you accept this PR it would be necessary to mention support for regular expressions support in this section of the docs:
https://docs.astro.build/en/guides/integrations-guide/vercel/#excluding-paths-from-caching

… implemented

Changes

I've noticed that /_image endpoint doesn't respond nicely (non 404) to HEAD requests. After investigation, I've found that none of server endpoints respond to the HEAD - they respond as 404.

User must explicitly implement export const HEAD to add support for this endpoint or provide export const ALL.

But typically users won't be doing this, since they typically might want just to add some GET handler and thats it. Since HEAD endpoint is useful for various things, for instance, checking if there is a route there but not caring about it's response - this PR adds default HEAD implementation for such cases.

• In case user would implement it explicitly, their implementation works export const HEAD
• If there are no export const GET handler - HEAD won't be auto-provided as well
• If user implemented ALL -> HEAD won't be auto-provided

Testing

1. TDD: Added test cases, tested before & after
2. Run examples/ssr/ via npm run dev:
   2.1. fetch('http://localhost:4321/api/products') -> 200 (API endpoint)
   2.2. fetch('http://localhost:4321/api/products', { method: 'HEAD' }) -> before 404, after 200
   2.3. fetch('http://localhost:4321/products/2', { method: 'HEAD' }) -> before 200, after 200 (Page endpoint, not affected)

Docs

Not sure about if docs should be updated.
Personally I'd expect this to work outside the box.

Changes

• Adds a basic local provider
• Updates the main logic to make things work
• Storage update: unifont has a storage option which is made to work with unstorage (which is already a dependency since sessions were introduced in Astro). Until then, I had a custom storage that matched unstorage API. However, it was too limited (I needed Buffer support for font files) so I switched to a built-in unstorage driver instead of re-inventing the wheel
• URL proxying: this is not new but I have extracted the logic. The idea is that we get font data from a given provider, and this includes urls to services like google. What we do is we collect those urls, hash them and replace the url in the fonts data with a url we control (/_astro/fonts/${hash}). That allows us to cache things efficiently
• Local fonts data generation: I followed what Nuxt does here https://github.com/nuxt/fonts/blob/main/src/providers/local.ts#L93-L106

Testing

Manual

Docs

N/A

Changes

• Re-export relevant providers from unifont

Testing

Docs

Changes

• Renames <Fonts /> to <Font /> to match RFC

Testing

Should still pass

Docs

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@astrojs/compiler (source)	^2.10.3 -> ^2.10.4					dependencies	patch
@astrojs/node (source)	^9.0.2 -> ^9.1.0					dependencies	minor
@astrojs/solid-js (source)	^5.0.2 -> ^5.0.4					dependencies	patch
@astrojs/svelte (source)	^7.0.3 -> ^7.0.4					dependencies	patch
@astrojs/vue (source)	^5.0.4 -> ^5.0.6					dependencies	patch
@cloudflare/workers-types	^4.20250109.0 -> ^4.20250214.0					dependencies	minor
@markdoc/markdoc (source)	^0.4.0 -> ^0.5.1					dependencies	minor
@netlify/blobs	^8.1.0 -> ^8.1.1					dependencies	patch
@netlify/functions	^2.8.0 -> ^2.8.2					dependencies	patch
@tailwindcss/vite (source)	^4.0.3 -> ^4.0.6					dependencies	patch
@vercel/analytics (source)	^1.4.1 -> ^1.5.0					dependencies	minor
@vercel/nft	^0.29.0 -> ^0.29.1					dependencies	patch
CodSpeedHQ/action	v3.2.0 -> v3.3.1					action	minor
async-listen	^3.0.1 -> ^3.1.0					dependencies	minor
eslint (source)	^9.19.0 -> ^9.20.1					devDependencies	minor
globby	^14.0.2 -> ^14.1.0					devDependencies	minor
linkedom	^0.18.7 -> ^0.18.9					devDependencies	patch
miniflare (source)	^3.20241230.1 -> ^3.20250204.1					dependencies	minor
nanoid	^5.0.9 -> ^5.1.0					dependencies	minor
nanostores	^0.11.3 -> ^0.11.4					dependencies	patch
postcss (source)	^8.5.1 -> ^8.5.2					dependencies	patch
postcss-preset-env (source)	^10.1.3 -> ^10.1.4					devDependencies	patch
prettier (source)	^3.4.2 -> ^3.5.1					devDependencies	minor
publint (source)	^0.3.2 -> ^0.3.5					devDependencies	patch
remark-gfm	^4.0.0 -> ^4.0.1					dependencies	patch
rollup (source)	^4.30.1 -> ^4.34.7					devDependencies	patch
rollup (source)	^4.34.2 -> ^4.34.7					devDependencies	patch
sass	^1.83.4 -> ^1.85.0					devDependencies	minor
sass	^1.83.4 -> ^1.85.0					dependencies	minor
svelte (source)	^5.19.7 -> ^5.20.1					devDependencies	minor
svelte (source)	^5.17.4 -> ^5.20.1					dependencies	minor
svelte (source)	^5.19.7 -> ^5.20.1					dependencies	minor
tailwindcss (source)	^4.0.3 -> ^4.0.6					dependencies	patch
tsconfck (source)	^3.1.4 -> ^3.1.5					dependencies	patch
turbo (source)	^2.4.0 -> ^2.4.2					devDependencies	patch
typescript-eslint (source)	^8.23.0 -> ^8.24.0					devDependencies	minor
vite (source)	^6.0.11 -> ^6.1.0					devDependencies	minor
vite (source)	^6.0.11 -> ^6.1.0					dependencies	minor
vite (source)	^6.0.7 -> ^6.1.0					dependencies	minor
vite-plugin-vue-devtools (source)	^7.7.1 -> ^7.7.2					dependencies	patch
wrangler (source)	^3.101.0 -> ^3.109.1					devDependencies	minor
wrangler (source)	^3.101.0 -> ^3.109.1					dependencies	minor
zod (source)	^3.24.1 -> ^3.24.2					dependencies	patch

Release Notes

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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.

Changes

• Adds onerror=redirect to Cloudflare image transform params. This will allow images to continue to work after hitting Cloudflare's free limit. (docs)

I am not positive how this impacts sites that don't have the image service set up at all, since it might then load the original image as opposed to just erroring and loading nothing as it does now. If it still applies when the image service is disabled entirely, and shows the underlying image, it could cause some confusion with users not realizing the service isn't turned on.

Testing

None. It's a hardcoded value, and I more want to introduce the idea to see if this should be a configurable value, or just always applied.

Docs

This might be worth mentioning in the docs. I can make a PR to those once this is decided on.

Should this be a configurable? Currently there aren't configurations to the options, though maybe it could work with the Image to offer it if that is the preferred out.

Changes

Closes #11454

• Improves SSR performance for rendering synchronous components by avoiding the use of Promise.

Testing

• Added unit tests to ~/packages/astro/test/units/render/rendering.test.js
• Integrated into own project to validate performance and ensure correctness

Docs

No docs were added as this is specifically performance related refactoring.

This PR implements the changes previously proposed in withastro/adapters#515, migrated to work within this repository's structure. The core functionality remains the same, with adjustments made to align with this repository.

Changes

When trying Netlify SSR with Astro, I wasn't able to get the included_files option to work. After investigating, I realized that the includeFiles and excludeFiles functionalities, similar to what Vercel provides, were necessary to include additional files during the build process.

In this PR, I have implemented the integration to add these options:

• Added includeFiles and excludeFiles options to the integration, mirroring Vercel's functionality.
  • includeFiles: Allows users to explicitly specify files or directories to be bundled with their function. Useful for avoiding missing files in production.
  • excludeFiles: Enables users to specify files or directories to be excluded from the deployment. Helps minimize bundle size.
• All code for these features has been adapted directly from Vercel's integration for consistency and reliability.

Testing

• Manually tested includeFiles and excludeFiles with various configurations to ensure:
  • Files specified in includeFiles are bundled correctly.
  • Files and directories specified in excludeFiles are omitted as expected.
• Automated tests added to validate edge cases and typical usage scenarios.
• Confirmed the implementation behaves identically to Vercel's integration.

Docs

• Updated astro docs with documentation for includeFiles and excludeFiles on netlify adapter.
• Added links to Vercel's documentation for further reference:
  • includeFiles
  • excludeFiles

Changes

• Astro 5 made changes to the image endpoint config
• This PR makes those structure changes in the node adapter
• For whatever reason, the old state of the config only created issues when built and executed in a docker container

Fixes #13183

Testing

• Tested locally (with some difficulty) by heavily modifying the SSR example and running it locally in a docker container

Docs

• N/A

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.2.6

Patch Changes

• #13188 7bc8256 Thanks @ematipico! - Fixes the wording of the an error message

• #13205 9d56602 Thanks @ematipico! - Fixes and issue where a server island component returns 404 when base is configured in i18n project.

• #13212 fb38840 Thanks @joshmkennedy! - An additional has been added during the build command to add clarity around output and buildOutput.

• #13213 6bac644 Thanks @joshmkennedy! - Allows readonly arrays to be passed to the paginate() function

@astrojs/node@9.0.3

Patch Changes

• #13223 23094a1 Thanks @ascorbic! - Fixes a bug that caused incorrect redirects for static files with numbers in the file extension

@astrojs/vercel@8.0.7

Patch Changes

• #13224 8e5b89c Thanks @ascorbic! - Unpins @vercel/routing-utils dependency as bug has been fixed

Changes

Fixes a typo inside the error message

Testing

CI should stay green

Docs

N/A

Changes

This PR moves the cloudflare adapter in the monorepo.

There was a test failing, which I updated. I left a TODO in cases we need to fix it.

Testing

CI should pass.

Docs

Will create a PR

Changes

This aims to add Route Groups, as known from Next.js and requested here: withastro/roadmap#480

Folder names in (parenthesis) should be excluded from the route structure, but their content should not be.

This can especially be helpful with boilerplates to encapsulate some of the logic.

Testing

Some tests should be added for sure. I had a quick look at packages/astro/test/route-manifest.test.js but they are all commented out.

I did some quick manual testing to check that it works as expected, however can't rule out that there have been major oversights since I didn't dig trough the whole codebase.

Docs

Docs should be added for this, probably a small passage in https://docs.astro.build/en/guides/routing/
As this this should not clash with any existing route logic, this could hopefully be kept rather short

Changes

Automatically configures session storage with the Node and Netlify adapters. If theexperimental.session flag is enabled, the Node adapter will configure fs session storage and Netlify will configure netlify-blobs session storage.

This also changes the experimental.session option to a boolean flag and moves session config to a top-level value. This change is to allow the new automatic session driver support. You now need to separately enable the experimental.session flag, and then configure the session driver using the top-level session key if providing manual configuration.

defineConfig({
  // ...
  experimental: {
-    session: {
-      driver: 'upstash',
-    },
+    session: true,
  },
+  session: {
+    driver: 'upstash',
+  }, 
});

You no longer need to configure a session driver if you are using an adapter that supports automatic session driver configuration and wish to use its default settings.

defineConfig({
  adapter: node({
    mode: "standalone",
  }),
  experimental: {
-    session: {
-      driver: 'fs',
-      cookie: 'astro-cookie',
-    },
+    session: true,
  },
+  session: {
+    cookie: 'astro-cookie',
+  }, 
});

However, you can still manually configure additional driver options or choose a non-default driver to use with your adapter with the new top-level session config option. For more information, see the experimental session docs.

Testing

Added test cases for the Node and Netlify adapters. The Netlify tests use the local mock blobs server.

Docs

Updated the docs for the config options. This adds several new error types, so I have moved session errors into their own section. I will do a separate PR to the docs repo to update the experimental feature page.

Changes

I added the isRedirect field to the Render context. This can help users avoid running middleware on routes that might just be a redirect.

For example, the Arcjet integration fails if run on a redirect because isPrerendered is false, but clientAddress throws if accessed; however, it would be generally recommended not to run Arcjet on a redirect because it'll run on the final endpoint. With this change, we can recommend users skip Arcjet when isRedirect is true.

Testing

I added a test to the redirects fixture that checks a header that is set by the middleware.

Docs

Yep! I'll add this to the Astro docs for Render context if this is something y'all want to include. 🎉

/cc @withastro/maintainers-docs for feedback!

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight-docsearch@0.6.0

Minor Changes

• #2578 f895f75 and #2390 f493361 Thanks @HiDeoo and @delucis!
  ⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.32.0

  Please use the @astrojs/upgrade command to upgrade your project:

  npx @astrojs/upgrade

@astrojs/starlight@0.32.0

Minor Changes

• #2390 f493361 Thanks @delucis! - Moves route data to Astro.locals instead of passing it down via component props

  ⚠️ BREAKING CHANGE:
  Previously, all of Starlight’s templating components, including user or plugin overrides, had access to a data object for the current route via Astro.props.
  This data is now available as Astro.locals.starlightRoute instead.

  To update, refactor any component overrides you have:

  • Remove imports of @astrojs/starlight/props, which is now deprecated.
  • Update code that accesses Astro.props to use Astro.locals.starlightRoute instead.
  • Remove any spreading of {...Astro.props} into child components, which is no longer required.

  In the following example, a custom override for Starlight’s LastUpdated component is updated for the new style:

  ---
  import Default from '@astrojs/starlight/components/LastUpdated.astro';
  - import type { Props } from '@astrojs/starlight/props';
  
  - const { lastUpdated } = Astro.props;
  + const { lastUpdated } = Astro.locals.starlightRoute;
  
  const updatedThisYear = lastUpdated?.getFullYear() === new Date().getFullYear();
  ---
  
  {updatedThisYear && (
  -   <Default {...Astro.props}><slot /></Default>
  +   <Default><slot /></Default>
  )}

  Community Starlight plugins may also need to be manually updated to work with Starlight 0.32. If you encounter any issues, please reach out to the plugin author to see if it is a known issue or if an updated version is being worked on.

• #2578 f895f75 Thanks @HiDeoo! - Deprecates the Starlight plugin setup hook in favor of the new config:setup hook which provides the same functionality.

  ⚠️ BREAKING CHANGE:

  The Starlight plugin setup hook is now deprecated and will be removed in a future release. Please update your plugins to use the new config:setup hook instead.

  export default {
    name: 'plugin-with-translations',
    hooks: {
  -   'setup'({ config }) {
  +   'config:setup'({ config }) {
        // Your plugin configuration setup code
      },
    },
  };

• #2578 f895f75 Thanks @HiDeoo! - Exposes the built-in localization system in the Starlight plugin config:setup hook.

  ⚠️ BREAKING CHANGE:

  This addition changes how Starlight plugins add or update translation strings used in Starlight’s localization APIs.
  Plugins previously using the injectTranslations() callback function from the plugin config:setup hook should now use the same function available in the i18n:setup hook.

  export default {
    name: 'plugin-with-translations',
    hooks: {
  -   'config:setup'({ injectTranslations }) {
  +   'i18n:setup'({ injectTranslations }) {
        injectTranslations({
          en: {
            'myPlugin.doThing': 'Do the thing',
          },
          fr: {
            'myPlugin.doThing': 'Faire le truc',
          },
        });
      },
    },
  };

• #2858 2df9d05 Thanks @XREvo! - Adds support for Pagefind’s multisite search features

• #2578 f895f75 Thanks @HiDeoo! - Adds a new HookParameters utility type to get the type of a plugin hook’s arguments.

• #2578 f895f75 Thanks @HiDeoo! - Adds a new useTranslations() callback function to the Starlight plugin config:setup hook to generate a utility function to access UI strings for a given language.

• #2578 f895f75 Thanks @HiDeoo! - Adds a new absolutePathToLang() callback function to the Starlight plugin config:setup to get the language for a given absolute file path.

Patch Changes

• #2848 9b32ba9 Thanks @HiDeoo! - Fixes styling of filter and metadata elements in Pagefind search UI.

Description

• Closes #2856
• It add more configuration option to pagefind, by allowing mergeIndex
• No visual changes had been made with this update.

This had been tested locally with 2 instances :

• one on port 3000 and the other on port 3001
• with this configuration

export default defineConfig({
	... ,
	integrations: [
		starlight({
			...,
			pagefind: {
				indexWeight: 2.0,
				mergeIndex: [{
					bundlePath: 'http://localhost:3001/pagefind/',
					indexWeight: 0.5,
				}]
			},
		}),
	],
});

• and network panel show that both sites where queried for search
  

What's next

• Completing the doc to let users known that they can use it (i'll do it in the the next days)

Description

• Updates Vitest from 3.0.1 to 3.0.5
• Motivated by GHSA-9crc-q9x8-hgqq
• The vulnerability doesn’t really impact us, but still thought we should update if possible

Description

This PR introduces Typst as an underlying math rendering engine. Typst is a modern and lightweight (syntactically) alternative to LaTeX. Supporting Typst will benefit those who are comfortable working with Typst instead of LaTeX.

Render math equations with Katex:

Render math equations with Typst:

Katex rendering engine and Typst rendering engine are not coexistent. Users need to choose their preferred engine in the config.

DISCLAIMER: I am a JS / TS newbie, please feel free to point out if I have done anything wrong, or even modify it directly :)

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.2.5

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.

Changes

Closes #13120

The fix is inside RenderContext, and now check if the route that we are about to render is an external redirect. If it is, we skip the whole middleware chain, and render the redirect straight away.

I checked with Matt and Florian, and they agree with the proposed solution.

Testing

I added a new test and fixture based on the reproduction provided.

Docs

N/A

Changes

#13111 removed special handling for endpoint trailing slashes, because they broke trailignSlash=always. However this caused a regression for endpoints that include a file extension. This PR changes the handling for endpoints that include a file extension, to always use trailingSlash: "ignore". This means it will match with and without the extension. I've done it liek this rather than setting to never, because that would be a breakign change. Currently file-based endpoints do obey trailing slash rules, even with file extensions. This is probably a mistake (who wants /sitemap.xml/), but some may rely on it so we'll move any change to Astro 6.

Fixes #13128

Testing

Adds tests

Docs

Changes

Multiple trailing slashes are supposed to be collapsed before applying trailing slash rules. However a regex mistake meant that it was also matching duplicate slashes that weren't trailing. This would have been a minor problem, except that in dev is was incorrectly matching against the full URL including query params, not just the path. This meant that duplicate slashes were collapsed in query params too, which is a problem when you might have https://.

This PR fixes both issues: corrects the traailing slash helper to only match trailing slashes, and ensures that the dev matching is applied to the pathname without query params

Testing

Adds a lot of tests for both dev and SSR to cover these.

Fixes #13127

Docs

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.2.4

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

@astrojs/markdoc@0.12.9

Patch Changes

• Updated dependencies [b71bd10]:
  • @astrojs/internal-helpers@0.5.1

@astrojs/preact@4.0.4

Patch Changes

• #12950 c497491 Thanks @Marabyte! - Upgrades @preact/preset-vite

@astrojs/internal-helpers@0.5.1

Patch Changes

• #13130 b71bd10 Thanks @ascorbic! - Fixes a bug that meant that internal as well as trailing duplicate slashes were collapsed

Changes

This PR fixes a typo in the JSDoc: WrakMap should be WeakMap

Testing

N/A

Docs

N/A

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tailwindcss (source)	^3.4.17 -> ^4.0.3

Release Notes

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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 these updates again.

• If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@playwright/test (source)	1.50.0 -> 1.50.1
@playwright/test (source)	^1.50.0 -> ^1.50.1
@tailwindcss/vite (source)	^4.0.1 -> ^4.0.3
@types/html-escaper (source)	3.0.2 -> 3.0.4
preferred-pm (source)	^4.1.0 -> ^4.1.1
rollup (source)	^4.32.1 -> ^4.34.2
semver	^7.7.0 -> ^7.7.1
svelte (source)	^5.19.6 -> ^5.19.7
tailwindcss (source)	^4.0.1 -> ^4.0.3
turbo (source)	^2.3.4 -> ^2.4.0
typescript-eslint (source)	^8.22.0 -> ^8.23.0
vite-plugin-solid	^2.11.0 -> ^2.11.1
vitest (source)	^3.0.4 -> ^3.0.5
which-pm (source)	^3.0.0 -> ^3.0.1

Release Notes

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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.

Description

• Update the plugin list with a new plugin - starlight-giscus

Changes

Making it more clear that a user action is required after onboarding to tailwind v4.

twitter thread: https://x.com/Hacksore/status/1885490439437857143

Testing

built locally and ran node astro.js add tailwind in the packages/astro dir.

Docs

N/A

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.2.3

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

Changes

rewrite will first decode pathname before passing it to dynamic routing.

Fixes #13098

Testing

Add test cases for dynamic routing. Only static mode rewrite is tested.

Docs

Changes

Back in the day, endpoints were special-cased to ignore trailing slash rules and always have it set to ignore. This turned out to break things, so it was removed for file-based endpoint routes in #9597. However injected endpoints were left out of that fix, meaning there was still the bug for them.

Fixes #13105

Testing

Added tests

Docs

Adds customization for the default ~partytown copy file folder in @astrojs/partytown during the astro:build:done hook.

Changes

• Adds support for overriding copyLibFiles.dest in the astro:build:done hook using the lib option in astro.config.*.
• If lib is not specified, it defaults to ~partytown.
• Removes the leading "/" from the lib value to match the behavior of fileURLToPath.

Testing

If no tests added, explain why.

I didn't add tests because I'm still figuring out how testing works. But I tested it locally by running astro build, and the copy file from Partytown is being copied correctly. The logic seems to work well.

Docs

/cc @withastro/maintainers-docs for feedback!

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.2.2

Patch Changes

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

Changes

Special-cases tailwind to ensure it doesn't install the integration package, which is deprecated. Previously it was always installing the integration package, even though it was also always added to the dependencies list. This changes it to only install the listed deps. It also adds an integrationName field, because in logs it was confusing having it log @astrojs/tailwind when that package wasn't actually installed.

Fixes #13097

Testing

There are currently no tests for atro add. It's a tough one to test without some kind of mocking for the package manager, so I'll leave it for now, beacuse this bug is affecting lots of users.

Docs

Changes

Fixes #13079
Fixes #13104
Fixes #13103

Also ensure that HTTP method CONNECT gets origin checked as well (it was previously wrongly omitted because only POST, PUT, PATCH, DELETE were previously checked).

Inspired by @joshmkennedy's PR #13100

Testing

Add test for HEAD getting correct HTTP response 200 (this would have failed prior to his prior)

Docs

Pure bug fix, no docs changes necessary

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.2.1

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"

Changes

Skips internal Vite requests when checking trailing slashes

Fixes #13094

Testing

Adding tests now

Docs

Changes

• Closes PLT-2756
• Adds a basic Fonts component
• Adds the virtual module and most of the "core features"
  • resolving providers
  • resolving fonts data
  • caching
  • dev/build handling
• Updates the config

Testing

Manual + automated

Docs

N/A

These were 404s for me

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/tailwind@6.0.0

Major Changes

• #13049 2ed4bd9 Thanks @florian-lefebvre! - Deprecates the integration

  Tailwind CSS now offers a Vite plugin which is the preferred way to use Tailwind 4 in Astro. Please uninstall @astrojs/tailwind and follow the Tailwind documentation for manual installation.

  This updated major version is only provided as a convenience for existing projects until they are able to migrate to the new plugin. It offers no additional functionality and is no longer recommended, but may continue to be used in your projects until it is removed entirely.

astro@5.2.0

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

@astrojs/internal-helpers@0.5.0

Minor Changes

• #12994 5361755 Thanks @ascorbic! - Adds collapseDuplicateTrailingSlashes function

@astrojs/markdown-remark@6.1.0

Minor Changes

• #12850 db252e0 Thanks @colinbate! - Adds support for TOML frontmatter in .md and .mdx files

  Astro 5.2 automatically identifies the format of your Markdown and MDX frontmatter based on the delimiter used. With +++ as a delimiter (instead of the --- YAML code fence), your frontmatter will automatically be recognized and parsed as TOML.

  This is useful for adding existing content files with TOML frontmatter to your project from another framework such as Hugo.

  TOML frontmatter can also be used with content collections, and files with different frontmatter languages can live together in the same project.

  No configuration is required to use TOML frontmatter in your content files. Your delimiter will indicate your chosen frontmatter language:

  +++
  date = 2025-01-30
  title = 'Use TOML frontmatter in Astro!'
  [author]
  name = 'Colin Bate'
  +++
  
  # Support for TOML frontmatter is here!

@astrojs/markdoc@0.12.8

Patch Changes

• Updated dependencies [5361755, db252e0]:
  • @astrojs/internal-helpers@0.5.0
  • @astrojs/markdown-remark@6.1.0

@astrojs/mdx@4.0.8

Patch Changes

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

Description

• Closes #
• What does this PR change? Give us a brief description.
• Did you change something visual? A before/after screenshot can be helpful.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight-docsearch@0.5.0

Minor Changes

• #2822 e56586a Thanks @KianNH! - Adds a new clientOptionsModule plugin option to support configuring unserializable DocSearch options such as resultsFooterComponent().

  See “DocSearch configuration” in the Starlight docs for more details.

Changes

This PR merges the first implementation of withastro/roadmap#1106

Testing

CI should pass

Docs

/cc @withastro/maintainers-docs for feedback!

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/node (source)	^9.0.1 -> ^9.0.2
@changesets/cli (source)	^2.27.11 -> ^2.27.12
@playwright/test (source)	1.49.1 -> 1.50.0
@playwright/test (source)	^1.49.1 -> ^1.50.0
@tailwindcss/vite (source)	^4.0.0 -> ^4.0.1
@types/html-escaper (source)	^3.0.2 -> ^3.0.3
eslint (source)	^9.18.0 -> ^9.19.0
fs-fixture	^2.6.0 -> ^2.7.0
linkedom	^0.18.6 -> ^0.18.7
open-props	^1.7.10 -> ^1.7.12
p-queue	^8.0.1 -> ^8.1.0
preferred-pm (source)	^4.0.0 -> ^4.1.0
rollup (source)	^4.31.0 -> ^4.32.1
semver	^7.6.3 -> ^7.7.0
shiki (source)	^1.29.1 -> ^1.29.2
svelte (source)	^5.19.0 -> ^5.19.6
tailwindcss (source)	^4.0.0 -> ^4.0.1
turbo (source)	^2.3.3 -> ^2.3.4
typescript-eslint (source)	^8.20.0 -> ^8.22.0
undici (source)	^7.2.3 -> ^7.3.0
vite-plugin-vue-devtools (source)	^7.7.0 -> ^7.7.1
vitest (source)	^3.0.2 -> ^3.0.4
yocto-spinner	^0.1.2 -> ^0.2.0

Release Notes

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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.

Changes

Allow sharp format options (e.g. https://sharp.pixelplumbing.com/api-output#avif)

Testing

I haven't added any tests yet, just opening to see if the feature is desired and this a good approach. However I'm not sure how to test this, trying all combinations would be impossible, maybe mocking to check options are actually passed is an option

Docs

I will add the change to the config reference once the api is decided.

cc @Princesseuh as discussed on Discord

Hello!

We have a repo where I wanted to use our logo as favicon. SVGs may finally be used directly! 🤗
But we do have to provide PNGs as fallback. And even .ico, to be really safe.

The idea was to then commit just the SVG as asset and single source of truth, and convert that through getImage.

Generating the .ico is kind of special¹, but this approach worked, so I figured it'd be pretty much the same for getImage.

Interestingly, however, when we tried to do the same in the component using getImage we would just get the same SVG out, untouched.

I was then able to find #7643 where this was deliberately implemented. From what I understand, other transformation services may not support SVG, but I'm not sure why it would be prevented in Sharp, too?

I couldn't really figure out the rationale, but maybe I'm missing something. Hope this makes sense!

Changes

• Let Sharp process SVG files

Testing

I tested this against my repo, where I had identified the bug, with the following component:

---
import faviconSrc from "@assets/logo.svg";

const favicon = (size: number) =>
  getImage({
    src: faviconSrc,
    format: "png",
    width: size,
    height: size,
  });

const appleTouchIcon = await favicon(180);
const favicon32 = await favicon(32);
const favicon16 = await favicon(16);
---

<link rel="apple-touch-icon" href={appleTouchIcon.src} />
<link rel="icon" type="image/png" sizes="32x32" href={favicon32.src} />
<link rel="icon" type="image/png" sizes="16x16" href={favicon16.src} />

Docs

I'm not sure whether something should be added to the docs, to be honest, I didn't find anything mentioning that SVG would not be supported as an input to getImage in the docs, but that's the case right now. With this fix, nothing should be mentioned as things should just work out of the box.

Changes

A bug in the way the patterns were generated meant that if there were multiple wildcard patterns in a path alias, only the first would ever match.

Fixes #13051

Testing

Added test cases

Docs

Changes

#13029 seems to have introduced a syntax error in an import. This fixes it and adds a biome ignore

Fixes #13057

Testing

Docs

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/react@4.2.0

Minor Changes

• #13036 3c90d8f Thanks @artmsilva! - Adds experimental support for disabling streaming

  This is useful to support libraries that are not compatible with streaming such as some CSS-in-JS libraries. To disable streaming for all React components in your project, set experimentalDisableStreaming: true as a configuration option for @astrojs/react:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import react from '@astrojs/react';
  
  export default defineConfig({
    integrations: [
      react({
  +      experimentalDisableStreaming: true,
      }),
    ],
  });

astro@5.1.10

Patch Changes

• #13058 1a14b53 Thanks @ascorbic! - Fixes broken type declaration

• #13059 e36837f Thanks @ascorbic! - Fixes a bug that caused tsconfig path aliases to break if there was more than one wildcard pattern

• #13045 c7f1366 Thanks @mtwilliams-code! - Fixes a bug where the some utility functions of the astro:i18n virtual module would return an incorrect result when trailingSlash is set to never

Changes

Part of proposal withastro/roadmap#1106

This PR does a bit of refactoring in order to extract the correct information to send to the virtual module.

• The source of truth must be the SSRManifest, because the virtual module information must be preserved even in on-demand pages. This means that the input source of the vite plugin is the SSRManifest. The manifest wasn't available in some of the commands, so I had to use createDevelopmentManifest whenever it was possible.
• To make the DX pleasant, and provide to the virtual module the same types that are defined in AstroConfig, I created a deserialisation phase, which transforms directories from string to URL, and the i18n strategy to its former configuration.
• I added new properties to the SSRManifest
• I renamed the ManifestData type to RoutesList, because it isn't actually a manifest. At some point we manifest and ssrManifest, which was really confusing.

Testing

The current tests should pass. I moved a failing test inside its own fixture, otherwise the valid fixture will never build.

Docs

Changes

• Closes PLT-2759
• Supports tailwind v4 (breaking change, this major only supports v4)
• Drops support for astro <= 5.0 (we rely on some 5.0 only features)
• Removes the nesting option as it's supported oob

Testing

Updated, should pass, and tested manually

Docs

Changeset, withastro/docs#10773

Description

The icon of :link directive (External URL variant) used favicon.yandex.net to obtain the icon, which is 16 x 16 by default. This PR improves the resolution of icons using Google's API.

Changes

• Adds a propType for using a parsed-from-JSON value directly, without reviving sub-objects via tuples. This allows web pages generated by external systems (not Astro) to use Astro islands without needing to encode props containing nested but basic (representable with JSON) data into tuples.

Testing

• No tests added yet. Wanting to get confirmation on whether Astro maintainers are open to this PR before I spend time on adding tests.

Docs

• No docs added yet. Wanting to get confirmation on whether Astro maintainers are open to this PR before I spend time on adding docs.

Changes

fixes #13035
getLocaleRelativeUrl will now return a '/' instead of an empty string in the case of base: '/' and trailingSlash: 'never'.
Changing this behavior of getLocalRelativeUrl caused a similar error in getLocaleAbsoluteUrl for trailingSlash: 'never' because it internaly uses getLocaleRelativeUrl. This is resolved similarly.

Testing

Added tests for both cases - the logic for testing base: '/' had only been testing when trailingSlash:'always'.

Docs

Changes

This PR fixes #13041

• It edits only one file, BaseHead.astro, in the Astro blog starter kit. It adds three new lines to that file.
• It adds a rel link to the (already-existing) /sitemap-index.xml file created by @astrojs/sitemap
• It adds a rel link to the (already-existing) /rss.xml file created by @astrojs/rss
• The link to the RSS feed file needs the global SITE_TITLE, so I added a line to the frontmatter to import that.

Testing

I created a personal blog using the Astro blog starter kit and noticed that these rel links were missing, so I added them. It worked.

Docs

No additional documentation is required because of this PR. In fact, I got most of the code for this PR from existing Astro documentation:

• the documentation for @astrojs/sitemap
• the documentation for @astrojs/rss

Description

• Closes #2806
• Adds a clientOptionsModule option to the starlightDocSearch plugin.
  • This takes the shape of a path to a JavaScript or TypeScript file which will be imported (if present) and merged with existing options in the starlight/docsearch-config virtual module.
  • If an option exists in both, i.e appId, the option in the clientOptionsModule file will be used.

Considerations

• Updating documentation

• Tests

Whilst this is probably not a large enough package to warrant it, I did setup try out setting up Vitest for this package where vitePluginDocSearch is passed in vitest.config.ts but since it would need a lot of work to setup a harness to test starlightDocSearch I opted against including it.

Changes

• Added popover to the list of boolean attributes

see: #11342 (comment)

Testing

Docs

Changes

This pull request introduces a new feature to the React integration by adding an option to disable streaming support. This feature aims to support libraries that are not compatible with streaming, such as Stitches.js. The most important changes include updates to the configuration options and rendering logic.

Testing

Docs

withastro/docs#10761

/cc @withastro/maintainers-docs for feedback!

Brings back #11513

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.1.9

Patch Changes

• #12986 8911bda Thanks @wetheredge! - Updates types and dev toolbar for ARIA 1.2 attributes and roles

• #12892 8f520f1 Thanks @louisescher! - Adds a more descriptive error when a content collection entry has an invalid ID.

• #13031 f576519 Thanks @florian-lefebvre! - Updates the server islands encoding logic to only escape the script end tag open delimiter and opening HTML comment syntax

• #13026 1d272f6 Thanks @ascorbic! - Fixes a regression that prevented the import of Markdown files as raw text or URLs.

@astrojs/alpinejs@0.4.3

Patch Changes

• #13014 820eee3 Thanks @jasonlav! - Fixes an issue with user scripts running after Alpine.start()

Changes

The fix in #12711 caused a regression for imports for markdown files as static assets using the ?raw param. That only worked accidentally before, but this is the proper fix.

I am just checking the id for ?raw. I realise this could in theory miss cases where there are multiple params, but I'm not aware of any cases where that would be legitimate so didn't think it was worth the cost of adding a full query param parse on every import. I'm open to other opinions on this though.

Fixes #13025

Testing

Added a test case

Docs

Changes

Add support for standard Content-Type and Content-Disposition http headers in SSG.

This PR is an implementation of this proposal, which seems to be mostly well received.

Why

Currently, middleware in SSR can override the filename or media type of .astro templates using the standard Content-Type and Content-Disposition http headers, and the browser will interpret it correctly. SSG will completely ignore these http headers and produce bad output, inconsistent with SSR. This PR brings SSR and SSG into alignment by adding Content-Type and Content-Disposition support to SSG builds.

This is mostly helpful for middleware that wants to modify the response for .astro templates to be file-based, but is fairly generic can have other uses as well.

Example

if this is returned by middleware when requesting opengraph-image.astro:

return new Response(body, {
  headers: {
    "Content-Type": "image/png", // Would be ignored during an SSG build
    "Content-Disposition": `inline; filename="opengraph-image.png"`,
  },
});

How this will be used

The main use case I have in mind for this change is an integration that allows people to define opengraph images using .astro templates that result in png images. This is not possible today, but would be trivial if this PR is merged. I have published a proof of concept integration that works in SSR but doesn't work in SSG, but would work everywhere with this PR.

Addressing Discusssion

Using standard http headers

There was some discussion of not using standard http headers. I think we absolutely should use these headers because:

• it makes SSR/SSG configuration symmetrical.
• a user might set both the custom configuration AND use the http headers (which already work in SSR today) and we'd have to decide how to handle that, with no good options that are obvious to me.

I feel strongly we should use standard http headers.

Other usecases

There was [some discussion] of other usecases (e.g. withastro/roadmap#643 (comment)) that I haven't tested but should be handled by this feature as-implemented.

Asymmetry between SSR/SSG

There was a conversation about this potentially introducing asymmetry between SSR/SSG.

I think this is a very valid concern, but, while this could be used to introduce asymmetry but it can also be used to fix asymmetry that is impossible to fix today. Example in the discussion.

Concerns

My current implementation has one issue which should either be discussed: if you dynamically use middleware to rewrite where you output the result of a request for a .astro template, the manifest/assets will not be exactly correct. For example, you might rewrite a .astro template to a png image, but the image will not be in the SSR manifest assets. The build asset URLs will reflect the correct output URL though, and I wrote a unit test that captures this.

I am unclear on how these integration hooks (which are the only way I know of to introspect the manifest during a build) are meant to be used, so I have no idea if this is a problem or not. I am unable to fix it though because we discover middleware rewriting AFTER we do the Vite build, which is where the manifest is generated.

Testing

I have added several unit tests to test the basic functionality. I have not extensively tested every edge/error case but would be happy to add more tests if this PR makes it far enough.

Docs

This is a new feature which would require documentation. I have not yet written that documentation but will if I get the provisional go-ahead.

This is a new feature that is unlikely to be incompatible with any existing astro sites. This would break backwards compatibility if someone is using Content-Disposition with .astro templates in SSG today, but since that does nothing and is totally broken, I can't imagine this is in use anywhere. So this should be documentation for a new feature.

This change does cause the existing build.format configuration option to be ignored for non-html astro templates where the filename is overridden, and I have updated the documentation to capture this. (jsdoc comment that backs the Configuration Reference documentation.

Related to issue #12710 (comment).

Externally loaded AlpineJS component scripts were loaded after Alpine.start() was triggered. Issue started with Astro V5.

Changes

• Runs Alpine.start() on the DOMContentLoaded event. According to MDN documentation (https://developer.mozilla.org/en-US/docs/Web/API/Document/DOMContentLoaded_event), DOMContentLoaded fires immediately after HTML and deferred scripts are loaded. In short, this change guarantees that Alpine.start() is only called after all scripts are loaded.

Testing

• This is a bugfix and integrations do not appear to have tests.

Docs

• No documentation updates necessary; resolving a bug.

This reverts commit f64b73c.

Changes

#11513 caused test failures on main

Testing

Docs

Changes

Upgrades Vite to fix GHSA-vg6x-rcgg-rjx6
This is a breaking change and lots of tests were failing. This PR contains the fix, which is to ensure the host header is set.

Testing

Updates tests

Docs

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/node (source)	^9.0.0 -> ^9.0.1
@solidjs/router	^0.15.2 -> ^0.15.3
postcss (source)	^8.4.49 -> ^8.5.1
rollup (source)	^4.30.1 -> ^4.31.0
sass	^1.83.1 -> ^1.83.4
shiki (source)	^1.26.2 -> ^1.29.1
svelte (source)	^5.17.3 -> ^5.19.0
typescript-eslint (source)	^8.19.1 -> ^8.20.0
undici (source)	^7.2.1 -> ^7.2.3

Release Notes

postcss/postcss (postcss)

v8.5.1

Compare Source

• Fixed backwards compatibility for complex cases (by @​romainmenke).

v8.5.0: 8.5 “Duke Alloces”

Compare Source

PostCSS 8.5 brought API to work better with non-CSS sources like HTML, Vue.js/Svelte sources or CSS-in-JS.

@​romainmenke during his work on Stylelint added Input#document in additional to Input#css.

root.source.input.document //=> "<p>Hello</p>
                           //    <style>
                           //    p {
                           //      color: green;
                           //    }
                           //    </style>"
root.source.input.css      //=> "p {
                           //      color: green;
                           //    }"

Thanks to Sponsors

This release was possible thanks to our community.

If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:

• Tidelift with a Spotify-like subscription model supporting all projects from your lock file.
• Direct donations at GitHub Sponsors or Open Collective.