AstroEco is Contributing…

Display your GitHub pull requests using astro-loader-github-prs

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/cloudflare@12.5.5

Patch Changes

#13930 acb9b30 Thanks @alexanderniebuhr! - Fixes an issue where setting values for Astro.response resulted in a Cloudflare runtime exception.

[ci] release

withastro/starlight

#3249 Jun 13

Releases

@astrojs/starlight@0.34.4

Patch Changes

#3205 95d124a Thanks @sgalcheung! - Fixes an issue preventing to use the <StarlightPage> component when the docs content collection that Starlight uses does not exist.
#3206 e6ea584 Thanks @HiDeoo! - Fixes a text selection issue for heading with a clickable anchor link when using double click to select text in Chrome and Safari.
#3233 3064c40 Thanks @torn4dom4n! - Updates Vietnamese UI translations.
#3248 16c1239 Thanks @HiDeoo! - Prevents icons in the <Card> component from being shrunk in some narrow viewports.
#3225 21b93b8 Thanks @randomguy-2650! - Updates German UI translations

Prevent `<Card>` icon from being shrunk

withastro/starlight

#3248 Jun 13

Description

Initially spotted by @ArmandPhilippot in Astro Docs, this PR prevents icons in <Card> components from being shrunk.

Before	After

Remaining tasks

Remove the code change in docs/src/content/docs/index.mdx only used to make the issue more visible.

new showcase entries for vtbot's Jotter and vtbag

withastro/starlight

#3246 Jun 12

Description

The Bag of Tricks for Astro's View Transitions (= view transitions with the <ClientRouter />)
The Bag of Tricks for View Transitions, @vtbag (= view transitions with the browser native API)

fix(cloudflare): internal fetch

withastro/astro

#13930 Jun 12

closes #13791

Compatible Astro 5.9 new API renderMarkdown

withastro/starlight

#3241 Jun 11

Description

Closes #3239

Create a createMarkdownTestHelper method to reduce repeated creation of createMarkdownProcessor, and this method could initialize different parameters in the test method, so we get all tests passed!

before

after

~~Next, I will create a test to reproduce this bug, so that we can better verify the modified code logic.~~
Add a test(should correctly autolink headings in remote markdown content using rehypeAutolinkHeadings) to reproduce this bug

TypeError: Failed to parse Markdown file "undefined":
Cannot read properties of undefined (reading 'replace')
at normalizePath (/Users/sgalcheung/Documents/....../starlight/packages/starlight/integrations/heading-links.ts:110:14)
at transformer (/Users/sgalcheung/Documents/....../starlight/packages/starlight/integrations/heading-links.ts:34:8)
at wrapped (file:///Users/sgalcheung/Documents/....../starlight/node_modules/.pnpm/trough@2.1.0/node_modules/trough/index.js:115:27)
at next (file:///Users/sgalcheung/Documents/....../starlight/node_modules/.pnpm/trough@2.1.0/node_modules/trough/index.js:65:23)
at done (file:///Users/sgalcheung/Documents/....../starlight/node_modules/.pnpm/trough@2.1.0/node_modules/trough/index.js:148:7)
at then (file:///Users/sgalcheung/Documents/....../starlight/node_modules/.pnpm/trough@2.1.0/node_modules/trough/index.js:158:5)
at wrapped (file:///Users/sgalcheung/Documents/....../starlight/node_modules/.pnpm/trough@2.1.0/node_modules/trough/index.js:136:9)
at next (file:///Users/sgalcheung/Documents/....../starlight/node_modules/.pnpm/trough@2.1.0/node_modules/trough/index.js:65:23)
at done (file:///Users/sgalcheung/Documents/....../starlight/node_modules/.pnpm/trough@2.1.0/node_modules/trough/index.js:148:7)
at then (file:///Users/sgalcheung/Documents/....../starlight/node_modules/.pnpm/trough@2.1.0/node_modules/trough/index.js:158:5)

feat(csp): add static header adapter function

withastro/astro

#13926 Jun 11

Changes

This PR adds a new feature and fixes a bug.

Feature

It adds a new experimental adapter feature called staticHeaders. See the updated section here: https://github.com/withastro/roadmap/blob/feat/rfc-csp/proposals/0055-csp.md#solution-adopted

The adapter feature is intentionally generic, allowing CSP to take advantage of it. It's been called experimental because the first feature to use it is CSP, so we want to make sure we get the API right first.

The PR doesn't update any adapters yet. I will do that in a separate PR.

To support this feature, we now track a new field called cspDestination within the SSRManifest. In the manifest, the value is intentionally undefined if the adapter doesn't use the new feature. The final value is eventually calculated at the very end, right before the rendering phase, and that's why the value becomes NonNullable.

Bug fix

Addresses

withastro/roadmap#1168 (review)

Where the meta tag should be rendered as early as possible.

Testing

I updated the tests and added new ones.

Docs

@withastro/maintainers-docs for feedback!

[ci] release

withastro/astro

#13925 Jun 11

Releases

astro@5.9.3

Patch Changes

#13923 a9ac5ed Thanks @ematipico! - BREAKING CHANGE to the experimental Content Security Policy (CSP) only

Changes the behavior of experimental Content Security Policy (CSP) to now serve hashes differently depending on whether or not a page is prerendered:
- Via the <meta> element for static pages.
- Via the Response header content-security-policy for on-demand rendered pages.
This new strategy allows you to add CSP content that is not supported in a <meta> element (e.g. report-uri, frame-ancestors, and sandbox directives) to on-demand rendered pages.

No change to your project code is required as this is an implementation detail. However, this will result in a different HTML output for pages that are rendered on demand. Please check your production site to verify that CSP is working as intended.

To keep up to date with this developing feature, or to leave feedback, visit the CSP Roadmap proposal.
#13926 953a249 Thanks @ematipico! - Adds a new Astro Adapter Feature called experimentalStaticHeaders to allow your adapter to receive the Headers for rendered static pages.

Adapters that enable support for this feature can access header values directly, affecting their handling of some Astro features such as Content Security Policy (CSP). For example, Astro will no longer serve the CSP <meta http-equiv="content-security-policy"> element in static pages to adapters with this support.

Astro will serve the value of the header inside a map that can be retrieved from the hook astro:build:generated. Adapters can read this mapping and use their hosting headers capabilities to create a configuration file.

A new field called experimentalRouteToHeaders will contain a map of Map<IntegrationResolvedRoute, Headers> where the Headers type contains the headers emitted by the rendered static route.

To enable support for this experimental Astro Adapter Feature, add it to your adapterFeatures in your adapter config:
```
// my-adapter.mjs
export default function createIntegration() {
  return {
    name: '@example/my-adapter',
    hooks: {
      'astro:config:done': ({ setAdapter }) => {
        setAdapter({
          name: '@example/my-adapter',
          serverEntrypoint: '@example/my-adapter/server.js',
          adapterFeatures: {
            experimentalStaticHeaders: true,
          },
        });
      },
    },
  };
}
```
See the Adapter API docs for more information about providing adapter features.
#13697 af83b85 Thanks @benosmac! - Fixes issues with fallback route pattern matching when i18n.routing.fallbackType is rewrite.
- Adds conditions for route matching in generatePath when building fallback routes and checking for existing translated pages
Now for a route to be matched it needs to be inside a named [locale] folder. This fixes an issue where route.pattern.test() incorrectly matched dynamic routes, causing the page to be skipped.
- Adds conditions for route matching in findRouteToRewrite
Now the requested pathname must exist in route.distURL for a dynamic route to match. This fixes an issue where route.pattern.test() incorrectly matched dynamic routes, causing the build to fail.
#13924 1cd8c3b Thanks @qw-in! - Fixes an edge case where isPrerendered was incorrectly set to false for static redirects.
#13926 953a249 Thanks @ematipico! - Fixes an issue where the experimental CSP meta element wasn't placed in the <head> element as early as possible, causing these policies to not apply to styles and scripts that came before the meta element.

fix: isPrerendered now set correctly in static configured redirects.

withastro/astro

#13924 Jun 10

Changes

Closes #13875

Previously, isPrerendered would be false in statically built configured redirects (notably in middleware).

Testing

I added a test, happy to expand or reorganize. Additionally I've run the full test suite locally and I don't have any new failures (rosetta + devcontainers likely the culprit #12704).

Docs

This is a fix, so I don't think docs are necessary?

refactor(csp): change CSP behaviour

withastro/astro

#13923 Jun 10

Changes

This PR changes how the CSP hashes are served. For static pages, we still serve them via the <meta> element, but for SSR pages, they are served using the Reponse headers.

This change partially addresses the following comments, where now the content of the CSP header for SSR pages can support directives that wouldn't be supported in the meta:

After landing this PR, I will move forward with the second part of Matthew's comment, where if there's an adapter, the meta tag isn't provided anymore for static pages, instead we will use the adapter's hosting capabilities to deliver those hashes:

Testing

Added a new test

Docs

I will update the roadmap PR after this PR is accepted.
I will send a pull request to the docs later.

fix(csp): quotes and resources

withastro/astro

#13919 Jun 9

Changes

I think I saw this bug in the roadmap, or there was an issue? I can't recall. Regardless, with this PR, astro doesn't add the quote to the resources. Only certain resources must have quotes e.g. 'self', and users must be responsible for them.

Testing

Tests updated

Docs

Updated the configuration examples. Will need to update the roadmap too

feat: unflag responsive images

withastro/astro

#13917 Jun 9

Changes

Unflags the responsive images feature
Defaults responsive styles to false
Makes the priority attribute available to all images

Migration Guide

If you were using the experimental responsive images feature, you'll need to update your configuration:

Remove the experimental flag

export default defineConfig({
   experimental: {
-    responsiveImages: true,
   },
});

Update image configuration options

During the experimental phase, default styles were applied automatically to responsive images. Now, you need to explicitly set the responsiveStyles option to true if you want these styles applied.

export default defineConfig({
  image: {
+    responsiveStyles: true,
  },
});

The experimental image configuration options have been renamed:

Before:

export default defineConfig({
  image: {
    experimentalLayout: 'constrained',
    experimentalObjectFit: 'cover', 
    experimentalObjectPosition: 'center',
    experimentalBreakpoints: [640, 750, 828, 1080, 1280],
    experimentalDefaultStyles: true, 
  },
  experimental: {
    responsiveImages: true,
  },
});

After:

export default defineConfig({
  image: {
    layout: 'constrained',
    objectFit: 'cover',
    objectPosition: 'center', 
    breakpoints: [640, 750, 828, 1080, 1280],
    responsiveStyles: true, // This is now *false* by default
  },
});

The `priority` option for the image component

By default, the Astro <Image /> component generates <img> tags that lazy-load their content by setting loading="lazy" and decoding="async". This improves performance by deferring the loading of images that are not immediately visible in the viewport, and gives the best scores in performance audits like Lighthouse. However, for the main, above-the-fold images, you should tell the browser to load them immediately. Currently you can do this by setting the loading attribute to "eager" and decoding to "sync" on the <img> tag, but this is a bit cumbersome. It also does not currently set the fetchpriority attribute, which is a new HTML attribute that allows you to specify the priority of resource fetching.

This change introduces a new priority option for the <Image /> and <Picture /> components, which automatically sets the loading, decoding, and fetchpriority attributes to their optimal values for above-the-fold images. It is a boolean prop, and you can use the shorthand syntax by simply adding priority as a prop to the <Image /> or <Picture /> component. When set, it will apply the following attributes:

loading="eager"
decoding="sync"
fetchpriority="high"

The individual attributes can still be set manually if you need to customize them further.

This option was previously available for experimental responsive images, but now it is a standard feature for all images.

Usage

<Image 
  src="/path/to/image.jpg" 
  alt="An example image" 
  priority
/>

Note

You should only use the priority option for images that are critical to the initial rendering of the page, and ideally only one image per page. Using it for too many images will lead to performance issues, as it forces the browser to load those images immediately, potentially blocking the rendering of other content.

Testing

Updated test fixtures

Docs

Changes needed beyond the initial planned unflagging:

renamed responsiveStyles option now defaults to false
new priority option

[ci] release

withastro/astro

#13915 Jun 9

Releases

astro@5.9.2

Patch Changes

#13919 423fe60 Thanks @ematipico! - Fixes a bug where Astro added quotes to the CSP resources.

Only certain resources require quotes (e.g. 'self' but not https://cdn.example.com), so Astro no longer adds quotes to any resources. You must now provide the quotes yourself for resources such as 'self' when necessary:
```
export default defineConfig({
  experimental: {
    csp: {
      styleDirective: {
        resources: [
-          "self",
+          "'self'",
          "https://cdn.example.com"
        ]
      }
    }
  }
})
```
#13914 76c5480 Thanks @ematipico! - BREAKING CHANGE to the experimental Content Security Policy feature only

Removes support for experimental Content Security Policy (CSP) when using the <ClientRouter /> component for view transitions.

It is no longer possible to enable experimental CSP while using Astro's view transitions. Support was already unstable with the <ClientRouter /> because CSP required making its underlying implementation asynchronous. This caused breaking changes for several users and therefore, this PR removes support completely.

If you are currently using the component for view transitions, please remove the experimental CSP flag as they cannot be used together.
```
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
-   csp: true
   }
});
```
Alternatively, to continue using experimental CSP in your project, you can consider migrating to the browser native View Transition API and remove the <ClientRouter /> from your project. You may be able to achieve similar results if you are not using Astro's enhancements to the native View Transitions and Navigation APIs.

Support might be reintroduced in future releases. You can follow this experimental feature's development in the CSP RFC.

fix(csp): drop view transitions support

withastro/astro

#13914 Jun 9

Changes

Depends on withastro/compiler#1081

This PR drops support for view transitions in CSP. Making the function renderTrantion asynchronous caused some undesirable effects in userland. We already knew that the support was unstable, and this regression made me decide that we aren't ready yet.

Closes #13908

Testing

I removed the tests

Docs

I will send a PR to the docs repository before the release

fix(deps): update astro client runtimes to v19 (major)

withastro/astro

#13913 Jun 9

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/react (source)	`^18.3.23` -> `^19.1.8`
@types/react-dom (source)	`^18.3.7` -> `^19.1.6`
react (source)	`^18.3.1` -> `^19.1.0`
react-dom (source)	`^18.3.1` -> `^19.1.0`

Release Notes

facebook/react (react)

Package	Change	Age	Adoption	Passing	Confidence
@sveltejs/vite-plugin-svelte (source)	`^5.0.3` -> `^5.1.0`
@vitejs/plugin-react (source)	`^4.5.0` -> `^4.5.2`
cheerio (source)	`1.0.0` -> `1.1.0`
linkedom	`^0.18.10` -> `^0.18.11`
preact (source)	`^10.26.8` -> `^10.26.9`
svelte (source)	`^5.33.14` -> `^5.34.1`

Package	Change	Age	Adoption	Passing	Confidence
@netlify/blobs	`^8.2.0` -> `^9.1.5`
@netlify/functions	`^3.1.5` -> `^4.1.2`
execa	`^8.0.1` -> `^9.6.0`
express (source)	`^4.21.2` -> `^5.1.0`

Package	Change	Age	Adoption	Passing	Confidence
@preact/signals (source)	`^2.0.5` -> `^2.2.0`
@types/react (source)	`^18.3.22` -> `^18.3.23`
@vitejs/plugin-react (source)	`^4.5.0` -> `^4.5.1`
@vue/compiler-sfc (source)	`^3.5.15` -> `^3.5.16`
preact (source)	`^10.26.7` -> `^10.26.8`
svelte (source)	`^5.33.2` -> `^5.33.14`
vue (source)	`^3.5.15` -> `^3.5.16`

Releases

@astrojs/cloudflare@12.5.5

Patch Changes

Releases

@astrojs/starlight@0.34.4

Patch Changes

Description

Remaining tasks

Description

Description

Changes

Feature

Bug fix

Testing

Docs

Releases

astro@5.9.3

Patch Changes

Changes

Testing

Docs

Changes

Testing

Docs

Changes

Testing

Docs

Changes

Migration Guide

Remove the experimental flag

Update image configuration options

The priority option for the image component

Usage

Testing

Docs

Releases

astro@5.9.2

Patch Changes

Changes

Testing

Docs

Release Notes

New Features

React

React DOM Client

React DOM Server

React Server Components

Deprecations

Breaking Changes

React

React DOM

Notable Changes

React

React DOM

TypeScript Changes

All Changes

React

React DOM

React DOM Server

ReactTestRenderer

React Reconciler

React-Is

useSyncExternalStore

New Features

React

Configuration

Release Notes

Minor Changes

Patch Changes

Suggest @vitejs/plugin-react-oxc if rolldown-vite is detected #​491

Use optimizeDeps.rollupOptions instead of optimizeDeps.esbuildOptions for rolldown-vite #​489

Add Vite 7-beta to peerDependencies range #​497

What's Changed

Doc Improvements

New Contributors

Fixes

Maintenance

Patch Changes

Minor Changes

Patch Changes

The `priority` option for the image component

Suggest `@vitejs/plugin-react-oxc` if rolldown-vite is detected #491

Use `optimizeDeps.rollupOptions` instead of `optimizeDeps.esbuildOptions` for rolldown-vite #489

Add Vite 7-beta to peerDependencies range #497