security(deps): Update dependency astro #86
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/npm-astro-vulnerability"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^4.0.0 || ^5.0.0 || ^6.0.0→^6.4.6 ^6.4.6 ^6.4.66.4.3→6.4.6Astro: Host header SSRF in prerendered error page fetch
CVE-2026-54299 / GHSA-2pvr-wf23-7pc7
More information
Details
Summary
Astro SSR apps with prerendered error pages (
/404or/500usingexport const prerender = true) fetch those pages over HTTP at runtime when an error occurs. The URL for this fetch is derived fromrequest.url, which in turn gets its origin from the incomingHostheader. When theHostheader is not validated againstallowedDomains, an attacker can point the fetch at an arbitrary host and read the response.Who is affected
This affects SSR deployments that:
createRequestFromNodeRequestfromastro/app/nodewithapp.render()without overridingprerenderedErrorPageFetch— this includes custom servers built on the public API and third-party adaptersNot affected:
@astrojs/node>= 9.5.4 (reads error pages from disk)@astrojs/cloudflare(uses the ASSETS binding)How it works
createRequestFromNodeRequestbuildsrequest.urlfrom the rawHost/:authorityheader. TheallowedDomainsoption is accepted but only gatesX-Forwarded-For— it does not constrain the URL origin. (The publiccreateRequestdoes fall back tolocalhostfor unvalidated hosts; this internal builder did not.)When
app.render()encounters a 404 or 500 with a prerendered error route,default-handler.tsconstructs the error page URL using the origin fromrequest.urland fetches it viaprerenderedErrorPageFetch, which defaults to globalfetch. The response body is served to the client.An attacker sends a request with
Host: attacker-host:port, triggers an error (e.g., requesting a nonexistent path for a 404), and receives the response from the attacker-controlled host reflected back.Remediation
The error page fetch origin is now validated against
allowedDomainsbefore use. When the host is validated, the original origin is preserved. Otherwise, it falls back tolocalhost. The fetch is also wrapped in a try/catch so that connection failures degrade gracefully to a plain error response.Credit
5ud0 / Tarmo Technologies
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro: XSS via Unescaped Attribute Names in Spread Props
CVE-2026-54298 / GHSA-jrpj-wcv7-9fh9
More information
Details
Summary
The
spreadAttributesfunction in Astro's server-side rendering pipeline iterates over object keys and passes them directly toaddAttribute, which interpolates the key into the HTML output without escaping. When a developer uses the spread syntax{...props}on an HTML element and the object keys come from an untrusted source (API, CMS, URL parameters), an attacker can inject arbitrary HTML attributes including event handlers likeonmousemove,onclick, or break out of the attribute context entirely to inject new elements.Details
The vulnerable function is
addAttributeatpackages/astro/src/runtime/server/render/util.ts:81-141:This function is called from
spreadAttributesatpackages/astro/src/runtime/server/index.ts:91-92:The
toAttributeStringfunction escapes the attribute value, but the attribute namekeyis never validated or escaped. An attacker can craft a JSON object with a key containing " characters to break out of the attribute context and inject event handlers.Execution flow: User controlled object keys (from API, CMS, URL params) are spread onto element via
{...props}. The compiler generatesspreadAttributes(props)which iterates withObject.entries()and callsaddAttribute(value, key). The key is interpolated as` ${key}="${escapedValue}"`. A malicious key breaks attribute context, resulting in XSS.POC
Create an SSR Astro page (
src/pages/index.astro):Enable SSR in
astro.config.mjs(for URL based demo):Note: SSR is not required for the vulnerability to exist. In static builds (default), the attack vector is compromised data sources at build time (API, CMS, database). SSR simply makes the PoC easier to demonstrate via URL parameters.
Start the dev server and visit:
URL encoded:
View the HTML source. The output contains:
The key
x" onmousemove="alert(document.cookie)" ybreaks out of the attribute context. Moving the mouse over the div executes the JavaScript.Impact
An attacker can execute arbitrary JavaScript in the context of a victim's browser session on any Astro application that spreads object props from untrusted sources onto HTML elements. This is a common pattern when integrating with external APIs or CMS systems. Exploitation enables session hijacking via cookie theft, credential theft by injecting fake login forms or keyloggers, defacement of the rendered page, and redirection to attacker controlled domains.
The vulnerability affects all Astro versions that support spread syntax on HTML elements and is exploitable in SSR, SSG (if build time data is compromised), and hybrid deployments.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
DOM Clobbering Gadget found in astro's client-side router that leads to XSS
CVE-2024-47885 / GHSA-m85w-3h95-hcf9
More information
Details
Summary
A DOM Clobbering gadget has been discoverd in Astro's client-side router. It can lead to cross-site scripting (XSS) in websites enables Astro's client-side routing and has stored attacker-controlled scriptless HTML elements (i.e.,
iframetags with unsanitizednameattributes) on the destination pages.Details
Backgrounds
DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. More for information about DOM Clobbering, here are some references:
[1] https://scnps.co/papers/sp23_domclob.pdf
[2] https://research.securitum.com/xss-in-amp4email-dom-clobbering/
Gadgets found in Astro
We identified a DOM Clobbering gadget in Astro's client-side routing module, specifically in the
<ViewTransitions />component. When integrated, this component introduces the following vulnerable code, which is executed during page transitions (e.g., clicking an<a>link):github.com/withastro/astro@7814a6cad1/packages/astro/src/transitions/router.ts (L135-L156)However, this implementation is vulnerable to a DOM Clobbering attack. The
document.scriptslookup can be shadowed by an attacker injected non-script HTML elements (e.g.,<img name="scripts"><img name="scripts">) via the browser's named DOM access mechanism. This manipulation allows an attacker to replace the intended script elements with an array of attacker-controlled scriptless HTML elements.The condition
script.dataset.astroExec === ''on line 138 can be bypassed because the attacker-controlled element does not have a data-astroExec attribute. Similarly, the check on line 134 can be bypassed as the element does not require atypeattribute.Finally, the
innerHTMLof an attacker-injected non-script HTML elements, which is plain text content before, will be set to the.innerHTMLof an script element that leads to XSS.PoC
Consider a web application using Astro as the framework with client-side routing enabled and allowing users to embed certain scriptless HTML elements (e.g.,
formoriframe). This can be done through a bunch of website's feature that allows users to embed certain script-less HTML (e.g., markdown renderers, web email clients, forums) or via an HTML injection vulnerability in third-party JavaScript loaded on the page.For PoC website, please refer to:
https://stackblitz.com/edit/github-4xgj2d. Clicking the "about" button in the menu will trigger analert(1)from an attacker-injectedformelement.Impact
This vulnerability can result in cross-site scripting (XSS) attacks on websites that built with Astro that enable the client-side routing with
ViewTransitionsand store the user-inserted scriptless HTML tags without properly sanitizing thenameattributes on the page.Patch
We recommend replacing
document.scriptswithdocument.getElementsByTagName('script')for referring to script elements. This will mitigate the possibility of DOM Clobbering attacks leveraging thenameattribute.Reference
Similar issues for reference:
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Atro CSRF Middleware Bypass (security.checkOrigin)
CVE-2024-56140 / GHSA-c4pw-33h3-35xw
More information
Details
Summary
A bug in Astro’s CSRF-protection middleware allows requests to bypass CSRF checks.
Details
When the
security.checkOriginconfiguration option is set totrue, Astro middleware will perform a CSRF check. (Source code:github.com/withastro/astro@6031962ab5/packages/astro/src/core/app/middlewares.ts)For example, with the following Astro configuration:
A request like the following would be blocked if made from a different origin:
However, a vulnerability exists that can bypass this security.
Pattern 1: Requests with a semicolon after the
Content-TypeA semicolon-delimited parameter is allowed after the type in
Content-Type.Web browsers will treat a
Content-Typesuch asapplication/x-www-form-urlencoded; abcas a simple request and will not perform preflight validation. In this case, CSRF is not blocked as expected.Pattern 2: Request without
Content-TypeheaderThe
Content-Typeheader is not required for a request. The following examples are sent without aContent-Typeheader, resulting in CSRF.Impact
Bypass CSRF protection implemented with CSRF middleware.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro's server source code is exposed to the public if sourcemaps are enabled
CVE-2024-56159 / GHSA-49w6-73cw-chjr
More information
Details
Summary
A bug in the build process allows any unauthenticated user to read parts of the server source code.
Details
During build, along with client assets such as css and font files, the sourcemap files for the server code are moved to a publicly-accessible folder.
github.com/withastro/astro@176fe9f113/packages/astro/src/core/build/static-build.ts (L139)Any outside party can read them with an unauthorized HTTP GET request to the same server hosting the rest of the website.
While some server files are hashed, making their access obscure, the files corresponding to the file system router (those in
src/pages) are predictably named. For example. the sourcemap file forsrc/pages/index.astrogets nameddist/client/pages/index.astro.mjs.map.PoC
Here is one example of an affected open-source website:
https://creatorsgarten.org/pages/index.astro.mjs.map
The file can be saved and opened using https://evanw.github.io/source-map-visualization/ to reconstruct the source code.
The above accurately mirrors the source code as seen in the repository: https://github.com/creatorsgarten/creatorsgarten.org/blob/main/src/pages/index.astro
The above was found as the 4th result (and the first one on Astro 5.0+) when making the following search query on GitHub.com (search results link):
This vulnerability is the root cause of https://github.com/withastro/astro/issues/12703, which links to a simple stackblitz project demonstrating the vulnerability. Upon build, notice the contents of the
dist/client(referred to asconfig.build.clientin astro code) folder. All astro servers make the folder in question accessible to the public internet without any authentication. It contains.mapfiles corresponding to the code that runs on the server.Impact
All server-output (SSR) projects on Astro 5 versions v5.0.3 through v5.0.6 (inclusive), that have sourcemaps enabled, either directly or through an add-on such as sentry, are affected. The fix for server-output projects was released in astro@5.0.7.
Additionally, all static-output (SSG) projects built using Astro 4 versions 4.16.17 or older, or Astro 5 versions 5.0.7 or older, that have sourcemaps enabled are also affected. The fix for static-output projects was released in astro@5.0.8, and backported to Astro v4 in astro@4.16.18.
The immediate impact is limited to source code. Any secrets or environment variables are not exposed unless they are present verbatim in the source code.
There is no immediate loss of integrity within the the vulnerable server. However, it is possible to subsequently discover another vulnerability via the revealed source code .
There is no immediate impact to availability of the vulnerable server. However, the presence of an unsafe regular expression, for example, can quickly be exploited to subsequently compromise the availability.
Remediation
The fix for server-output projects was released in astro@5.0.7, and the fix for static-output projects was released in astro@5.0.8 and backported to Astro v4 in astro@4.16.18. Users are advised to update immediately if they are using sourcemaps or an integration that enables sourcemaps.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro allows unauthorized third-party images in _image endpoint
CVE-2025-55303 / GHSA-xf8x-j4p2-f749
More information
Details
Summary
In affected versions of
astro, the image optimization endpoint in projects deployed with on-demand rendering allows images from unauthorized third-party domains to be served.Details
On-demand rendered sites built with Astro include an
/_imageendpoint which returns optimized versions of images.The
/_imageendpoint is restricted to processing local images bundled with the site and also supports remote images from domains the site developer has manually authorized (using theimage.domainsorimage.remotePatternsoptions).However, a bug in impacted versions of
astroallows an attacker to bypass the third-party domain restrictions by using a protocol-relative URL as the image source, e.g./_image?href=//example.com/image.png.Proof of Concept
Create a new minimal Astro project (
astro@5.13.0).Configure it to use the Node adapter (
@astrojs/node@9.1.0— newer versions are not impacted):Build the site by running
astro build.Run the server, e.g. with
astro preview.Append
/_image?href=//placehold.co/600x400to the preview URL, e.g. http://localhost:4321/_image?href=//placehold.co/600x400The site will serve the image from the unauthorized
placehold.coorigin.Impact
Allows a non-authorized third-party to create URLs on an impacted site’s origin that serve unauthorized image content.
In the case of SVG images, this could include the risk of cross-site scripting (XSS) if a user followed a link to a maliciously crafted SVG.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro's
X-Forwarded-Hostis reflected without validationCVE-2025-61925 / GHSA-5ff5-9fcw-vg88
More information
Details
Summary
When running Astro in on-demand rendering mode using a adapter such as the node adapter it is possible to maliciously send an
X-Forwarded-Hostheader that is reflected when using the recommendedAstro.urlproperty as there is no validation that the value is safe.Details
Astro reflects the value in
X-Forwarded-Hostin output when usingAstro.urlwithout any validation.It is common for web servers such as nginx to route requests via the
Hostheader, and forward on other request headers. As such as malicious request can be sent with both aHostheader and anX-Forwarded-Hostheader where the values do not match and theX-Forwarded-Hostheader is malicious. Astro will then return the malicious value.This could result in any usages of the
Astro.urlvalue in code being manipulated by a request. For example if a user follows guidance and usesAstro.urlfor a canonical link the canonical link can be manipulated to another site. It is not impossible to imagine that the value could also be used as a login/registration or other form URL as well, resulting in potential redirecting of login credentials to a malicious party.As this is a per-request attack vector the surface area would only be to the malicious user until one considers that having a caching proxy is a common setup, in which case any page which is cached could persist the malicious value for subsequent users.
Many other frameworks have an allowlist of domains to validate against, or do not have a case where the headers are reflected to avoid such issues.
PoC
nvm useyarn run buildnode ./dist/server/entry.mjscurl --location 'http://localhost:4321/' --header 'X-Forwarded-Host: www.evil.com' --header 'Host: www.example.com'X-Forwarded-HostheaderFor the more advanced / dangerous attack vector deploy the application behind a caching proxy, e.g. Cloudflare, set a non-zero cache time, perform the above
curlrequest a few times to establish a cache, then perform the request without the malicious headers and observe that the malicious data is persisted.Impact
This could affect anyone using Astro in an on-demand/dynamic rendering mode behind a caching proxy.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro Development Server has Arbitrary Local File Read
CVE-2025-64757 / GHSA-x3h8-62x9-952g
More information
Details
Summary
A vulnerability has been identified in the Astro framework's development server that allows arbitrary local file read access through the image optimization endpoint. The vulnerability affects Astro development environments and allows remote attackers to read any image file accessible to the Node.js process on the host system.
Details
/packages/astro/src/assets/endpoint/node.tsThe vulnerability exists in the Node.js image endpoint handler used during development mode. The endpoint accepts an
hrefparameter that specifies the path to an image file. In development mode, this parameter is processed without adequate path validation, allowing attackers to specify absolute file paths.Vulnerable Code Location:
packages/astro/src/assets/endpoint/node.tsThe development branch bypasses the security checks that exist in the production code path, which validates that file paths are within the allowed assets directory.
PoC
Attack Prerequisites
astro dev)/_imageendpoint must be accessible to the attackerExploit Steps
Start Astro Development Server:
Craft Malicious Request:
Example Attack:
Demonstration Results
Test Environment: macOS with Astro v5.13.3
Successful Exploitation:
/System/Library/Image Capture/Automatic Tasks/MakePDF.app/Contents/Resources/0blank.jpgstolen-image.pngcontaining processed system imageAttack Payload:
Server Response:
Impact
Confidentiality Impact: HIGH
Integrity Impact: NONE
Availability Impact: NONE
Affected Components
Primary Component
packages/astro/src/assets/endpoint/node.tsloadLocalImage()Secondary Components
packages/astro/src/assets/endpoint/generic.tsSeverity
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro vulnerable to URL manipulation via headers, leading to middleware and CVE-2025-61925 bypass
CVE-2025-64525 / GHSA-hr2q-hp5q-x767
More information
Details
Summary
In impacted versions of Astro using on-demand rendering, request headers
x-forwarded-protoandx-forwarded-portare insecurely used, without sanitization, to build the URL. This has several consequences the most important of which are:x-forwarded-proto)x-forwarded-proto)Details
The
x-forwarded-protoandx-forwarded-portheaders are used without sanitization in two parts of the Astro server code. The most important is in thecreateRequest()function. Any configuration, including the default one, is affected:https://github.com/withastro/astro/blob/970ac0f51172e1e6bff4440516a851e725ac3097/packages/astro/src/core/app/node.ts#L97
https://github.com/withastro/astro/blob/970ac0f51172e1e6bff4440516a851e725ac3097/packages/astro/src/core/app/node.ts#L121
These header values are then used directly to construct URLs.
By injecting a payload at the protocol level during URL creation (via the
x-forwarded-protoheader), the entire URL can be rewritten, including the host, port and path, and then pass the rest of the URL, the real hostname and path, as a query so that it doesn't affect (re)routing.If the following header value is injected when requesting the path
/ssr:The complete URL that will be created is:
https://www.malicious-url.com/?tank=://localhost/ssrAs a reminder, URLs are created like this:
The value is injected at the beginning of the string (
${protocol}), and ends with a query?tank=whose value is the rest of the string,://${hostnamePort}${req.url}.This way there is control over the routing without affecting the path, and the URL can be manipulated arbitrarily. This behavior can be exploited in various ways, as will be seen in the PoC section.
The same logic applies to
x-forwarded-port, with a few differences.PoC
The PoC will be tested with a minimal repository:
2.16.0)/ssr), the other simulating an admin page (/admin) protected by a middlewareDownload the PoC repository
Middleware-based protected route bypass - x-forwarded-proto only
The middleware has been configured to protect the
/adminroute based on the official documentation:When tryint to access
/adminthe attacker is naturally redirected :The attackr can bypass the middleware path check using a malicious header value:
How is this possible?
Here, with the payload
x:admin?, the attacker can use the URL API parser to their advantage:x:is considered the protocol//, the parser considers there to be no authority, and everything before the?character is therefore considered part of the path:adminDuring a path-based middleware check, the path value begins with a
/:context.url.pathname === "/admin". However, this is not the case with this payload;context.url.pathname === "admin", the absence of a slash satisfies both the middleware check and the router and consequently allows us to bypass the protection and access the page.SSRF
As seen, the request URL is built from untrusted input via the
x-forwarded-protocolheader, if it turns out that this URL is subsequently used to perform external network calls, for an API for example, this allows an attacker to supply a malicious URL that the server will fetch, resulting in server-side request forgery (SSRF).Example of code reusing the "origin" URL, concatenating it to the API endpoint :
DoS via cache poisoning
If a CDN is present, it is possible to force the caching of bad pages/resources, or 404 pages on the application routes, rendering the application unusable.
A

404cab be forced, causing an error on the/ssrpage like this :curl -i -H "x-forwarded-proto: https://localhost/vulnerable?" http://localhost:4321/ssrSame logic applies to
x-forwarded-port:curl -i -H "x-forwarded-port: /vulnerable?" http://localhost:4321/ssrHow is this possible?
The router sees the request for the path
/vulnerable, which does not exist, and therefore returns a404, while the potential CDN sees/ssrand can then cache the404response, consequently serving it to all users requesting the path/ssr.URL pollution
The exploitability of the following is also contingent on the presence of a CDN, and is therefore cache poisoning.
If the value of
request.urlis used to create links within the page, this can lead to Stored XSS withx-forwarded-protoand the following value:results in the following URL object:
It is also possible to inject any link, always, if the value of
request.urlis used on the server side to create links.The attacker is more limited with
x-forwarded-portIf the value of
request.urlis used to create links within the page, this can lead to broken links, with the header and the following value:Example of an Astro website:

WAF bypass
For this section, Astro invites users to read previous research on the React-Router/Remix framework, in the section "Exploitation - WAF bypass and escalations". This research deals with a similar case, the difference being that the vulnerable header was
x-forwarded-hostin their case:https://zhero-web-sec.github.io/research-and-things/react-router-and-the-remixed-path
Note: A section addressing DoS attacks via cache poisoning using the same vector was also included there.
CVE-2025-61925 complete bypass
It is possible to completely bypass the vulnerability patch related to the
X-Forwarded-Hostheader.By sending
x-forwarded-hostwith an empty value, theforwardedHostnamevariable is assigned an empty string. Then, during the subsequent check, the condition fails becauseforwardedHostnamereturnsfalse, its value being an empty string:Consequently, the implemented check is bypassed. From this point on, since the request has no
host(its value being an empty string), the path value is retrieved by the URL parser to set it as thehost. This is because thehttp/httpsschemes are considered special schemes by the WHATWG URL Standard Specification, requiring anauthority state.From there, the following request on the example SSR application (astro repo) yields an SSRF:

empty
x-forwarded-host+ the targethostin the pathCredits
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro's middleware authentication checks based on url.pathname can be bypassed via url encoded values
CVE-2025-64765 / GHSA-ggxq-hp9w-j794
More information
Details
A mismatch exists between how Astro normalizes request paths for routing/rendering and how the application’s middleware reads the path for validation checks. Astro internally applies
decodeURI()to determine which route to render, while the middleware usescontext.url.pathnamewithout applying the same normalization (decodeURI).This discrepancy may allow attackers to reach protected routes (e.g., /admin) using encoded path variants that pass routing but bypass validation checks.
github.com/withastro/astro@ebc4b1cde8/packages/astro/src/vite-plugin-astro-server/request.ts (L40-L44)Consider an application having the following middleware code:
context.url.pathnameis validated , if it's equal to/admintheisAuthedproperty must be true for the next() method to be called. The same example can be found in the official docs https://docs.astro.build/en/guides/authentication/context.url.pathnamereturns the raw version which is/%61adminwhile pathname which is used for routing/rendering/admin, this creates a path normalization mismatch.By sending the following request, it's possible to bypass the middleware check
Remediation
Ensure middleware context has the same normalized pathname value that Astro uses internally, because any difference could allow it to bypass such checks. In short maybe something like this
Thank you, let @Sudistark know if any more info is needed. Happy to help :)
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro has an Authentication Bypass via Double URL Encoding, a bypass for CVE-2025-64765
CVE-2025-66202 / GHSA-whqg-ppgf-wp8c
More information
Details
Authentication Bypass via Double URL Encoding in Astro
Bypass for CVE-2025-64765 / GHSA-ggxq-hp9w-j794
Summary
A double URL encoding bypass allows any unauthenticated attacker to bypass path-based authentication checks in Astro middleware, granting unauthorized access to protected routes. While the original CVE-2025-64765 (single URL encoding) was fixed in v5.15.8, the fix is insufficient as it only decodes once. By using double-encoded URLs like
/%2561dmininstead of/%61dmin, attackers can still bypass authentication and access protected resources such as/admin,/api/internal, or any route protected by middleware pathname checks.Fix
A more secure fix is just decoding once, then if the request has a %xx format, return a 400 error by using something like :
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro vulnerable to reflected XSS via the server islands feature
CVE-2025-64764 / GHSA-wrwg-2hg8-v723
More information
Details
Summary
After some research it appears that it is possible to obtain a reflected XSS when the server islands feature is used in the targeted application, regardless of what was intended by the component template(s).
Details
Server islands run in their own isolated context outside of the page request and use the following pattern path to hydrate the page:
/_server-islands/[name]. These paths can be called via GET or POST and use three parameters:e: component to exportp: the transmitted properties, encrypteds: for the slotsSlots are placeholders for external HTML content, and therefore allow, by default, the injection of code if the component template supports it, nothing exceptional in principle, just a feature.
This is where it becomes problematic: it is possible, independently of the component template used, even if it is completely empty, to inject a slot containing an XSS payload, whose parent is a tag whose name is is the absolute path of the island file. Enabling reflected XSS on any application, regardless of the component templates used, provided that the server islands is used at least once.
How ?
By default, when a call is made to the endpoint
/_server-islands/[name], the value of the parametereisdefault, pointing to a function exported by the component's module.Upon further investigation, we find that two other values are possible for the component export (param
e) in a typical configuration:urlandfile.filereturns a string value corresponding to the absolute path of the island file. Since the value is of typestring, it fulfills the following condition and leads to this code block:An entire template is created, completely independently, and then returned:
childSlots, the value provided to thesparameter, is injected as a childAll of this is done using
markHTMLString. This allows the injection of any XSS payload, even if the component template intended by the application is initially empty or does not provide for the use of slots.Proof of concept
For our Proof of Concept (PoC), we will use a minimal repository:
Download the PoC repository
Access the following URL and note the opening of the popup, demonstrating the reflected XSS:
http://localhost:4321/_server-islands/ServerTime?e=file&p=&s={%22zhero%22:%22%3Cimg%20src=x%20onerror=alert(0)%3E%22}
The value of the parameter
smust be in JSON format and the payload must be injected at the value level, not the key level :Despite the initial template being empty, it is created because the value of the URL parameter
eis set tofile, as explained earlier. The parent tag is the name of the component's internal route, and its child is the value of the key "zhero" (the name doesn't matter) of the URL parameters.Credits
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro Cloudflare adapter has Stored Cross-site Scripting vulnerability in /_image endpoint
CVE-2025-65019 / GHSA-fvmw-cj7j-j39q
More information
Details
Summary
A Cross-Site Scripting (XSS) vulnerability exists in Astro when using the @astrojs/cloudflare adapter with
output: 'server'. The built-in image optimization endpoint (/_image) usesisRemoteAllowed()from Astro’s internal helpers, which unconditionally allowsdata:URLs. When the endpoint receives a validdata:URL pointing to a malicious SVG containing JavaScript, and the Cloudflare-specific implementation performs a 302 redirect back to the originaldata:URL, the browser directly executes the embedded JavaScript. This completely bypasses any domain allow-listing (image.domains/image.remotePatterns) and typical Content Security Policy mitigations.Affected Versions
@astrojs/cloudflare≤ 12.6.10 (and likely all previous versions)output: 'server'and the Cloudflare adapterRoot Cause – Vulnerable Code
File:
node_modules/@​astrojs/internal-helpers/src/remote.tsIn the Cloudflare adapter, the
/_imageendpoint contains logic similar to:Because
data:URLs are considered “allowed”, a request such as:https://example.com/_image?href=data:image/svg+xml;base64,PHN2Zy... (base64-encoded malicious SVG)triggers a 302 redirect directly to the
data:URL, causing the browser to render and execute the malicious JavaScript inside the SVG.Proof of Concept (PoC)
output: 'server').(Base64 decodes to:
<svg xmlns="http://www.w3.org/2000/svg"><script>alert('zomasec')</script></svg>)data:URL → browser executes the<script>→alert()fires.Impact
image.domains/image.remotePatternsconfiguration entirelySafe vs Vulnerable Behavior
Other Astro adapters (Node, Vercel, etc.) typically proxy and rasterize SVGs, stripping JavaScript. The Cloudflare adapter currently redirects to remote resources (including
data:URLs), making it uniquely vulnerable.References
data:URL bypass in WordPress: CVE-2025-2575Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro: Remote allowlist bypass via unanchored matchPathname wildcard
CVE-2026-33769 / GHSA-g735-7g2w-hh3f
More information
Details
Summary
This issue concerns Astro's
remotePatternspath enforcement for remote URLs used by server-side fetchers such as the image optimization endpoint. The path matching logic for/*wildcards is unanchored, so a pathname that contains the allowed prefix later in the path can still match. As a result, an attacker can fetch paths outside the intended allowlisted prefix on an otherwise allowed host. In our PoC, both the allowed path and a bypass path returned 200 with the same SVG payload, confirming the bypass.Impact
Attackers can fetch unintended remote resources on an allowlisted host via the image endpoint, expanding SSRF/data exposure beyond the configured path prefix.
Description
Taint flow: request ->
transform.src->isRemoteAllowed()->matchPattern()->matchPathname()User-controlled
hrefis parsed intotransform.srcand validated viaisRemoteAllowed():Source:
github.com/withastro/astro@e0f1a2b3e4/packages/astro/src/assets/endpoint/generic.ts (L43-L56)isRemoteAllowed()checks eachremotePatternviamatchPattern():Source:
github.com/withastro/astro@e0f1a2b3e4/packages/internal-helpers/src/remote.ts (L15-L21)The vulnerable logic in
matchPathname()usesreplace()without anchoring the prefix for/*patterns:Source:
github.com/withastro/astro@e0f1a2b3e4/packages/internal-helpers/src/remote.ts (L85-L99)Vulnerable code flow:
isRemoteAllowed()evaluatesremotePatternsfor a requested URL.matchPathname()handlespathname: "/img/*"using.replace()on the URL path./evil/img/secretincorrectly matches because/img/is removed even when it's not at the start.PoC
The PoC starts a local attacker server and configures remotePatterns to allow only
/img/*. It then requests the image endpoint with two URLs: an allowed path and a bypass path with/img/in the middle. Both requests returned the SVG payload, showing the path restriction was bypassed.Vulnerable config
Affected pages
This PoC targets the
/_imageendpoint directly; no additional pages are required.PoC Code
Attacker server
PoC Steps
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro: XSS in define:vars via incomplete tag sanitization
CVE-2026-41067 / GHSA-j687-52p2-xcff
More information
Details
Summary
The
defineScriptVarsfunction in Astro's server-side rendering pipeline uses a case-sensitive regex/<\/script>/gto sanitize values injected into inline<script>tags via thedefine:varsdirective. HTML parsers close<script>elements case-insensitively and also accept whitespace or/before the closing>, allowing an attacker to bypass the sanitization with payloads like</Script>,</script >, or</script/>and inject arbitrary HTML/JavaScript.Details
The vulnerable function is
defineScriptVarsatpackages/astro/src/runtime/server/render/util.ts:42-53:This function is called from
renderElementatutil.ts:172-174when a<script>element hasdefine:vars:The regex
/<\/script>/gfails to match three classes of closing script tags that HTML parsers accept per the HTML specification §13.2.6.4:</Script>,</SCRIPT>,</sCrIpT>— HTML tag names are case-insensitive but the regex has noiflag.>:</script >,</script\t>,</script\n>— after the tag name, the HTML tokenizer enters the "before attribute name" state on ASCII whitespace.</script/>— the tokenizer enters "self-closing start tag" state on/.JSON.stringify()does not escape<,>, or/characters, so all these payloads pass through serialization unchanged.Execution flow: User-controlled input (e.g.,
Astro.url.searchParams) → assigned to a variable → passed viadefine:varson a<script>tag →renderElement→defineScriptVars→ incomplete sanitization → injected into<script>block in HTML response → browser closes the script element early → attacker-controlled HTML parsed and executed.PoC
Step 1: Create an SSR Astro page (
src/pages/index.astro):Step 2: Ensure SSR is enabled in
astro.config.mjs:Step 3: Start the dev server and visit:
Step 4: View the HTML source. The output contains:
The browser's HTML parser matches
</Script>case-insensitively, closing the script block. The<img onerror=alert(document.cookie)>is then parsed as HTML and the JavaScript inonerrorexecutes.Alternative bypass payloads:
Impact
An attacker can execute arbitrary JavaScript in the context of a victim's browser session on any SSR Astro application that passes request-derived data to
define:varson a<script>tag. This is a documented and expected usage pattern in Astro.Exploitation enables:
document.cookie)The vulnerability affects all Astro versions that support
define:varsand is exploitable in any SSR deployment where user input reaches adefine:varsscript variable.Recommended Fix
Replace the case-sensitive exact-match regex with a comprehensive escape that covers all HTML parser edge cases. The simplest correct fix is to escape all
<characters in the JSON output:This is the standard approach used by frameworks like Next.js and Rails. Replacing every
<with\u003cis safe inside JSON string contexts (JavaScript treats\u003cas<at runtime) and eliminates all possible</script>variants including case variations, whitespace, and self-closing forms.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro: Server island encrypted parameters vulnerable to cross-component replay
CVE-2026-45028 / GHSA-xr5h-phrj-8vxv
More information
Details
Impact
Astro versions prior to 6.1.10 used AES-GCM encryption to protect the confidentiality and integrity of server island props and slots parameters, but did not bind the ciphertext to its intended component or parameter type. An attacker could replay one component's encrypted props (
p) value as another component's slots (s) value, or vice versa.Since slots contain raw unescaped HTML while props may contain user-controlled values, this could lead to XSS in applications that meet all of the following conditions:
These conditions are very unlikely to occur in real-world production applications.
Patches
This has been patched in astro@6.1.10.
The fix binds each encrypted parameter to its target component and purpose using AES-GCM authenticated additional data (AAD). Each ciphertext now includes context like
props:IslandNameorslots:IslandName, so encrypted data for one component cannot be replayed against a different component, and encrypted props cannot be reused as slots.References
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:PReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Astro: Reflected XSS via unescaped slot name
CVE-2026-50146 / GHSA-8hv8-536x-4wqp
More information
Details
Summary
When a component uses a
client:*directive, Astro inserts named slot content into adata-astro-templateattribute without HTML escaping the slot name allowing an attacker to break out of the attribute context and inject arbitrary HTML, resulting in reflected XSS during SSR.This is similar to GHSA-wrwg-2hg8-v723 but exploits a different injection point.
Vulnerable Code
packages/astro/src/runtime/server/render/component.ts:371:376I found that key is interpolated directly into the attribute value without proper escaping.
Proof of Concept
For the PoC, I set up with a minimal repository with Astro 6.3.1, Node.js: v26.0.0.
astro.config.mjssrc/pages/index.astrosrc/components/Wrapper.jsxPayload:
Accessing this URL will trigger the popup.
http://localhost:4321/?tab=abc%22%3E%3C%2Ftemplate%3E%3C%2Fastro-island%3E%3Cimg+src%3Dx+onerror%3Dconfirm(document.domain)%3E%3C!--
This will render in html.
Fix
I suggest leveraging the existing escape function on the slot name.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
withastro/astro (astro)
v6.4.6Compare Source
Patch Changes
#16765
b10e86eThanks @fkatsuhiro! - Fixes an issue where renaming an image file while the dev server is running triggers a build error. Now Astro correctly hot-reloads the image without crashing.#17026
add3df1Thanks @matthewp! - HardensaddAttributeto drop attribute names containing characters that are invalid per the HTML spec (",',>,/,=, whitespace)#17033
ffda27bThanks @matthewp! - Validates the request origin againstallowedDomainsbefore fetching prerendered error pages. WhenallowedDomainsis configured and the Host header matches, the original origin is used. Otherwise, the fetch falls back tolocalhost.v6.4.5Compare Source
Patch Changes
#16985
4ecff32Thanks @maximslo! - Fixes theexperimental.loggerdestination not being used for the "Server listening on..." startup message. The logger is now resolved before the server starts listening, andadapterLoggerre-creates itself when the underlying logger changes so the startup message uses the correct destination.#16947
e0703a6Thanks @ematipico! - FixesAstro.request.urlnot reflecting validatedX-Forwarded-Proto/X-Forwarded-Hostheaders whensecurity.allowedDomainsis configured. Previously, onlyAstro.urlwas updated with the forwarded origin whileAstro.request.urlretained the socket-derived URL, causing the two to diverge behind TLS-terminating proxies.#16997
dc45246Thanks @matthewp! - Reverts a change toisNoderuntime detection that caused a significant build time regression for Cloudflare adapter users with large prerendered sitesv6.4.4Compare Source
Patch Changes
#16926
1b39ae8Thanks @narendraio! - PreventsApp.match()from throwing on request paths that contain an invalid percent-sequence.#16924
2c0bc94Thanks @astrobot-houston! - Fixes an issue where editing a client-side component (e.g. withclient:idle,client:load, etc.) caused an unnecessary full program reload of the backend during development.#16958
2c1d50fThanks @fkatsuhiro! - Fixes a bug where static file endpoints usinggetStaticPathswith.htmlin dynamic param values (e.g.{ path: 'file.html' }) would fail with aNoMatchingStaticPathFounderror during build. The.htmlsuffix is no longer incorrectly stripped from endpoint route pathnames.#16855
c610cdaThanks @astrobot-houston! - Fixes dynamic routes returning 500 "TypeError: Missing parameter" when using domain-based i18n routing in SSR.#16946
606c37bThanks @ematipico! - FixesAstro.routePatternto preserve original casing of dynamic parameter names from filenames. Previously, a file atsrc/pages/blog/[postId].astrowould return/blog/[postid]forAstro.routePatterndue to an internal.toLowerCase()call. It now correctly returns/blog/[postId].#16720
16d49b6Thanks @thomas-callahan-collibra! - Fix an issue where dynamic routes would return the string[object Object]instead of the expected content, in certain runtimes.#16703
17390a6Thanks @henrybrewer00-dotcom! - Fixes styles being stripped when the project root is started with a path whose case differs from the actual filesystem case (e.g. runningastro devfromd:\dev\appwhile the folder on disk isD:\dev\app).#16855
c610cdaThanks @astrobot-houston! - FixesAstro.currentLocalereturning the default locale instead of the domain's locale on dynamic routes served from a mapped domain.v6.4.3Compare Source
Patch Changes
#16900
17a0fbdThanks @ocavue! - Bumpsdevaluedependency to v5.8.1#16016
0d85e1bThanks @felmonon! - Fix a false positive in the dev toolbar accessibility audit for anchors with text inside closed<details>elements.#16911
79c6c46Thanks @astrobot-houston! - Fixes a bug whereexperimental.advancedRoutingwithastro/honohandlers threwTypeError: Cannot read properties of undefined (reading 'route')for unmatched routes instead of rendering the custom 404 page.#16899
239c469Thanks @matthewp! - Fixes a false "does not call the middleware() handler" warning when usingastro()in a customsrc/app.tsand the first request is a redirect route.#16887
493acdbThanks @astrobot-houston! - FixesredirectToDefaultLocalenot working after the Advanced Routing refactoring.#16908
ef53ab9Thanks @florian-lefebvre! - Improves optimized fallbacks generation when using the Fonts API by using better metrics for bold variantsv6.4.2Patch Changes
#16889
b94bcfdThanks @Princesseuh! - Fixes aplugins is not iterablecrash when using a pre-6.0@astrojs/mdxalongside integrations (e.g. Starlight) that setmarkdown.remarkPlugins,markdown.rehypePlugins, ormarkdown.remarkRehype.#16878
b9f6bb9Thanks @fkatsuhiro! - Fixes an issue where on-demand (SSR) dynamic routes would return 404 when a prerendered dynamic route with the same URL pattern was sorted first alphabetically. In production builds with@astrojs/nodeadapter, if[a_prebuild].astro(prerender=true) came before[b_ssr].astroalphabetically, requests to URLs not in the prerendered route's static paths would 404 instead of falling through to the SSR route. The fix adds fallthrough logic so that when a prerendered dynamic route matches but can't serve the request, Astro tries subsequent matching routes.v6.4.1Patch Changes
eeb064cThanks @Princesseuh! - Restores theastro/jsx/rehype.jsentry point so that older versions of@astrojs/mdxcontinue to work when used with Astro 6.x. This entry point will be removed in Astro 7.0.v6.4.0Compare Source
Minor Changes
#16468
4cff3a1Thanks @matthewp! - Adds a newpreserveBuildServerDiradapter featureAdapters can now set
preserveBuildServerDir: truein their adapter features to keep thedist/server/directory structure for static builds, mirroring the existingpreserveBuildClientDiroption. This is useful for adapters that require a consistentdist/client/anddist/server/layout regardless of build output type.#16848
f732f3cThanks @Princesseuh! - Adds a newmarkdown.processorconfiguration option, allowing you to choose an alternative Markdown processor.Websites with many Markdown/MDX files tend to be slow to build because the unified ecosystem (e.g., remark, rehype) is slow to process. This feature introduces the ability to replace this part of the build pipeline with another processor.
The default processor is
unified(). This means that existing configurations remain unchanged and your remark/rehype plugins continue to work.In addition to this new configuration option, Astro provides a new alternative processor based on Rust: Sätteri. You can choose to use it now by installing
@astrojs/markdown-satteri, importing thesatteri()processor, and adapting your existing configuration:This processor does not support the remark and rehype plugins. This means you may need to convert them to MDAST or HAST plugins to retain your current functionality.
The existing top-level
markdown.remarkPlugins,markdown.rehypePlugins,markdown.remarkRehype,markdown.gfm, andmarkdown.smartypantsoptions still work, but are now deprecated and will be removed in a future major update. The matchingremarkPlugins,rehypePlugins, andremarkRehypeoptions on the MDX integration are also deprecated for the same reason. To anticipate their removal, move them ontounified({...})(or your preferred plugin processor) :For more information on enabling and using this feature in your project, see our Markdown guide. To give feedback on this new Rust processor, see the Native Markdown / MDX parsing and processing RFC.
Patch Changes
#16468
4cff3a1Thanks @matthewp! - Skips the static preview server when an adapter provides its ownpreviewEntrypoint, allowing the adapter to handle both static and dynamic routes#16811
e0e26dbThanks @matthewp! - FixesX-Forwarded-HostandX-Forwarded-Protoheaders being ignored when set in a customsrc/app.tsfetch handler before creatingFetchState#16468
4cff3a1Thanks @matthewp! - Fixes the static preview server to respectpreserveBuildClientDir, serving files frombuild.clientinstead ofoutDirwhen the adapter requires it#16770
1e2aa11Thanks @matthewp! - Fixes a race condition where the Vite dep optimizer could lose React dependencies in dev mode when using Astro Actions#16468
4cff3a1Thanks @matthewp! - Exempts internal routes (e.g. server islands) fromgetStaticPaths()validation, fixing server island rendering on static sites#16468
4cff3a1Thanks @matthewp! - Fixes preview for static sites that contain non-prerendered routes. Previously, the preview command ignored SSR routes discovered during route scanning and always used the static preview server.Updated dependencies [
f732f3c,f732f3c]:v6.3.8Compare Source
Patch Changes
#16830
f2bf3cbThanks @matthewp! - Fixes 404s for dynamically imported JS chunks when using an adapter withassetQueryParams(e.g. Vercel skew protection)#16831
ace96baThanks @astrobot-houston! - Fixes a misleadingGetStaticPathsRequirederror when a redirect is configured from a dynamic route to a static (or less-dynamic) destination. For example,'/project/[slug]': '/'previously produced a confusing error pointing atindex.astro. Astro now detects the parameter mismatch at config validation time and throws a clearInvalidRedirectDestinationerror naming the missing parameters.#16702
b7d1758Thanks @matthewp! - Fixes scoped styles from.astrocomponents being dropped when rendered inside MDX content (<Content />fromrender(entry)) passed through a named slot using<Fragment slot="X">. The Fragment component now eagerly evaluates its slot contents to ensure propagating components register their styles before head content is flushed.#16823
3df6a45Thanks @astrobot-houston! - Fixes missing CSS for conditionally rendered Svelte components in production builds#16836
3d7adfaThanks @LongYC! - Document compressHTML: "jsx" config is only available since Astro v6.2.0#16864
334ce13Thanks @cheets! - Fixes a false-positiveInternal Warning: route cache overwrittenlogged on every SSR request for dynamic routesv6.3.7Compare Source
Patch Changes
#16821
9c76b12Thanks @astrobot-houston! - Fixes request body handling in the Node adapter whenreq.bodyis aBuffer,Uint8Array, orArrayBuffer. Previously, binary body data was incorrectly JSON-stringified (producing{"type":"Buffer","data":[...]}) instead of being passed through directly. This affected libraries likeserverless-httpthat setreq.bodyto aBuffer.#16785
de96360Thanks @astrobot-houston! - Fixesvite.build.minify,vite.build.sourcemap, andvite.build.rollupOptions.output(e.g.compact) being ignored for client-side builds. These top-level Vite build options are now properly forwarded to the client environment, with environment-specific overrides (vite.environments.client.build.*) taking priority when set.#16819
b5dd8f1Thanks @astrobot-houston! - Fixes custom elements in MDX files bypassing the renderer pipeline. Custom elements (tags containing hyphens like<my-element>) in.mdxfiles are now routed through registered renderers for SSR, matching the behavior of.astrofiles. If no renderer claims the element, it falls back to rendering as raw HTML.#16808
765896cThanks @ematipico! - Fixes dynamic routes returning 400 Bad Request when the URL contains a literal%character, such as paths built withencodeURIComponent('%?.pdf')#16804
90d2acaThanks @jp-knj! - Fixes a v6 regression whereastro:i18ncould not be imported from client<script>blocks.v6.3.6Compare Source
Patch Changes
#16774
8f77583Thanks @astrobot-houston! - Fixes markdown images with empty alt text () in content collections dropping thealtattribute entirely. Thealt=""attribute is now correctly preserved in the rendered HTML output, which is important for accessibility (indicating decorative images).#16776
3d10b5eThanks @matthewp! - Fixes HMR serving stale content when components are passed as props viagetStaticPaths()#16784
7453860Thanks @ematipico! - Improved the printing of the build time if it goes over the 60 seconds.#16665
3dbbceeThanks @Princesseuh! - Fixes remote SVG sources erroring withdangerouslyProcessSVGafter the v6.3 SVG-processing gate. The default Sharp service now resolves the output format from the source up-front when it can (URL extension,data:MIME, ESM metadata), and from the actual buffer at request time when it can't, so SVG sources pass through untouched without needing to setimage.dangerouslyProcessSVG: trueor an explicitformat="svg".The error message has also been updated to point at
format="svg"as the simpler workaround when an SVG source is encountered withoutdangerouslyProcessSVGenabled.#16777
1754b91Thanks @matthewp! - Fixes HMR serving stale content for dynamically imported components through barrel files#16730
068d924Thanks @harshagarwalnyu! - Fixes an issue where thefile()content loader did not generate a valid JSON Schema for collections whose JSON or YAML data is a top-level array instead of an object.v6.3.5Compare Source
Patch Changes
#16771
07c8805Thanks @ematipico! - Fixespositionprop on<Image>and<Picture>components breaking Content Security Policy (CSP).#16593
50924ceThanks @yanthomasdev! - Improves error messages with more consistent and correct writing.#16757
5d661cdThanks @astrobot-houston! - Fixes dev server serving stale content when SSR-only modules change (e.g..astrofiles outside the project root in a monorepo, or dynamically imported components).Previously, the
astro:hmr-reloadplugin returned an empty array after detecting SSR-only module changes, which prevented Vite'supdateModulesfrom propagating the invalidation to the SSR module runner. The runner's evaluated module cache stayed stale, so subsequent requests continued returning old content.Now the plugin returns the SSR-only modules so Vite can process them through
updateModules, which properly invalidates the module runner's cache and ensures fresh content on the next request.v6.3.4Compare Source
Patch Changes
#16723
0f10bfeThanks @matthewp! - AddsfetchFileoption toexperimental.advancedRoutingto customize or disable the entrypoint file#16723
0f10bfeThanks @matthewp! - Fixes Honocache()middleware to follow the standard wrapper pattern#16723
0f10bfeThanks @matthewp! - AddsApp.Providersinterface for typing custom context providers onAstroandctx#16723
0f10bfeThanks @matthewp! - AddsFetchState.responseproperty, set automatically afterpages()ormiddleware()completes#16723
0f10bfeThanks @matthewp! - AddsFetchabletype export for typing the advanced routing entrypoint#16572
4a5a077Thanks @DORI2001! - Suppresses[WARN] Vite warning: unused imports from "@​astrojs/internal-helpers/remote"during prerender builds. The package is now bundled alongsideastroin the prerender environment, matching how it is handled in the SSR environment.#16756
b6ee23dThanks @astrobot-houston! - Fixes styles from Markdoc/MDX custom components not being extracted to<head>in the dev server when using the Cloudflare adapter withprerenderEnvironment: 'node'and rendering content through a wrapper component.#16747
904d19aThanks @astrobot-houston! - Fixes Astro action requests failing inastro devwhen using the Cloudflare adapter withprerenderEnvironment: 'node'alongside a prerendered catch-all route such as[...page].astro.Actions and other SSR POST endpoints now continue to work in dev instead of returning an HTTP 500 error.
#16701
3495ce4Thanks @demaisj! - FixMapandSetinstances saved in a content collection being broken when retrieving entries.#16614
fca1c32Thanks @Eptagone! - Fixesentry.datatype inference when a live collection is configured without a schema.#16661
03b8f7fThanks @ocavue! - Updatestypescriptto v6. No changes are needed from users.#16681
c22770aThanks @dotnetCarpenter! - Fixes an issue where SVG images withwidth="0"orheight="0"incorrectly threw aNoImageMetadataerror instead of being treated as valid dimensions.v6.3.3Compare Source
Patch Changes
bd84f33Thanks @matthewp! - Fixes a reflected XSS vulnerability where slot names on hydrated components were not HTML-escaped in SSR outputv6.3.2Compare Source
Patch Changes
#16675
11d4592Thanks @ascorbic! - Fixes a regression whereAstro.cachewasundefinedwhenexperimental.cachewas not configured.The previous documented behavior is for
Astro.cacheto always be defined as a no-op shim:cache.set()warns once,cache.invalidate()throws andcache.enabledcan be used to gate. This allows library and user code can call cache methods without conditional checks. The cache provider registration was being gated at the call site onexperimental.cachebeing configured, which meant the disabled shim branch inside the provider was unreachable and theAstro.cachegetter was never attached to the context.#16691
0f0a4ceThanks @matthewp! - FixesHTMLElement is not definederror during HMR when using components with client-side scripts (e.g. Starlight<Tabs>) and the Cloudflare adapter#16562
07529ecThanks @matthewp! - Fixes non-prerendered routes failing when a dynamic prerendered route exists in the same project withprerenderEnvironment: 'node'#16638
272185bThanks @ematipico! - Fixes a bug where the Astro compiler wasn't freed at the end of the build. After the fix, the memory used by the compiler is now correctly freed at the end of the build.#16544
d365c97Thanks @matthewp! - TightensisRemotePath()to reject control characters after a leading slash and fixes the dev image endpoint origin check#16685
889e748Thanks @farrosfr! - Improve validation messages forsecurity.csp.directiveswhenscript-srcorstyle-srcare incorrectly placed in thedirectivesarray.#16605
772f13aThanks @rururux! - FixesassetsPrefixnot being available onbuildfromastro:config/server.#16556
f38dec7Thanks @matthewp! - Rejects double-encoded URL paths with a 400 response instead of silently falling back to partial decoding#16659
38bcb25Thanks @jsparkdev! - Fixes&characters appearing as raw entity strings (e.g.&#​38;) in<meta>tags when viewed in link previews or raw HTML.Updated dependencies [
d365c97,9256345]:v6.3.1Compare Source
Patch Changes
15fbc41Thanks @matthewp! - Fixes local images returning 404 on non-prerendered pages when using the generic image endpointv6.3.0Compare Source
Minor Changes
#16366
d69f858Thanks @matthewp! - Adds a newexperimental.advancedRoutingoption that lets you take full control of Astro's request handling pipeline by creating asrc/app.tsfile in your project.Today, Astro handles every incoming request through a fixed internal pipeline: trailing slash normalization, redirects, actions, middleware, page rendering, i18n, and so on. That pipeline works great for most sites, but as projects grow you often want to run your own logic between those steps — an auth check before rendering, a rate limiter before actions, custom logging around the whole stack. Advanced routing gives you that control.
When enabled, Astro looks for a
src/app.tsfile in your project. If it finds one, that file becomes the entrypoint for all server-rendered requests. You compose the pipeline yourself using the handlers Astro provides, and you can slot your own logic anywhere in the chain.Enabling advanced routing
Two ways to build your pipeline
Astro ships two entrypoints for advanced routing:
astro/fetchandastro/hono.astro/fetchis a low-level, framework-free API built on the Web Fetch standard. You create aFetchStatefrom the incoming request, then call handler functions in sequence. Each handler takes the state, does its work, and returns aResponse(orundefinedto pass through). This is the core primitive that everything else is built on:astro/honowraps the same handlers as Hono middleware, so you can mix Astro's pipeline with Hono's ecosystem of middleware (logger, CORS, JWT, rate limiting, etc.) using theapp.use()pattern you already know:Both approaches give you the same power — pick whichever fits your project. If you don't need a framework,
astro/fetchkeeps things minimal. If you want a rich middleware ecosystem,astro/honogets you there with one import.For more information on enabling and using this feature in your project, see the experimental advanced routing docs. To give feedback, or to keep up with its development, see the advanced routing RFC for more information and discussion.
#16366
d69f858Thanks @matthewp! - Adds aconsume()instance method toAstroCookies. This method marks the cookies as consumed and returns theSet-Cookieheader values. After consumption, any subsequentset()calls will log a warning, since the headers have already been sent.Previously this was only available as a static method
AstroCookies.consume(cookies). The static method is now deprecated but kept for backward compatibility with existing adapters.#16412
ba2d2e3Thanks @0xbejaxer! - Add retry and error event handling forastro-islandhydration import failures to reduce unrecoverable hydration errors on transient network failures.#16582
885cd31Thanks @Princesseuh! - Adds a newimage.dangerouslyProcessSVGflag to optionally enable processing SVG inputs. For security reasons, Astro will no longer rasterizes SVG image sources by default in its default image service and endpoint.Set
image.dangerouslyProcessSVG: trueto opt back into processing SVG inputs.Note that this is a breaking change for users who were previously relying on Astro's default image service to rasterize SVG inputs, but it is a necessary change to improve security and prevent potential vulnerabilities.
#16519
1b1c218Thanks @louisescher! - Adds support for redirecting URLs in remote image optimization.Previously, when a remote image URL meant to be optimized by Astro led to a redirect, Astro would fail silently and ignore the redirect. Now, Astro tracks up to 10 redirects for these images. If any of the redirects are not covered by a pattern in
image.remotePatternsor a domain inimage.domains, Astro will fail with a helpful error message.In the following example, the first image would be loaded successfully, while the second would lead to Astro throwing an error:
In cases where all redirects to HTTPS hosts should be trusted, the following configuration for
image.remotePatternscan be used:Patch Changes
#16592
9c6efc5Thanks @matthewp! - Escapes interpolated values in the dev server redirect HTML template, consistent with how the 404 template already handles them#16585
78f305eThanks @web-dev0521! - Fixesz.array(z.boolean())in form actions incorrectly coercing the string"false"totrue. Boolean array elements now use the same'true'/'false'string comparison as singlez.boolean()fields, so submitting["false", "true", "false"]correctly parses as[false, true, false].#16567
12a03f2Thanks @matthewp! - Fixes deleted content collection entries persisting ingetCollection()results during dev#16595
ce9b25cThanks @web-dev0521! - FixespushDirectivein the CSP runtime duplicating the new directive once per existing non-matching directive. CallinginsertDirective()(or otherwise pushing a directive whose name is not yet in the list) now appends it exactly once, and a directive that merges with a later existing entry no longer leaves an unmerged copy behind.#16600
94e4b7cThanks @web-dev0521! - FixesAstro.preferredLocalereturning the wrong value wheni18n.localesmixes object-form entries ({ path, codes }) with string entries that normalize to the same locale. The first matching code in the configuredlocalesorder is now selected, matching the documented behavior.#16591
cce20f7Thanks @matthewp! - Uses a consistent generic error message in the image endpoint across all adapters#16629
f54be80Thanks @g-taki! - Fixes a bug where SSR responses inastro devcould crash withTypeError: this.logger.flush is not a function.#16589
3740b24Thanks @ArmandPhilippot! - Fixes an outdated code snippet in the documentation for session storage configuration.Updated dependencies [
354e231]:v6.2.2Compare Source
Patch Changes
#16292
00f48eeThanks @p-linnane! - Fixes head metadata propagation in dev for adapters that load modules in theprerenderVite environment, such as@astrojs/cloudflare. Theastro:head-metadataplugin previously only tracked thessrenvironment, somaybeRenderHead()could fire inside an unrelated component's<template>element, trapping subsequent hoisted<style>blocks.#16451
778865fThanks @maximslo! - Fixes build crash when processing animated AVIF images. Sharp now gracefully passes through unsupported image formats instead of crashing during the build.#16548
7214d3eThanks @senutpal! - Fixes scoped styles applying to the wrong element whenvite.css.transformeris set to'lightningcss'and a selector uses a nested&inside:where(...), such as Tailwind v4'sspace-x-*,space-y-*, anddivide-*utilities.#16566
9ac96b4Thanks @web-dev0521! - Fixesdata-astro-prefetch="tap"not triggering when clicking nested elements (e.g.<span>,<img>,<svg>) inside an anchor tag.#15994
1e70d18Thanks @ossaidqadri! - Fix<style>compilation failure when importing Astro components via tsconfig path aliases#16144
1cd6650Thanks @fkatsuhiro! - Fixed a regression where.htmlwas unexpectedly stripped from dynamic route parameters on non-page routes (.tsendpoints and redirects). This caused endpoints like/some/[...id].tsreturningid: 'file.html'ongetStaticPathsto not serve that file because the generated route (/some/file.html) would get matched asid: filethat is not part of the list returned bygetStaticPaths.#16415
559c0fdThanks @0xbejaxer! - Fix CSS traversal boundaries so pages withexport const partial = truestill contribute styles when imported as components by other pages.#16516
17f1867Thanks @fkatsuhiro! - Fixes an issue where the index route would return a 404 error when using a custombasepath combined withtrailingSlash: 'never'. This ensures that the home page and internal rewrites are correctly matched under these configurations.#16515
280ec88Thanks @jp-knj! - Fixes an issue wherei18n.fallbackpages withfallbackType: 'rewrite'were emitted with empty bodies duringastro build.#16565
7959798Thanks @enjoyandlove! - Fixes session persistence whensession.delete()is the first mutation in a request (no priorget,set,has, orkeys). The session was marked dirty in memory, but persistence skipped the save because#datastayedundefined, so the backing store could still return the deleted key on the next request.#16527
86fd80dThanks @enjoyandlove! - Prevents script deduplication state from being consumed while rendering inert<template>contexts.#16540
e59c637Thanks @ascorbic! - Skips session storage reads when no session cookie is present. Previously, callingsession.get()on a request without a session cookie would initialize the storage driver and make a read that was guaranteed to miss. On network-backed drivers this added latency and resource usage to every anonymous request.#16517
6ab0b3cThanks @adamchal! - Removes inline CSS for prerendered routes from the SSR manifest. The static HTML on disk already inlines those styles, and the SSR worker never renders prerendered routes, so the data was dead weight. Builds with many prerendered routes andbuild.inlineStylesheets: "always"(or"auto"with small stylesheets) will see a smaller SSR entry chunk, which reduces cold-start parse time on platforms like Cloudflare Workers.#16509
d3d3557Thanks @cyphercodes! - Fix conditional named slot callbacks receiving arguments fromAstro.slots.render().#16236
c6b068eThanks @fkatsuhiro! - Fixes thepositionprop on<Image />and<Picture />components to correctly applyobject-positionstyles#16018
d14f47cThanks @felmonon! - FixdefineLiveCollection()soLiveLoaderdata types declared as interfaces are accepted.v6.2.1Compare Source
Patch Changes
#16531
76db01dThanks @rodrigosdev! - Fixes config validation for omittedintegrationsfields with newer Zod versions.#16535
7df0fe4Thanks @rururux! - Fixed an issue where a warning was displayed when theserverproperty was missing during config validation, even though it is not required.#16534
5cf6c51Thanks @matthewp! - Fixes compatibility with Zod 4.4.0 for theserverconfig property and error formattingv6.2.0Compare Source
Minor Changes
#16187
fe58071Thanks @gllmt! - Adds awaitUntiloption to theRenderOptionsso that adapters can forward runtime background-task hooks to Astro.When provided by an adapter, runtime cache providers receive
context.waitUntilinCacheProvider.onRequest(), which allows background cache work such as stale-while-revalidatewithout blocking the response. The Cloudflare adapter now forwards
ExecutionContext.waitUntilto this API.#16290
a49637aThanks @ViVaLaDaniel! - Ensures thatserver.allowedHosts(andvite.preview.allowedHosts) configuration is respected when usingastro previewwith the@astrojs/cloudflareadapter. This improves security by preventing DNS rebinding attacks when previewing Cloudflare builds locally.#15725
4108ec1Thanks @meyer! - Adds support for a new'jsx'value for thecompressHTMLoption. When set, whitespace is stripped using JSX whitespace rules instead of the default HTML compression strategy.In JSX, whitespaces never matter, as such, no amount of indentation, or newlines will not affect the rendered output. For instance, the following code:
will be rendered as
foobar, whereas with HTML whitespace rules, a space would be present between the words due to the newline and indentation between the tags.#16477
28fb3e1Thanks @ematipico! - Adds experimental support for configurable log handlers.This experimental feature provides better control over Astro's logging infrastructure by allowing users to replace the default console output with custom logging implementations (e.g., structured JSON). This is particularly useful for users using on-demand rendering and wishing to connect their log aggregation services, such as Kibana, Logstash, CloudWatch, Grafana, or Loki.
By default, Astro provides three built-in log handlers (
json,node, andconsole), but you can also create your own.JSON logging
JSON logging can be enabled via the CLI for the
build,dev, andsynccommands using theexperimentalJsonflag:Custom logger
You can also create your own custom logger by implementing the correct interface:
For more information on enabling and using this feature in your project, see the Experimental Logger docs.
For a complete overview and to give feedback on this experimental API, see the Custom logger RFC.
#16333
0f7c3c8Thanks @florian-lefebvre! - Adds an experimental flagsvgOptimizerthat enables automatic optimization of your SVG components using the provided optimizer. This supersedes thesvgoexperimental flag, which is now removed.When enabled, your imported SVG files used as components will be optimized for smaller file sizes and better performance while maintaining visual quality. This can significantly reduce the size of your SVG assets by removing unnecessary metadata, comments, and redundant code.
Astro ships with a SVGO based optimizer, but any can be used.
To enable this feature, add the experimental flag in your Astro config and remove
svgoif it was enabled:For more information on enabling and using this feature in your project, see the experimental SVG optimization docs.
#16302
f6f8e80Thanks @florian-lefebvre! - Adds a newexperimental_getFontFileURL()method to resolve font file URLs when using the Fonts APIThe
fontDataobject exported fromastro:assetswas introduced to provide low-level access to font family data for advanced usage. One of the goals of this API was to be able to resolve buffers using URLs. However, it turned out to be impractical, especially during prerendering.Astro now exports a new
experimental_getFontFileURL()helper function fromastro:assetsto resolve font file URLs fromfontData. For example, when using satori to generate Open Graph images:See the Fonts API documentation for more information.
Patch Changes
8812382Thanks @seroperson! - Prevents script deduplication inside<template>elementsv6.1.10Compare Source
Patch Changes
#16479
1058428Thanks @matthewp! - Fixes a spurious[WARN] [content] Content config not loadedwarning duringastro devfor projects that don't use content collections#16457
3d82220Thanks @matthewp! - Hardens server island encryption to prevent encrypted data from one island component being replayed against a different one#16481
152700eThanks @matthewp! - Fixes a spurious 404 request for a dev toolbar sourcemap duringastro devcaused by the browser mis-resolving a relativesourceMappingURLfrom the/@​id/URL prefix#16480
1bcb43bThanks @matthewp! - Fixes an unnecessary full page reload on first navigation during devv6.1.9Compare Source
Patch Changes
#16448
99464edThanks @matthewp! - Updates vite, picomatch, and unstorage to latest patch versions#16422
a3951d7Thanks @matthewp! - Hardensastro-islandexport resolution and hydration error handling for malformed component metadata#16420
e21de1dThanks @matthewp! - Hardens Astro's error overlay and server logging paths to avoid unsafe HTML insertion and format-string interpolation#16419
f3485c3Thanks @matthewp! - Hardens nested object and package metadata lookups to ignore prototype keys in content handling and project scaffolding#16022
a002540Thanks @mathieumaf! - Fixes an issue where i18n domains would return 404 whentrailingSlashis set tonever.Updated dependencies [
99464ed,f3485c3]:v6.1.8Compare Source
Patch Changes
#16367
a6866a7Thanks @ematipico! - Fixes an issue where build output files could contain special characters (!,~,{,}) in their names, causing deploy failures on platforms like Netlify.#16381
217c5b3Thanks @ematipico! - Slightly improved the performance of the dev server by caching the internal crawling of the dependencies of a project.#16348
7d26cd7Thanks @ocavue! - Fixes a bug where emitted assets during a client build would contain always fresh, new hashes in their name. Now the build should be more stable.#16317
d012bfeThanks @das-peter! - Fixes a bug whereallowedDomainsweren't correctly propagated when using the development server.#16379
5a84551Thanks @martrapp! - Improves Vue scoped style handling in DEV mode during client router navigation.#16317
d012bfeThanks @das-peter! - Adds tests to verify settings are properly propagated when using the development server.#16282
5b0fdaaThanks @jmurty! - Fixes build errors on platforms with skew protection enabled (e.g. Vercel, Netlify) for inter-chunk Javascript using dynamic importsUpdated dependencies [
e0b240e]:v6.1.7Compare Source
Patch Changes
#16027
c62516bThanks @fkatsuhiro! - Fixes a bug where remote image dimensions were not validated during static builds on Netlify.#16311
94048f2Thanks @Arecsu! - Fixes--portflag being ignored after a Vite-triggered server restart (e.g. when a.envfile changes)#16316
0fcd04cThanks @ematipico! - Fixes the/_imageendpoint accepting an arbitraryf=svgquery parameter and serving non-SVG content asimage/svg+xml. The endpoint now validates that the source is actually SVG before honoringf=svg, matching the same guard already enforced on the<Image>component path.v6.1.6Compare Source
Patch Changes
#16202
b5c2fbaThanks @matthewp! - Fixes Actions failing withActionsWithoutServerOutputErrorwhen usingoutput: 'static'with an adapter#16303
b06eabfThanks @matthewp! - Improves handling of special characters in inline<script>content#14924
bb4586aThanks @aralroca! - Fixes SCSS and CSS module file changes triggering a full page reload instead of hot-updating styles in place during developmentv6.1.5Compare Source
Patch Changes
#16171
5bcd03cThanks @Desel72! - Fixes a build error that occurred when a pre-rendered page used the<Picture>component and another page calledrender()on content collection entries.#16239
7c65c04Thanks @dataCenter430! - Fixes sync content inside<Fragment>not streaming to the browser until all async sibling expressions have resolved.#16242
686c312Thanks @martrapp! - Revives UnoCSS in dev mode when used with the client router.This change partly reverts #16089, which in hindsight turned out to be too general. Instead of automatically persisting all style sheets, we now do this only for styles from Vue components.
#16192
79d86b8Thanks @alexanderniebuhr! - Uses today’s date for Cloudflarecompatibility_dateinastro add cloudflareWhen creating new projects,
astro add cloudflarenow setscompatibility_dateto the current date. Previously, this date was resolved from locally installed packages, which could be unreliable in some package manager environments. Using today’s date is simpler and more reliable across environments, and is supported byworkerd.#16259
34df955Thanks @gameroman! - Removeddlvdependencyv6.1.4Compare Source
Patch Changes
#16197
21f9fe2Thanks @SchahinRohani! - Remove unused re-exports from assets/utils barrel file to fix Vite build warning#16059
6d5469eThanks @matthewp! - FixesExpected 'miniflare' to be definederrors and 404 responses in dev mode when using the Cloudflare adapter and the config file changes. Instead of creating a brand new Vite server on config changes, Astro now performs a Vite in-place restart, allowing the Cloudflare adapter to reuse its existing miniflare instance across restarts.#16154
7610ba4Thanks @Desel72! - Fixes pages with dots in their filenames (e.g.hello.world.astro) returning 404 when accessed with a trailing slash in the dev server. ThetrailingSlashForPathfunction now only forcestrailingSlash: 'never'for endpoints with file extensions, allowing pages to correctly respect the user'strailingSlashconfig.#16193
23425e2Thanks @matthewp! - FixestrailingSlash: "always"producing redirect HTML instead of the actual response for extensionless endpoints during static buildsv6.1.3Compare Source
Patch Changes
#16161
b51f297Thanks @matthewp! - Fixes a dev rendering issue with the Cloudflare adapter where head metadata could be missing and dev CSS/scripts could be injected in the wrong place#16110
de669f0Thanks @tmimmanuel! - Fixes skew protection query parameters not being appended to inter-chunk JavaScript imports in client bundles, which could cause version mismatches during rolling deployments on Vercel#16162
a0a49e9Thanks @rururux! - Fixes an issue where HMR would not trigger when modifying files while using @astrojs/cloudflare with prerenderEnvironment: 'node' enabled.#16142
7454854Thanks @rururux! - Fixes HTML content being incorrectly escaped as plain text when rendering a MDX component using theAstroContainerAPIs.#16116
12602a9Thanks @riderx! - Fixes a bug where page-level CSS could leak between unrelated pages when traversing style parents across top-level route boundaries#16178
a7e7567Thanks @matthewp! - Fixes SSR builds failing with "No matching renderer found" when a project only has injected routes and nosrc/pages/directoryv6.1.2Compare Source
Patch Changes
#16104
47a394dThanks @matthewp! - Fixesastro previewignoringvite.preview.allowedHostsset inastro.config.mjs#16047
711f837Thanks @matthewp! - Fixes catch-all routes incorrectly intercepting requests for static assets when using the@astrojs/nodeadapter in middleware mode.#15981
a60cbb6Thanks @moktamd! - Fix Zod v4 validation error formatting to show human-readable messages instead of raw JSONv6.1.1Compare Source
Patch Changes
#16479
1058428Thanks @matthewp! - Fixes a spurious[WARN] [content] Content config not loadedwarning duringastro devfor projects that don't use content collections#16457
3d82220Thanks @matthewp! - Hardens server island encryption to prevent encrypted data from one island component being replayed against a different one#16481
152700eThanks @matthewp! - Fixes a spurious 404 request for a dev toolbar sourcemap duringastro devcaused by the browser mis-resolving a relativesourceMappingURLfrom the/@​id/URL prefix#16480
1bcb43bThanks @matthewp! - Fixes an unnecessary full page reload on first navigation during devv6.1.0Compare Source
Minor Changes
#15804
a5e7232Thanks @merlinnot! - Allows setting codec-specific defaults for Astro's built-in Sharp image service viaimage.service.config.You can now configure encoder-level options such as
jpeg.mozjpeg,webp.effort,webp.alphaQuality,avif.effort,avif.chromaSubsampling, andpng.compressionLevelwhen usingastro/assets/services/sharpfor compile-time image generation.These settings apply as defaults for the built-in Sharp pipeline, while per-image
qualitystill takes precedence when set on<Image />,<Picture />, orgetImage().#15455
babf57fThanks @AhmadYasser1! - AddsfallbackRoutesto theIntegrationResolvedRoutetype, exposing i18n fallback routes to integrations via theastro:routes:resolvedhook for projects usingfallbackType: 'rewrite'.This allows integrations such as the sitemap integration to properly include generated fallback routes in their output.
#15340
10a1a5aThanks @trueberryless! - Adds support for advanced configuration of SmartyPants in Markdown.You can now pass an options object to
markdown.smartypantsin your Astro configuration to fine-tune how punctuation, dashes, and quotes are transformed.This is helpful for projects that require specific typographic standards, such as "oldschool" dash handling or localized quotation marks.
See the
retext-smartypantsoptions for more information.Patch Changes
#16025
a09f319Thanks @koji-1009! - Instructs the client router to skip view transition animations when the browser is already providing its own visual transition, such as a swipe gesture.#16055
ccecb8fThanks @Gautam-Bharadwaj! - Fixes an issue whereclient:onlycomponents could have duplicateclient:component-pathattributes added in MDX in rare cases#16081
44fc340Thanks @crazylogic03! - Fixes theemitFile() is not supported in serve modewarning that appears duringastro devwhen using integrations that inject before-hydration scripts (e.g.@astrojs/react)#16068
31d733bThanks @Karthikeya1500! - Fixes the dev toolbar a11y audit incorrectly classifyingmenuitemradioas a non-interactive ARIA role.#16080
e80ac73Thanks @ematipico! - Fixesexperimental.queuedRenderingincorrectly escaping the HTML output of.htmlpage files, causing the page content to render as plain text instead of HTML in the browser.#16048
13b9d56Thanks @matthewp! - Fixes a dev server crash (serverIslandNameMap.get is not a function) that occurred when navigating to a page withserver:deferafter first visiting a page without one, when using@astrojs/cloudflare#16093
336e086Thanks @Snugug! - Fixes Zod meta not correctly being rendered on top-level schema when converted into JSON Schema#16043
d402485Thanks @ematipico! - FixescheckOriginCSRF protection inastro devbehind a TLS-terminating reverse proxy. The dev server now readsX-Forwarded-Proto(gated onsecurity.allowedDomains, matching production behaviour) so the constructed request origin matches thehttps://origin the browser sends. Also ensuressecurity.allowedDomainsandsecurity.checkOriginare respected in dev.#16064
ba58e0dThanks @ematipico! - Updates the dependencysvgoto the latest, to fix a security issue.#16007
2dcd8d5Thanks @florian-lefebvre! - Fixes a case where fonts files would unecessarily be copied several times during the build#16017
b089b90Thanks @felmonon! - Fix theastro syncerror message whengetImage()is called while loading content collections.#16014
fa73fbbThanks @matthewp! - Fixes a build error where usingastro:config/clientinside a<script>tag would cause Rollup to fail with "failed to resolve importvirtual:astro:routesfromvirtual:astro:manifest"#16054
f74465aThanks @seroperson! - Fixes an issue with the development server, where changes to the middleware weren't picked, and it required a full restart of the server.#16033
198d31bThanks @adampage! - Fixes a bug where the the roleimagewas incorrectly reported by audit tool bar.#15935
278828cThanks @oliverlynch! - Fixes cached assets failing to revalidate due to redirect check mishandling Not Modified responses.#16075
2c1ae85Thanks @florian-lefebvre! - Fixes a case where invalid URLs would be generated in development when using font families with an obliquestyleand angles#16062
87fd6a4Thanks @matthewp! - Warns on dev server startup when Vite 8 is detected at the top level of the user's project, and automatically adds a"overrides": { "vite": "^7" }entry topackage.jsonwhen runningastro add cloudflare. This prevents arequire_dist is not a functioncrash caused by a Vite version split between Astro (requires Vite 7) and packages like@tailwindcss/vitethat hoist Vite 8.Updated dependencies [
10a1a5a]:v6.0.8Compare Source
Patch Changes
#15978
6d182feThanks @seroperson! - Fixes a bug where Astro Actions didn't properly support nested object properties, causing problems when users used zod functions such assuperRefineordiscriminatedUnion.#16011
e752170Thanks @matthewp! - Fixes a dev server hang on the first request when using the Cloudflare adapter#15997
1fddff7Thanks @ematipico! - FixesAstro.rewrite()failing when the target path contains duplicate slashes (e.g.//about). The duplicate slashes are now collapsed before URL parsing, preventing them from being interpreted as a protocol-relative URL.v6.0.7Compare Source
Patch Changes
#15950
acce5e8Thanks @matthewp! - Fixes a build regression in projects with multiple frontend integrations whereserver:deferserver islands could fail at runtime when all pages are prerendered.#15988
c93b4a0Thanks @ossaidqadri! - Fix styles from dynamically imported components not being injected on first dev server load.#15968
3e7a9d5Thanks @chasemccoy! - FixesrenderMarkdownin custom content loaders not resolving images in markdown content. Images referenced in markdown processed byrenderMarkdownare now correctly optimized, matching the behavior of the built-inglob()loader.#15990
1e6017fThanks @ematipico! - Fixes an issue whereAstro.currentLocalewould always be the default locale instead of the actual one when using a dynamic route like[locale].astroor[locale]/index.astro. It now resolves to the correct locale from the URL.#15990
1e6017fThanks @ematipico! - Fixes an issue where visiting an invalid locale URL (e.g./asdf/) would show the content of a dynamic[locale]page with a 404 status code, instead of showing your custom 404 page. Now, the correct 404 page is rendered when the locale in the URL doesn't match any configured locale.#15960
1d84020Thanks @matthewp! - Fixes Cloudflare dev server islands withprerenderEnvironment: 'node'by sharing the serialized manifest encryption key across dev environments and routing server island requests through the SSR runtime.#15735
9685e2dThanks @fa-sharp! - Fixes an EventEmitter memory leak when serving static pages from Node.js middleware.When using the middleware handler, requests that were being passed on to Express / Fastify (e.g. static files / pre-rendered pages / etc.) weren't cleaning up socket listeners before calling
next(), causing a memory leak warning. This fix makes sure to run the cleanup before callingnext().v6.0.6Compare Source
Patch Changes
#15965
2dca307Thanks @matthewp! - Fixes client hydration for components imported through Node.js subpath imports (package.json#imports, e.g.#components/*), for example when using the Cloudflare adapter in development.#15770
6102ca2Thanks @jpc-ae! - Updates thecreate astrowelcome message to highlight the graceful dev/preview server quit command rather than the kill process shortcut#15953
7eddf22Thanks @Desel72! - fix(hmr): eagerly recompile on style-only change to prevent stale slots render#15916
5201ed4Thanks @trueberryless! - FixesInferLoaderSchematype inference for content collections defined with a loader that includes aschema#15864
d3c7de9Thanks @florian-lefebvre! - Removes temporary support for Node >=20.19.1 because Stackblitz now uses Node 22 by default#15944
a5e1acdThanks @fkatsuhiro! - Fixes SSR dynamic routes with.htmlextension (e.g.[slug].html.astro) not working#15937
d236245Thanks @ematipico! - Fixes an issue where HMR didn't correctly work on Windows when adding/changing/deleting routes inpages/.#15931
98dfb61Thanks @Strernd! - Fix skew protection query params not being applied to island hydrationcomponent-urlandrenderer-url, and ensure query params are appended safely for asset URLs with existing search/hash parts.Updated dependencies []:
v6.0.5Compare Source
Patch Changes
#15891
b889231Thanks @matthewp! - Fix dev routing forserver:deferislands when adapters opt into handling prerendered routes in Astro core. Server island requests are now treated as prerender-handler eligible so prerendered pages usingprerenderEnvironment: 'node'can load island content without400errors.#15890
765a887Thanks @matthewp! - Fixesastro:actionsvalidation to check resolved routes, so projects using default static output with at least oneprerender = falsepage or endpoint no longer fail during startup.#15884
dcd2c8eThanks @matthewp! - Avoid aMaxListenersExceededWarningduringastro devstartup by increasing the shared Vite watcher listener limit when attaching content server listeners.#15904
23d5244Thanks @jlukic! - Emit thebefore-hydrationscript chunk for theclientVite environment. The chunk was only emitted forprerenderandssrenvironments, causing a 404 when browsers tried to load it. This broke hydration for any integration usinginjectScript('before-hydration', ...), including Lit SSR.#15933
325901eThanks @ematipico! - Fixes an issue where<style>tags inside SVG components weren't correctly tracked when enabling CSP.#15875
c43ef8aThanks @matthewp! - Ensure custom prerenderers are always torn down during build, even whengetStaticPaths()throws.#15887
1861fedThanks @ematipico! - Fixes an issue where the build incorrectly leaked server entrypoint into the client environment, causing adapters to emit warnings during the build.#15888
925252eThanks @matthewp! - Fix a bug whereserver:defercould fail at runtime in prerendered pages for some adapters (including Cloudflare), causing errors likeserverIslandMap?.get is not a function.#15901
07c1002Thanks @delucis! - Fixes JSON schema generation for content collection schemas that have differences between their input and output shapes.#15882
759f946Thanks @matthewp! - FixAstro.url.pathnamefor the root page when usingbuild.format: "file"so it resolves to/index.htmlinstead of/.htmlduring builds.v6.0.4Compare Source
Patch Changes
#15870
920f10bThanks @matthewp! - Prebundleastro/toolbarin dev when custom dev toolbar apps are registered, preventing re-optimization reloads that can hide or break the toolbar.#15876
f47ac53Thanks @ematipico! - FixesredirectToDefaultLocaleproducing a protocol-relative URL (//locale) instead of an absolute path (/locale) whenbaseis'/'.#15767
e0042f7Thanks @matthewp! - Fixes server islands (server:defer) not working when only used in prerendered pages withoutput: 'server'.#15873
35841edThanks @matthewp! - Fix a dev server bug where newly created pages could miss layout-imported CSS until restart.#15874
ce0669dThanks @ematipico! - Fixes a warning when usingprefetchAll#15754
58f1d63Thanks @rururux! - Fixes a bug where a directory at the project root sharing the same name as a page route would cause the dev server to return a 404 instead of serving the page.#15869
76b3a5eThanks @matthewp! - Update the unknown file extension error hint to recommendvite.resolve.noExternal, which is the correct Vite 7 config key.v6.0.3Compare Source
Patch Changes
#15711
b2bd27bThanks @OliverSpeir! - Improves Astro core's dev environment handling for prerendered routes by ensuring route/CSS updates and prerender middleware behavior work correctly across both SSR and prerender environments.This enables integrations that use Astro's prerender dev environment (such as Cloudflare with
prerenderEnvironment: 'node') to get consistent route matching and HMR behavior during development.#15852
1cdaf9fThanks @ematipico! - Fixes a regression where the the routes emitted by theastro:build:donehook didn't have thedistURLarray correctly populated.#15765
ca76ff1Thanks @matthewp! - Hardens server island POST endpoint validation to use own-property checks for improved consistencyv6.0.2Compare Source
Patch Changes
95e12a2Thanks @Princesseuh! - Fixesreturn;syntax not working in the frontmatter correctly in certain contextsv6.0.1Compare Source
Patch Changes
a4c0d0bThanks @matthewp! - Fixesastro addso the tsconfig preview shows the actual pending changes before confirmationv6.0.0Compare Source
Major Changes
#14446
ece667aThanks @florian-lefebvre! - RemovesentryPointsonastro:build:ssrhook (Integration API) - (v6 upgrade guidance)#15535
dfe2e22Thanks @florian-lefebvre! - DeprecatesloadManifest()andloadApp()fromastro/app/node(Adapter API) - (v6 upgrade guidance)#15006
f361730Thanks @florian-lefebvre! - Removes sessiontestdriver - (v6 upgrade guidance)#15461
9f21b24Thanks @florian-lefebvre! - BREAKING CHANGE to the v6 beta Adapter API only: renamesentryTypetoentrypointResolutionand updates possible valuesAstro 6 introduced a way to let adapters have more control over the entrypoint by passing
entryType: 'self'tosetAdapter(). However during beta development, the name was unclear and confusing.entryTypeis now renamed toentrypointResolutionand its possible values are updated:legacy-dynamicbecomesexplicit.selfbecomesauto.If you are building an adapter with v6 beta and specifying
entryType, update it:#14426
861b9ccThanks @florian-lefebvre! - Removes the deprecatedemitESMImage()function - (v6 upgrade guidance)#15006
f361730Thanks @florian-lefebvre! - Deprecates session driver string signature - (v6 upgrade guidance)#15180
8780ff2Thanks @Princesseuh! - Adds support for converting SVGs to raster images (PNGs, WebP, etc) to the default Sharp image service - (v6 upgrade guidance)#14446
ece667aThanks @florian-lefebvre! - Removesroutesonastro:build:donehook (Integration API) - (v6 upgrade guidance)#15424
33d6146Thanks @Princesseuh! - Throws an error whengetImage()fromastro:assetsis called on the client - (v6 upgrade guidance)#14462
9fdfd4cThanks @florian-lefebvre! - Removes the oldapp.render()signature (Adapter API) - (v6 upgrade guidance)#14956
0ff51dfThanks @matthewp! - Astro v6.0 upgrades to Zod v4 for schema validation - (v6 upgrade guidance)#14759
d7889f7Thanks @florian-lefebvre! - Updates how schema types are inferred for content loaders with schemas (Loader API) - (v6 upgrade guidance)#15192
ada2808Thanks @gameroman! - Removes support for CommonJS config files - (v6 upgrade guidance)#14462
9fdfd4cThanks @florian-lefebvre! - Removesprefetch()withoption - (v6 upgrade guidance)#14306
141c4a2Thanks @ematipico! - Removes support for routes with percent-encoded percent signs (e.g.%25) - (v6 upgrade guidance)#14432
b1d87ecThanks @florian-lefebvre! - DeprecatesAstroingetStaticPaths()- (v6 upgrade guidance)#14759
d7889f7Thanks @florian-lefebvre! - Removes the option to define dynamic schemas in content loaders as functions and adds a new equivalentcreateSchema()property (Loader API) - (v6 upgrade guidance)#14457
049da87Thanks @florian-lefebvre! - Updates trailing slash behavior of endpoint URLs - (v6 upgrade guidance)#14494
727b0a2Thanks @florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance)#14461
55a1a91Thanks @florian-lefebvre! - Deprecatesimport.meta.env.ASSETS_PREFIX- (v6 upgrade guidance)#14586
669ca5bThanks @ocavue! - Changes the values allowed inparamsreturned bygetStaticPaths()- (v6 upgrade guidance)#15668
1118ac4Thanks @florian-lefebvre! - Changes TypeScript configuration - (v6 upgrade guidance)#14421
df6d2d7Thanks @florian-lefebvre! - Removes the previously deprecatedAstro.glob()- (v6 upgrade guidance)#15049
beddfebThanks @Ntale3! - Removes the ability to render Astro components in Vitest client environments - (v6 upgrade guidance)#15461
9f21b24Thanks @florian-lefebvre! - DeprecatescreateExports()andstart()(Adapter API) - (v6 upgrade guidance)#15535
dfe2e22Thanks @florian-lefebvre! - DeprecatesNodeAppfromastro/app/node(Adapter API) - (v6 upgrade guidance)#14462
9fdfd4cThanks @florian-lefebvre! - Removes thehandleFormsprop for the<ClientRouter />component - (v6 upgrade guidance)#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)#15332
7c55f80Thanks @matthewp! - Adds frontmatter parsing support torenderMarkdownin content loaders. When markdown content includes frontmatter, it is now extracted and available inmetadata.frontmatter, and excluded from the HTML output. This makesrenderMarkdownbehave consistently with theglobloader.#14400
c69c7deThanks @ellielok! - Removes the deprecated<ViewTransitions />component - (v6 upgrade guidance)#14306
141c4a2Thanks @ematipico! - RemovesRouteData.generatefrom the Integration API - (v6 upgrade guidance)#14406
4f11510Thanks @florian-lefebvre! - Changes the default routing configuration value ofi18n.routing.redirectToDefaultLocalefromtruetofalse- (v6 upgrade guidance)#14989
73e8232Thanks @florian-lefebvre! - Deprecates exposedastro:transitionsinternals - (v6 upgrade guidance)#15726
6f19eccThanks @ocavue! - Updates dependencyshikito v4Check Shiki's upgrade guide.
#14758
010f773Thanks @florian-lefebvre! - Removes thesetManifestDatamethod fromAppandNodeApp(Adapter API) - (v6 upgrade guidance)#14477
25fe093Thanks @florian-lefebvre! - Removesrewrite()from Actions context - (v6 upgrade guidance)#14826
170f64eThanks @florian-lefebvre! - Removes theexperimental.failOnPrerenderConflictflag and replaces it with a new configuration optionprerenderConflictBehavior- (v6 upgrade guidance)#14923
95a1969Thanks @florian-lefebvre! - Deprecatesastro:schemaandzfromastro:contentin favor ofastro/zod- (v6 upgrade guidance)#14844
8d43b1dThanks @trueberryless! - Removes exposedastro:actionsinternals - (v6 upgrade guidance)#14306
141c4a2Thanks @ematipico! - Changes the shape ofSSRManifestproperties and adds several new required properties in the Adapter API - (v6 upgrade guidance)#15266
f7c9365Thanks @florian-lefebvre! - AllowsAstro.cspandcontext.cspto be undefined instead of throwing errors whencsp: trueis not configuredWhen using the experimental Content Security Policy feature in Astro 5.x,
context.cspwas always defined but would throw ifexperimental.cspwas not enabled in the Astro config.For the stable version of this API in Astro 6,
context.cspcan now be undefined if CSP is not enabled and its methods will never throw.What should I do?
If you were using experimental CSP runtime utilities, you must now access methods conditionally:
#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)#15407
aedbbd8Thanks @ematipico! - Changes how styles of responsive images are emitted - (v6 upgrade guidance)#14306
141c4a2Thanks @ematipico! - Changes integration hooks and HMR access patterns in the Integration API - (v6 upgrade guidance)#14306
141c4a2Thanks @ematipico! - Removes the unusedastro:ssr-manifestvirtual module - (v6 upgrade guidance)#14485
6f67c6eThanks @florian-lefebvre! - Updatesimport.meta.envvalues to always be inlined - (v6 upgrade guidance)#14480
36a461bThanks @florian-lefebvre! - Updates<script>and<style>tags to render in the order they are defined - (v6 upgrade guidance)#14407
3bda3ceThanks @ascorbic! - Removes legacy content collection support - (v6 upgrade guidance)Minor Changes
#14306
141c4a2Thanks @ematipico! - Adds new optional properties tosetAdapter()for adapter entrypoint handling in the Adapter APIChanges:
entryType?: 'self' | 'legacy-dynamic'- determines if the adapter provides its own entrypoint ('self') or if Astro constructs one ('legacy-dynamic', default)Migration: Adapter authors can optionally add these properties to support custom dev entrypoints. If not specified, adapters will use the legacy behavior.
#15700
4e7f3e8Thanks @ocavue! - Updates the internal logic during SSR by providing additional metadata for UI framework integrations.#15231
3928b87Thanks @rururux! - Adds a new optionalgetRemoteSize()method to the Image Service API.Previously,
inferRemoteSize()had a fixed implementation that fetched the entire image to determine its dimensions.With this new helper function that extends
inferRemoteSize(), you can now override or extend how remote image metadata is retrieved.This enables use cases such as:
For example, you can add a simple cache layer to your existing image service:
See the Image Services API reference documentation for more information.
#15077
a164c77Thanks @matthewp! - Updates the Integration API to addsetPrerenderer()to theastro:build:starthook, allowing adapters to provide custom prerendering logic.The new API accepts either an
AstroPrerendererobject directly, or a factory function that receives the default prerenderer:Also adds the
astro:static-pathsvirtual module, which exports aStaticPathsclass for adapters to collect all prerenderable paths from within their target runtime. This is useful when implementing a custom prerenderer that runs in a non-Node environment:See the adapter reference for more details on implementing a custom prerenderer.
#15345
840fbf9Thanks @matthewp! - Adds a newemitClientAssetfunction toastro/assets/utilsfor integration authors. This function allows emitting assets that will be moved to the client directory during SSR builds, useful for assets referenced in server-rendered content that need to be available on the client.#15460
ee7e53fThanks @florian-lefebvre! - Updates the Adapter API to allow providing aserverEntrypointwhen usingentryType: 'self'Astro 6 introduced a new powerful yet simple Adapter API for defining custom server entrypoints. You can now call
setAdapter()with theentryType: 'self'option and specify your customserverEntrypoint:If you need further customization at the Vite level, you can omit
serverEntrypointand instead specify your custom server entrypoint withvite.build.rollupOptions.input.#15781
2de969dThanks @ematipico! - Adds a newclientAddressoption to thecreateContext()functionProviding this value gives adapter and middleware authors explicit control over the client IP address. When not provided, accessing
clientAddressthrows an error consistent with other contexts where it is not set by the adapter.Additionally, both of the official Netlify and Vercel adapters have been updated to provide this information in their edge middleware.
#15258
d339a18Thanks @ematipico! - Stabilizes the adapter featureexperimentalStatiHeaders. If you were using this feature in any of the supported adapters, you'll need to change the name of the flag:#15535
dfe2e22Thanks @florian-lefebvre! - Exports newcreateRequest()andwriteResponse()utilities fromastro/app/nodeTo replace the deprecated
NodeApp.createRequest()andNodeApp.writeResponse()methods, theastro/app/nodemodule now exposes newcreateRequest()andwriteResponse()utilities. These can be used to convert a NodeJSIncomingMessageinto a web-standardRequestand stream a web-standardResponseinto a NodeJSServerResponse:#15755
f9ee868Thanks @matthewp! - Adds a newsecurity.serverIslandBodySizeLimitconfiguration optionServer island POST endpoints now enforce a body size limit, similar to the existing
security.actionBodySizeLimitfor Actions. The new option defaults to1048576(1 MB) and can be configured independently.Requests exceeding the limit are rejected with a 413 response. You can customize the limit in your Astro config:
#15529
a509941Thanks @florian-lefebvre! - Adds a new build-in font providernpmto access fonts installed as NPM packagesYou can now add web fonts specified in your
package.jsonthrough Astro's type-safe Fonts API. Thenpmfont provider allows you to add fonts either from locally installed packages innode_modulesor from a CDN.Set
fontProviders.npm()as your fonts provider along with the requirednameandcssVariablevalues, and addoptionsas needed:See the NPM font provider reference documentation for more details.
#15471
32b4302Thanks @ematipico! - Adds a new experimental flagqueuedRenderingto enable a queue-based rendering engineThe new engine is based on a two-pass process, where the first pass
traverses the tree of components, emits an ordered queue, and then the queue is rendered.
The new engine does not use recursion, and comes with two customizable options.
Early benchmarks showed significant speed improvements and memory efficiency in big projects.
Queue-rendered based
The new engine can be enabled in your Astro config with
experimental.queuedRendering.enabledset totrue, and can be further customized with additional sub-features.Pooling
With the new engine enabled, you now have the option to have a pool of nodes that can be saved and reused across page rendering. Node pooling has no effect when rendering pages on demand (SSR) because these rendering requests don't share memory. However, it can be very useful for performance when building static pages.
Content caching
The new engine additionally unlocks a new
contentCacheoption. This allows you to cache values of nodes during the rendering phase. This is currently a boolean feature with no further customization (e.g. size of cache) that uses sensible defaults for most large content collections:When disabled, the pool engine won't cache strings, but only types.
For more information on enabling and using this feature in your project, see the experimental queued rendering docs for more details.
#14888
4cd3fe4Thanks @OliverSpeir! - Updatesastro add cloudflareto better setup types, by adding./worker-configuration.d.tsto tsconfig includes and agenerate-typesscript to package.json#15646
0dd9d00Thanks @delucis! - Removes redundantfetchpriorityattributes from the output of Astro’s<Image>componentPreviously, Astro would always include
fetchpriority="auto"on images not using thepriorityattribute.However, this is the default value, so specifying it is redundant. This change omits the attribute by default.
#15291
89b6cddThanks @florian-lefebvre! - Removes theexperimental.fontsflag and replaces it with a new configuration optionfonts- (v6 upgrade guidance)#15495
5b99e90Thanks @leekeh! - Adds a newmiddlewareModeadapter feature to replace the previousedgeMiddlewareoption.This feature only impacts adapter authors. If your adapter supports
edgeMiddleware, you should upgrade to the newmiddlewareModeoption to specify the middleware mode for your adapter as soon as possible. TheedgeMiddlewarefeature is deprecated and will be removed in a future major release.#15694
66449c9Thanks @matthewp! - AddspreserveBuildClientDiroption to adapter featuresAdapters can now opt in to preserving the client/server directory structure for static builds by setting
preserveBuildClientDir: truein their adapter features. When enabled, static builds will output files tobuild.clientinstead of directly tooutDir.This is useful for adapters that require a consistent directory structure regardless of the build output type, such as deploying to platforms with specific file organization requirements.
#15332
7c55f80Thanks @matthewp! - Adds afileURLoption torenderMarkdownin content loaders, enabling resolution of relative image paths. When provided, relative image paths in markdown will be resolved relative to the specified file URL and included inmetadata.localImagePaths.#15407
aedbbd8Thanks @ematipico! - Adds support for responsive images whensecurity.cspis enabled, out of the box.Astro's implementation of responsive image styles has been updated to be compatible with a configured Content Security Policy.
Instead of, injecting style elements at runtime, Astro will now generate your styles at build time using a combination of
class=""anddata-*attributes. This means that your processed styles are loaded and hashed out of the box by Astro.If you were previously choosing between Astro's CSP feature and including responsive images on your site, you may now use them together.
#15543
d43841dThanks @Princesseuh! - Adds a newexperimental.rustCompilerflag to opt into the experimental Rust-based Astro compilerThis experimental compiler is faster, provides better error messages, and generally has better support for modern JavaScript, TypeScript, and CSS features.
After enabling in your Astro config, the
@astrojs/compiler-rspackage must also be installed into your project separately:This new compiler is still in early development and may exhibit some differences compared to the existing Go-based compiler. Notably, this compiler is generally more strict in regard to invalid HTML syntax and may throw errors in cases where the Go-based compiler would have been more lenient. For example, unclosed tags (e.g.
<p>My paragraph) will now result in errors.For more information about using this experimental feature in your project, especially regarding expected differences and limitations, please see the experimental Rust compiler reference docs. To give feedback on the compiler, or to keep up with its development, see the RFC for a new compiler for Astro for more information and discussion.
#15349
a257c4cThanks @ascorbic! - Passes collection name to live content loadersLive content collection loaders now receive the collection name as part of their parameters. This is helpful for loaders that manage multiple collections or need to differentiate behavior based on the collection being accessed.
#15006
f361730Thanks @florian-lefebvre! - Adds new session driver object shapeFor greater flexibility and improved consistency with other Astro code, session drivers are now specified as an object:
Specifying the session driver as a string has been deprecated, but will continue to work until this feature is removed completely in a future major version. The object shape is the current recommended and documented way to configure a session driver.
#15291
89b6cddThanks @florian-lefebvre! - Adds a new Fonts API to provide first-party support for adding custom fonts in Astro.This feature allows you to use fonts from both your file system and several built-in supported providers (e.g. Google, Fontsource, Bunny) through a unified API. Keep your site performant thanks to sensible defaults and automatic optimizations including preloading and fallback font generation.
To enable this feature, configure
fontswith one or more fonts:Import and include the
<Font />component with the requiredcssVariableproperty in the head of your page, usually in a dedicatedHead.astrocomponent or in a layout component directly:In any page rendered with that layout, including the layout component itself, you can now define styles with your font's
cssVariableto apply your custom font.In the following example, the
<h1>heading will have the custom font applied, while the paragraph<p>will not.Visit the updated fonts guide to learn more about adding custom fonts to your project.
#14550
9c282b5Thanks @ascorbic! - Adds support for live content collectionsLive content collections are a new type of content collection that fetch their data at runtime rather than build time. This allows you to access frequently updated data from CMSs, APIs, databases, or other sources using a unified API, without needing to rebuild your site when the data changes.
Live collections vs build-time collections
In Astro 5.0, the content layer API added support for adding diverse content sources to content collections. You can create loaders that fetch data from any source at build time, and then access it inside a page via
getEntry()andgetCollection(). The data is cached between builds, giving fast access and updates.However, there was no method for updating the data store between builds, meaning any updates to the data needed a full site deploy, even if the pages are rendered on demand. This meant that content collections were not suitable for pages that update frequently. Instead, these pages tended to access the APIs directly in the frontmatter. This worked, but it led to a lot of boilerplate, and meant users didn't benefit from the simple, unified API that content loaders offer. In most cases, users tended to individually create loader libraries shared between pages.
Live content collections (introduced experimentally in Astro 5.10) solve this problem by allowing you to create loaders that fetch data at runtime, rather than build time. This means that the data is always up-to-date, without needing to rebuild the site.
How to use
To use live collections, create a new
src/live.config.tsfile (alongside yoursrc/content.config.tsif you have one) to define your live collections with a live content loader using the newdefineLiveCollection()function from theastro:contentmodule:You can then use the
getLiveCollection()andgetLiveEntry()functions to access your live data, along with error handling (since anything can happen when requesting live data!):Upgrading from experimental live collections
If you were using the experimental feature, you must remove the
experimental.liveContentCollectionsflag from yourastro.config.*file:No other changes to your project code are required as long as you have been keeping up with Astro 5.x patch releases, which contained breaking changes to this experimental feature. If you experience problems with your live collections after upgrading to Astro v6 and removing this flag, please review the Astro CHANGELOG from 5.10.2 onwards for any potential updates you might have missed, or follow the current v6 documentation for live collections.
#15548
5b8f573Thanks @florian-lefebvre! - Adds a new optionalembeddedLangsprop to the<Code />component to support languages beyond the primarylangThis allows, for example, highlighting
.vuefiles with a<script setup lang="tsx">block correctly:See the
<Code />component documentation for more details.#14826
170f64eThanks @florian-lefebvre! - Adds an optionprerenderConflictBehaviorto configure the behavior of conflicting prerendered routesBy default, Astro warns you during the build about any conflicts between multiple dynamic routes that can result in the same output path. For example
/blog/[slug]and/blog/[...all]both could try to prerender the/blog/post-1path. In such cases, Astro renders only the highest priority route for the conflicting path. This allows your site to build successfully, although you may discover that some pages are rendered by unexpected routes.With the new
prerenderConflictBehaviorconfiguration option, you can now configure this further:prerenderConflictBehavior: 'error'fails the buildprerenderConflictBehavior: 'warn'(default) logs a warning and the highest-priority route winsprerenderConflictBehavior: 'ignore'silently picks the highest-priority route when conflicts occur#14946
95c40f7Thanks @ematipico! - Removes theexperimental.cspflag and replaces it with a new configuration optionsecurity.csp- (v6 upgrade guidance)#15579
08437d5Thanks @ascorbic! - Adds two new experimental flags for a Route Caching API and further configuration-level Route Rules for controlling SSR response caching.Route caching gives you a platform-agnostic way to cache server-rendered responses, based on web standard cache headers. You set caching directives in your routes using
Astro.cache(in.astropages) orcontext.cache(in API routes and middleware), and Astro translates them into the appropriate headers or runtime behavior depending on your adapter. You can also define cache rules for routes declaratively in your config usingexperimental.routeRules, without modifying route code.This feature requires on-demand rendering. Prerendered pages are already static and do not use route caching.
Getting started
Enable the feature by configuring
experimental.cachewith a cache provider in your Astro config:Using
Astro.cacheandcontext.cacheIn
.astropages, useAstro.cache.set()to control caching:In API routes and middleware, use
context.cache:Cache options
cache.set()accepts the following options:maxAge(number): Time in seconds the response is considered fresh.swr(number): Stale-while-revalidate window in seconds. During this window, stale content is served while a fresh response is generated in the background.tags(string[]): Cache tags for targeted invalidation. Tags accumulate across multipleset()calls within a request.lastModified(Date): When multipleset()calls providelastModified, the most recent date wins.etag(string): Entity tag for conditional requests.Call
cache.set(false)to explicitly opt out of caching for a request.Multiple calls to
cache.set()within a single request are merged: scalar values use last-write-wins,lastModifieduses most-recent-wins, and tags accumulate.Invalidation
Purge cached entries by tag or path using
cache.invalidate():Config-level route rules
Use
experimental.routeRulesto set default cache options for routes without modifying route code. Supports Nitro-style shortcuts for ergonomic configuration:Route patterns support static paths, dynamic parameters (
[slug]), and rest parameters ([...path]). Per-routecache.set()calls merge with (and can override) the config-level defaults.You can also read the current cache state via
cache.options:Cache providers
Cache behavior is determined by the configured cache provider. There are two types:
CDN-Cache-Control,Cache-Tag) and let the CDN handle caching. Astro strips these headers before sending the response to the client.onRequest()to intercept and cache responses in-process, adding anX-Astro-Cacheheader (HIT/MISS/STALE) for observability.Built-in memory cache provider
Astro includes a built-in, in-memory LRU runtime cache provider. Import
memoryCachefromastro/configto configure it.Features:
X-Astro-Cacheresponse header:HIT,MISS, orSTALE?b=2&a=1and?a=1&b=2hit the same entry)utm_*,fbclid,gclid, etc.) excluded from cache keys by defaultVaryheader support — responses that setVaryautomatically get separate cache entries per variantquery.exclude(glob patterns) andquery.include(allowlist)For more information on enabling and using this feature in your project, see the Experimental Route Caching docs.
For a complete overview and to give feedback on this experimental API, see the Route Caching RFC.
#15483
7be3308Thanks @florian-lefebvre! - Addsstreamingoption to thecreateApp()function in the Adapter API, mirroring the same functionality available when creating a newAppinstanceAn adapter's
createApp()function now acceptsstreaming(defaults totrue) as an option. HTML streaming breaks a document into chunks to send over the network and render on the page in order. This normally results in visitors seeing your HTML as fast as possible but factors such as network conditions and waiting for data fetches can block page rendering.HTML streaming helps with performance and generally provides a better visitor experience. In most cases, disabling streaming is not recommended.
However, when you need to disable HTML streaming (e.g. your host only supports non-streamed HTML caching at the CDN level), you can opt out of the default behavior by passing
streaming: falsetocreateApp():See more about the
createApp()function in the Adapter API reference.Patch Changes
#15423
c5ea720Thanks @matthewp! - Improves error message when a dynamic redirect destination does not match any existing route.Previously, configuring a redirect like
/categories/[category]→/categories/[category]/1in static output mode would fail with a misleading "getStaticPaths required" error. Now, Astro detects this early and provides a clear error explaining that the destination does not match any existing route.#15167
4fca170Thanks @HiDeoo! - Fixes an issue where CSS from unused components, when using content collections, could be incorrectly included between page navigations in development mode.#15565
30cd6dbThanks @ematipico! - Fixes an issue where the use of the Astro internal logger couldn't work with Cloudflare Vite plugin.#15508
2c6484aThanks @KTibow! - Fixes behavior when shortcuts are used before server is ready#15125
6feb0d7Thanks @florian-lefebvre! - Improves JSDoc annotations forAstroGlobal,AstroSharedContextandAPIContexttypes#15712
7ac43c7Thanks @florian-lefebvre! - Improvesastro infoby supporting more operating systems when copying the information to the clipboard.#15054
22db567Thanks @matthewp! - Improves zod union type error messages to show expected vs received types instead of generic "Invalid input"#15064
caf5621Thanks @ascorbic! - Fixes a bug that caused incorrect warnings of duplicate entries to be logged by the glob loader when editing a file#15801
01db4f3Thanks @ascorbic! - Improves the experience of working with experimental route caching in dev mode by replacing some errors with silent no-ops, avoiding the need to write conditional logic to handle different modesAdds a
cache.enabledproperty toCacheLikeso libraries can check whether caching is active without try/catch.#15562
e14a51dThanks @florian-lefebvre! - Removes types for theastro:ssr-manifestmodule, which was removed#15542
9760404Thanks @rururux! - Improves rendering by preservinghidden="until-found"value in attributes#15044
7cac71bThanks @florian-lefebvre! - Removes an exposed internal API of the preview server#15573
d789452Thanks @matthewp! - Clear the route cache on content changes so slug pages reflect updated data during dev.#15308
89cbcfaThanks @matthewp! - Fixes styles missing in dev for prerendered pages when using Cloudflare adapter#15435
957b9feThanks @rururux! - Improves compatibility of the built-in image endpoint with runtimes that don't support CJS dependencies correctly#15640
4c1a801Thanks @ematipico! - Reverts the support of Shiki with CSP. Unfortunately, after exhaustive tests, the highlighter can't be supported to cover all cases.Adds a warning when both Content Security Policy (CSP) and Shiki syntax highlighting are enabled, as they are incompatible due to Shiki's use of inline styles
#15415
cc3c46cThanks @ematipico! - Fixes an issue where CSP headers were incorrectly injected in the development server.#15412
c546563Thanks @florian-lefebvre! - Improves theAstroAdaptertype and how legacy adapters are handled#15322
18e0980Thanks @matthewp! - Prevents missing CSS when using both SSR and prerendered routes#15760
f49a27fThanks @ematipico! - Fixed an issue where queued rendering wasn't correctly re-using the saved nodes.#15277
cb99214Thanks @ematipico! - Fixes an issue where the functioncreateShikiHighlighterwould always create a new Shiki highlighter instance. Now the function returns a cached version of the highlighter based on the Shiki options. This should improve the performance for sites that heavily rely on Shiki and code in their pages.#15394
5520f89Thanks @florian-lefebvre! - Fixes a case where using the Fonts API withnetlify devwouldn't work because of query parameters#15605
f6473fdThanks @ascorbic! - Improves.astrocomponent SSR rendering performance by up to 2x.This includes several optimizations to the way that Astro generates and renders components on the server. These are mostly micro-optimizations, but they add up to a significant improvement in performance. Most pages will benefit, but pages with many components will see the biggest improvement, as will pages with lots of strings (e.g. text-heavy pages with lots of HTML elements).
#15721
e6e146cThanks @matthewp! - Fixes action route handling to return 404 for requests to prototype method names likeconstructorortoStringused as action paths#15497
a93c81dThanks @matthewp! - Fix dev reloads for content collection Markdown updates under Vite 7.#15780
e0ac125Thanks @ematipico! - Preventsvite.envPrefixmisconfiguration from exposingaccess: "secret"environment variables in client-side bundles. Astro now throws a clear error at startup if anyvite.envPrefixentry matches a variable declared withaccess: "secret"inenv.schema.For example, the following configuration will throw an error for
API_SECRETbecause it's defined assecretits name matches['PUBLIC_', 'API_']defined inenv.schema:#15514
999a7ddThanks @veeceey! - Fixes font flash (FOUT) during ClientRouter navigation by preserving inline<style>elements and font preload links in the head during page transitions.Previously,
@font-facedeclarations from the<Font>component were removed and re-inserted on every client-side navigation, causing the browser to re-evaluate them.#15560
170ed89Thanks @z0mt3c! - Fix X-Forwarded-Proto validation when allowedDomains includes both protocol and hostname fields. The protocol check no longer fails due to hostname mismatch against the hardcoded test URL.#15704
862d77bThanks @umutkeltek! - Fixes i18n fallback middleware intercepting non-404 responsesThe fallback middleware was triggering for all responses with status >= 300, including legitimate 3xx redirects, 403 forbidden, and 5xx server errors. This broke auth flows and form submissions on localized server routes. The fallback now correctly only triggers for 404 (page not found) responses.
#15661
7150a2eThanks @ematipico! - Fixes a build error when generating projects with 100k+ static routes.#15580
a92333cThanks @ematipico! - Fixes a build error when generating projects with a large number of static routes#15176
9265546Thanks @matthewp! - Fixes hydration for framework components inside MDX when usingAstro.slots.render()Previously, when multiple framework components with
client:*directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.#15506
074901fThanks @ascorbic! - Fixes a race condition where concurrent requests to dynamic routes in the dev server could produce incorrect params.#15444
10b0422Thanks @AhmadYasser1! - FixesAstro.rewritereturning 404 when rewriting to a URL with non-ASCII charactersWhen rewriting to a path containing non-ASCII characters (e.g.,
/redirected/héllo), the route lookup compared encodeddistURLhrefs against decoded pathnames, causing the comparison to always fail and resulting in a 404. This fix compares against the encoded pathname instead.#15728
12ca621Thanks @SvetimFM! - Improves internal state retention for persisted elements during view transitions, especially avoiding WebGL context loss in Safari and resets of CSS transitions and iframes in modern Chromium and Firefox browsers#15279
8983f17Thanks @ematipico! - Fixes an issue where the dev server would serve files like/README.mdfrom the project root when they shouldn't be accessible. A new route guard middleware now blocks direct URL access to files that exist outside ofsrcDirandpublicDir, returning a 404 instead.#15703
829182bThanks @matthewp! - Fixes server islands returning a 500 error in dev mode for adapters that do not setadapterFeatures.buildOutput(e.g.@astrojs/netlify)#15749
573d188Thanks @ascorbic! - Fixes a bug that causedsession.regenerate()to silently lose session dataPreviously, regenerated session data was not saved under the new session ID unless
set()was also called.#15549
be1c87eThanks @0xRozier! - Fixes an issue where original (unoptimized) images from prerendered pages could be kept in the build output during SSR builds.#15454
b47a4e1Thanks @Fryuni! - Fixes a race condition in the content layer which could result in dropped content collection entries.#15685
1a323e5Thanks @jcayzac! - Fix regression where SVG images in content collectionimage()fields could not be rendered as inline components. This behavior is now restored while preserving the TLA deadlock fix.#15603
5bc2b2cThanks @0xRozier! - Fixes a deadlock that occurred when using SVG images in content collections#15385
9e16d63Thanks @matthewp! - Fixes content layer loaders that use dynamic importsContent collection loaders can now use
await import()andimport.meta.glob()to dynamically import modules during build. Previously, these would fail with "Vite module runner has been closed."#15565
30cd6dbThanks @ematipico! - Fixes an issue where the use of theCodecomponent would result in an unexpected error.#15125
6feb0d7Thanks @florian-lefebvre! - Fixes remote imagesEtagheader handling by disabling internal cache#15317
7e1e35aThanks @matthewp! - Fixes?rawimports failing when used in both SSR and prerendered routes#15809
94b4a46Thanks @Princesseuh! - Fixesfitdefaults not being applied unlesslayoutwas also specified#15563
e959698Thanks @ematipico! - Fixes an issue where warnings would be logged during the build using one of the official adapters#15121
06261e0Thanks @ematipico! - Fixes a bug where the Astro, with the Cloudflare integration, couldn't correctly serve certain routes in the development server.#15585
98ea30cThanks @matthewp! - Add a default body size limit for server actions to prevent oversized requests from exhausting memory.#15264
11efb05Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22#15778
4ebc1e3Thanks @ematipico! - Fixes an issue where the computedclientAddresswas incorrect in cases of a Request header with multiple values. TheclientAddressis now also validated to contain only characters valid in IP addresses, rejecting injection payloads.#15565
30cd6dbThanks @ematipico! - Fixes an issue where the new Astro v6 development server didn't log anything when navigating the pages.#15024
22c48baThanks @florian-lefebvre! - Fixes a case where JSON schema generation would fail for unrepresentable types#15669
d5a888bThanks @florian-lefebvre! - Removes thecssescdependencyThis CommonJS dependency could sometimes cause errors because Astro is ESM-only. It is now replaced with a built-in ESM-friendly implementation.
#15740
c5016fcThanks @matthewp! - Removes an escape hatch that skipped attribute escaping for URL values containing&, ensuring all dynamic attribute values are consistently escaped#15756
b6c64d1Thanks @matthewp! - Hardens the dev server by validating Sec-Fetch metadata headers to restrict cross-origin subresource requests#15744
fabb710Thanks @matthewp! - Fixes cookie handling during error page rendering to ensure cookies set by middleware are consistently included in the response#15776
e9a9cc6Thanks @matthewp! - Hardens error page response merging to ensure framing headers from the original response are not carried over to the rendered error page#15759
39ff2a5Thanks @matthewp! - Adds a newbodySizeLimitoption to the@astrojs/nodeadapterYou can now configure a maximum allowed request body size for your Node.js standalone server. The default limit is 1 GB. Set the value in bytes, or pass
0to disable the limit entirely:#15777
02e24d9Thanks @matthewp! - Fixes CSRF origin check mismatch by passing the actual server listening port tocreateRequest, ensuring the constructed URL origin includes the correct port (e.g.,http://localhost:4321instead ofhttp://localhost). Also restrictsX-Forwarded-Prototo only be trusted whenallowedDomainsis configured.#15742
9d9699cThanks @matthewp! - HardensclientAddressresolution to respectsecurity.allowedDomainsforX-Forwarded-For, consistent with the existing handling ofX-Forwarded-Host,X-Forwarded-Proto, andX-Forwarded-Port. TheX-Forwarded-Forheader is now only used to determineAstro.clientAddresswhen the request's host has been validated against anallowedDomainsentry. Without a matching domain,clientAddressfalls back to the socket's remote address.#15768
6328f1aThanks @matthewp! - Hardens internal cookie parsing to use a null-prototype object consistently for the fallback path, aligning with how the cookie library handles parsed values#15125
6feb0d7Thanks @florian-lefebvre! - Fixes images not working in development when using setups with port forwarding#15811
2ba0db5Thanks @ematipico! - Fixes integration-injected scripts (e.g. Alpine.js viainjectScript()) not being loaded in the dev server when using non-runnable environment adapters like@astrojs/cloudflare.#15208
8dbdd8eThanks @matthewp! - Makessession.driveroptional in config schema, allowing adapters to provide default driversAdapters like Cloudflare, Netlify, and Node provide default session drivers, so users can now configure session options (like
ttl) without explicitly specifying a driver.#15260
abca1ebThanks @ematipico! - Fixes an issue where adding new pages weren't correctly shown when using the development server.#15591
1ed07bfThanks @renovate! - Upgradesdevalueto v5.6.3#15137
2f70bf1Thanks @matthewp! - Addslegacy.collectionsBackwardsCompatflag that restores v5 backwards compatibility behavior for legacy content collections - (v6 upgrade guidance)When enabled, this flag allows:
type: 'content'ortype: 'data'src/content/config.ts(legacy location)entry.slugandentry.render()methodsThis is a temporary migration helper for v6 upgrades. Migrate collections to the Content Layer API, then disable this flag.
#15550
58df907Thanks @florian-lefebvre! - Improves the JSDoc annotations for theAstroAdaptertype#15696
a9fd221Thanks @Princesseuh! - Fixes images not working in MDX when using the Cloudflare adapter in certain cases#15386
a0234a3Thanks @OliverSpeir! - Updatesastro add cloudflareto use the latest validcompatibility_datein the wrangler config, if available#15036
f125a73Thanks @florian-lefebvre! - Fixes certain aliases not working when using images in JSON files with the content layer#15693
4db2089Thanks @ArmandPhilippot! - Fixes the links to Astro Docs to match the v6 structure.#15093
8d5f783Thanks @matthewp! - Reduces build memory by filtering routes per environment so each only builds the pages it needs#15268
54e5cc4Thanks @rururux! - fix: avoid creating unused images during build in Picture component#15757
631aaedThanks @matthewp! - Hardens URL pathname normalization to consistently handle backslash characters after decoding, ensuring middleware and router see the same canonical pathname#15337
7ff7b11Thanks @ematipico! - Fixes a bug where the development server couldn't serve newly created new pages while the development server is running.#15535
dfe2e22Thanks @florian-lefebvre! - Fixes the types ofcreateApp()exported fromastro/app/entrypoint#15073
2a39c32Thanks @ascorbic! - Don't log an error when there is no content config#15717
4000aaaThanks @matthewp! - Ensures that URLs with multiple leading slashes (e.g.//admin) are normalized to a single slash before reaching middleware, so that pathname checks likecontext.url.pathname.startsWith('/admin')work consistently regardless of the request URL format#15450
50c9129Thanks @florian-lefebvre! - Fixes a case wherebuild.serverEntrywould not be respected when using the new Adapter API#15331
4592be5Thanks @matthewp! - Fixes an issue where API routes would overwrite public files during build. Public files now correctly take priority over generated routes in both dev and build modes.#15414
faedcc4Thanks @sapphi-red! - Fixes a bug where some requests to the dev server didn't start with the leading/.#15419
a18d727Thanks @ematipico! - Fixes an issue where theaddcommand could accept any arbitrary value, leading the possible command injections. Nowaddand--addacceptsvalues that are only acceptable npmjs.org names.
#15507
07f6610Thanks @matthewp! - Avoid bundling SSR renderers when only API endpoints are dynamic#15125
6feb0d7Thanks @florian-lefebvre! - Reduces Astro’s install size by around 8 MB#15752
918d394Thanks @ascorbic! - Fixes an issue where a session ID from a cookie with no matching server-side data was accepted as-is. The session now generates a new ID when the cookie value has no corresponding storage entry.#15743
3b4252aThanks @matthewp! - Hardens config-based redirects with catch-all parameters to prevent producing protocol-relative URLs (e.g.//example.com) in theLocationheader#15761
8939751Thanks @ematipico! - Fixes an issue where it wasn't possible to setexperimental.queuedRendering.poolSizeto0.#15633
9d293c2Thanks @jwoyo! - Fixes a case where<script>tags from components passed as slots to server islands were not included in the response#15491
6c60b05Thanks @matthewp! - Fixes a case where settingvite.server.allowedHosts: truewas turned into an invalid array#15459
a4406b4Thanks @florian-lefebvre! - Fixes a case wherecontext.cspwas logging warnings in development that should be logged in production only#15125
6feb0d7Thanks @florian-lefebvre! - Enables the ClientRouter to preserve the original hash part of the target URL during server side redirects.#15133
53b125bThanks @HiDeoo! - Fixes an issue where adding or removing<style>tags in Astro components would not visually update styles during development without restarting the development server.#15362
dbf71c0Thanks @jcayzac! - FixesinferSizebeing kept in the HTML attributes of the emitted<img>when that option is used with an image that is not remote.#15421
bf62b6fThanks @Princesseuh! - Removes unintended logging#15732
2ce9e74Thanks @florian-lefebvre! - Updates docs links to point to the stable release#15718
14f37b8Thanks @florian-lefebvre! - Fixes a case where internal headers may leak when rendering error pages#15214
6bab8c9Thanks @ematipico! - Fixes an issue where the internal performance timers weren't correctly updated to reflect new build pipeline.#15112
5751d2bThanks @HiDeoo! - Fixes a Windows-specific build issue when importing an Astro component with a<script>tag using an import alias.#15345
840fbf9Thanks @matthewp! - Fixes an issue where.sqlfiles (and other non-asset module types) were incorrectly moved to the client assets folder during SSR builds, causing "no such module" errors at runtime.The
ssrMoveAssetsfunction now reads the Vite manifest to determine which files are actual client assets (CSS and static assets like images) and only moves those, leaving server-side module files in place.#15259
8670a69Thanks @ematipico! - Fixes an issue where styles weren't correctly reloaded when using the@astrojs/cloudflareadapter.#15473
d653b86Thanks @matthewp! - Improves Host header handling for SSR deployments behind proxies#15047
5580372Thanks @matthewp! - Fixes wrangler config template inastro add cloudflareto use correct entrypoint and compatibility date#14589
7038f07Thanks @43081j! - Improves CLI styling#15586
35bc814Thanks @matthewp! - Fixes an issue where allowlists were not being enforced when handling remote images#15422
68770efThanks @matthewp! - Upgrade to @astrojs/compiler@3.0.0-beta#15205
12adc55Thanks @martrapp! - Fixes an issue where theastro:page-loadevent did not fire on initial page loads.#15125
6feb0d7Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyChanges the font format downloaded by default when using the experimental Fonts API. Additionally, adds a new
formatsconfiguration option to specify which font formats to download.Previously, Astro was opinionated about which font sources would be kept for usage, mainly keeping
woff2andwofffiles.You can now specify what font formats should be downloaded (if available). Only
woff2files are downloaded by default.What should I do?
If you were previously relying on Astro downloading the
woffformat, you will now need to specify this explicitly with the newformatsconfiguration option. Additionally, you may also specify any additional file formats to download if available:#15179
8c8aee6Thanks @HiDeoo! - Fixes an issue when importing using an import alias a file with a name matching a directory name.#15036
f125a73Thanks @florian-lefebvre! - Fixes a vite warning log during builds when using npm#15269
6f82aaeThanks @ematipico! - Fixes a regression wherebuild.serverEntrystopped working as expected.#15053
674b63fThanks @matthewp! - Excludesastro:*andvirtual:astro:*from client optimizeDeps in core. Needed for prefetch users since virtual modules are now in the dependency graph.#15764
44daecfThanks @matthewp! - Fixes form actions incorrectly auto-executing during error page rendering. When an error page (e.g. 404) is rendered, form actions from the original request are no longer executed, since the full request handling pipeline is not active.#15788
a91da9fThanks @florian-lefebvre! - Reverts changes made to TSConfig templates#15657
cb625b6Thanks @qzio! - Adds a newsecurity.actionBodySizeLimitoption to configure the maximum size of Astro Actions request bodies.This lets you increase the default 1 MB limit when your actions need to accept larger payloads. For example, actions that handle file uploads or large JSON payloads can now opt in to a higher limit.
If you do not set this option, Astro continues to enforce the 1 MB default to help prevent abuse.
#15176
9265546Thanks @matthewp! - Fixes scripts in components not rendering when a sibling<Fragment slot="...">exists but is unusedUpdated dependencies [
bbb5811,4ebc1e3,cb99214,80f0225,727b0a2,4e7f3e8,a164c77,1fa4177,7c55f80,cf6ea6b,6f19ecc,f94d3c5,a18d727,240c317,745e632]:v5.18.2Compare Source
Patch Changes
8f7d8c4Thanks @matthewp! - Populates styles in the SSR manifest for prerendered routes. Previously, prerendered routes hadstyles: []in the manifest, making it impossible for workers or middleware to discover which CSS files a prerendered page uses.v5.18.1Compare Source
Patch Changes
c2cd371]:v5.18.0Compare Source
Minor Changes
#15589
b7dd447Thanks @qzio! - Adds a newsecurity.actionBodySizeLimitoption to configure the maximum size of Astro Actions request bodies.This lets you increase the default 1 MB limit when your actions need to accept larger payloads. For example, actions that handle file uploads or large JSON payloads can now opt in to a higher limit.
If you do not set this option, Astro continues to enforce the 1 MB default to help prevent abuse.
Patch Changes
efae11cThanks @qzio! - Fix X-Forwarded-Proto validation when allowedDomains includes both protocol and hostname fields. The protocol check no longer fails due to hostname mismatch against the hardcoded test URL.v5.17.3Compare Source
Patch Changes
#15564
522f880Thanks @matthewp! - Add a default body size limit for server actions to prevent oversized requests from exhausting memory.#15569
e01e98bThanks @matthewp! - Respect image allowlists when inferring remote image sizes and reject remote redirects.v5.17.2Compare Source
Patch Changes
c13b536Thanks @matthewp! - Improves Host header handling for SSR deployments behind proxiesv5.17.1Compare Source
Patch Changes
#15334
d715f1fThanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyRemoves the
getFontBuffer()helper function exported fromastro:assetswhen using the experimental Fonts APIThis experimental feature introduced in v15.6.13 ended up causing significant memory usage during build. This feature has been removed and will be reintroduced after further exploration and testing.
If you were relying on this function, you can replicate the previous behavior manually:
node:fsfontDataandcontext.urlv5.17.0Compare Source
Minor Changes
#14932
b19d816Thanks @patrickarlt! - Adds support for returning a Promise from theparser()option of thefile()loaderThis enables you to run asynchronous code such as fetching remote data or using async parsers when loading files with the Content Layer API.
For example:
See the
parser()reference documentation for more information.#15171
f220726Thanks @mark-ignacio! - Adds a new, optionalkernelconfiguration option to select a resize algorithm in the Sharp image serviceBy default, Sharp resizes images with the
lanczos3kernel. This new config option allows you to set the default resizing algorithm to any resizing option supported by Sharp (e.g.linear,mks2021).Kernel selection can produce quite noticeable differences depending on various characteristics of the source image - especially drawn art - so changing the kernel gives you more control over the appearance of images on your site:
This selection will apply to all images on your site, and is not yet configurable on a per-image basis. For more information, see Sharps documentation on resizing images.
#15063
08e0fd7Thanks @jmortlock! - Adds a newpartitionedoption when setting a cookie to allow creating partitioned cookies.Partitioned cookies can only be read within the context of the top-level site on which they were set. This allows cross-site tracking to be blocked, while still enabling legitimate uses of third-party cookies.
You can create a partitioned cookie by passing
partitioned: truewhen setting a cookie. Note that partitioned cookies must also be set withsecure: true:For more information, see the
AstroCookieSetOptionsAPI reference.#15022
f1fce0eThanks @ascorbic! - Adds a newretainBodyoption to theglob()loader to allow reducing the size of the data store.Currently, the
glob()loader stores the raw body of each content file in the entry, in addition to the rendered HTML.The
retainBodyoption defaults totrue, but you can set it tofalseto prevent the raw body of content files from being stored in the data store. This significantly reduces the deployed size of the data store and helps avoid hitting size limits for sites with very large collections.The rendered body will still be available in the
entry.rendered.htmlproperty for markdown files, and theentry.filePathproperty will still point to the original file.When
retainBodyisfalse,entry.bodywill beundefinedinstead of containing the raw file contents.#15153
928529fThanks @jcayzac! - Adds a newbackgroundproperty to the<Image />component.This optional property lets you pass a background color to flatten the image with. By default, Sharp uses a black background when flattening an image that is being converted to a format that does not support transparency (e.g.
jpeg). Providing a value forbackgroundon an<Image />component, or passing it to thegetImage()helper, will flatten images using that color instead.This is especially useful when the requested output format doesn't support an alpha channel (e.g.
jpeg) and can't support transparent backgrounds.See more about this new property in the image reference docs
#15015
54f6006Thanks @tony! - Adds optionalplacementconfig option for the dev toolbar.You can now configure the default toolbar position (
'bottom-left','bottom-center', or'bottom-right') viadevToolbar.placementin your Astro config. This option is helpful for sites with UI elements (chat widgets, cookie banners) that are consistently obscured by the toolbar in the dev environment.You can set a project default that is consistent across environments (e.g. dev machines, browser instances, team members):
User preferences from the toolbar UI (stored in
localStorage) still take priority, so this setting can be overridden in individual situations as necessary.v5.16.16Compare Source
Patch Changes
#15281
a1b80c6Thanks @matthewp! - Ensures server island requests carry an encrypted component export identifier so they do not accidentally resolve to the wrong component.#15304
02ee3c7Thanks @cameronapak! - Fix: Remove await from getActionResult example#15324
ab41c3eThanks @Princesseuh! - Fixes an issue where certain unauthorized links could be rendered as clickable in the error overlayv5.16.15Compare Source
Patch Changes
0aafc83Thanks @florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local providerv5.16.14Compare Source
Patch Changes
#15213
c775fceThanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyUpdates how the local provider must be used when using the experimental Fonts API
Previously, there were 2 kinds of font providers: remote and local.
Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:
Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.
See the experimental Fonts API docs for more information.
#15213
c775fceThanks @florian-lefebvre! - ExposesrootonFontProviderinit()contextWhen building a custom
FontProviderfor the experimental Fonts API, theinit()method receives acontext. This context now exposes arootURL, useful for resolving local files:#15185
edabeaaThanks @EricGrill! - Add.vercelto.gitignorewhen adding the Vercel adapter viaastro add vercelv5.16.13Compare Source
Patch Changes
#15182
cb60ee1Thanks @florian-lefebvre! - Adds a newgetFontBuffer()method to retrieve font file buffers when using the experimental Fonts APIThe
getFontData()helper function fromastro:assetswas introduced in 5.14.0 to provide access to font family data for use outside of Astro. One of the goals of this API was to be able to retrieve buffers using URLs.However, it turned out to be impractical and even impossible during prerendering.
Astro now exports a new
getFontBuffer()helper function fromastro:assetsto retrieve font file buffers from URL returned bygetFontData(). For example, when using satori to generate Open Graph images:See the experimental Fonts API documentation for more information.
v5.16.12Compare Source
Patch Changes
#15175
47ae148Thanks @florian-lefebvre! - Allows experimental Font providers to specify family optionsPreviously, an Astro
FontProvidercould only accept options at the provider level when called. That could result in weird data structures for family-specific options.Astro
FontProviders can now declare family-specific options, by specifying a generic:Once the font provider is registered in the Astro config, types are automatically inferred:
#15175
47ae148Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyUpdates how options are passed to the Google and Google Icons font providers when using the experimental Fonts API
Previously, the Google and Google Icons font providers accepted options that were specific to given font families.
These options must now be set using the
optionsproperty instead. For example using the Google provider:#15200
c0595b3Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyRemoves
getFontData()exported fromastro:assetswithfontDatawhen using the experimental Fonts APIAccessing font data can be useful for advanced use cases, such as generating meta tags or Open Graph images. Before, we exposed a
getFontData()helper function to retrieve the font data for a givencssVariable. That was however limiting for programmatic usages that need to access all font data.The
getFontData()helper function is removed and replaced by a newfontDataobject:We may reintroduce
getFontData()later on for a more friendly DX, based on your feedback.#15254
8d84b30Thanks @lamalex! - Fixes CSSassetsPrefixwith remote URLs incorrectly prepending a forward slashWhen using
build.assetsPrefixwith a remote URL (e.g.,https://cdn.example.com) for CSS assets, the generated<link>elements were incorrectly getting a/prepended to the full URL, resulting in invalid URLs like/https://cdn.example.com/assets/style.css.This fix checks if the stylesheet link is a remote URL before prepending the forward slash.
#15178
731f52dThanks @kedarvartak! - Fixes an issue where stopping the dev server withq+enterincorrectly created adistfolder and copied font files when using the experimental Fonts API#15230
3da6272Thanks @rahuld109! - Fixes greedy regex in error message markdown rendering that caused link syntax examples to capture extra characters#15253
2a6315aThanks @matthewp! - Fixes hydration for React components nested inside HTML elements in MDX files#15227
9a609f4Thanks @matthewp! - Fixes styles not being included for conditionally rendered Svelte 5 components in production builds#14607
ee52160Thanks @simensfo! - Reintroduces css deduplication for hydrated client components. Ensures assets already added to a client chunk are not flagged as orphanedv5.16.11Compare Source
Patch Changes
#15017
9e7a3c8Thanks @ixchio! - Fixes CSS double-bundling when the same CSS file is imported in both a page's frontmatter and a component's script tag#15225
6fe62e1Thanks @ematipico! - Updates to the latest version ofdevaluev5.16.10Compare Source
Patch Changes
2fa19c4- Improved error handling in the rendering phaseAdded defensive validation in
App.render()and#renderError()to provide a descriptive error message when a route module doesn't have a valid page function.#15199
d8e64efThanks @ArmandPhilippot! - Fixes the links to Astro Docs so that they match the current docs structure.#15169
b803d8bThanks @rururux! - fix: fix image 500 error when moving dist directory in standalone Node#14622
9b35c62Thanks @aprici7y! - Fixes CSS url() references to public assets returning 404 in dev mode when base path is configured#15219
43df4ceThanks @matthewp! - Upgrades thediffpackage to v8v5.16.9Compare Source
Patch Changes
#15174
37ab65aThanks @florian-lefebvre! - Adds Google Icons to built-in font providersTo start using it, access it on
fontProviders:#15150
a77c4f4Thanks @matthewp! - Fixes hydration for framework components inside MDX when usingAstro.slots.render()Previously, when multiple framework components with
client:*directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.#15130
9b726c4Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyChanges how font providers are implemented with updates to the
FontProvidertypeThis is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on
unifonttypes. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely onunifonttypes will require an update to your project code.Previously, an Astro
FontProviderwas made of a config and a runtime part. It relied directly onunifonttypes, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registries).
What should I do?
If you were using a 3rd-party
unifontfont provider, you will now need to write an AstroFontProviderusing it under the hood. For example:9cd5b87Thanks @matthewp! - Fixes scripts in components not rendering when a sibling<Fragment slot="...">exists but is unusedv5.16.8Compare Source
Patch Changes
#15124
81db3c0Thanks @leonace924! - Fixes an issue where requests with query parameters to thebasepath would return a 404 if trailingSlash was not'ignore'in development#15152
39ee41fThanks @rururux! - Fixes a case wherecontext.cookies.set()would be overridden when setting cookies via response headers in development#15140
6f6f8f8Thanks @cameronraysmith! - Fixes esbuild warning due to dead code in assets virtual module#15127
2cff904Thanks @Princesseuh! - Updates "Unsupported page types found" error to only appear in more realistic cases#15149
34f84c2Thanks @rahuld109! - Skips "Use the Image component" audit warning for images inside framework components (React, Vue, Svelte, etc.)v5.16.7Compare Source
Patch Changes
#15122
b137946Thanks @florian-lefebvre! - Improves JSDoc annotations forAstroGlobal,AstroSharedContextandAPIContexttypes#15123
3f58fa2Thanks @43081j! - Improves rendering performance by grouping render chunks when emitting from async iterables to avoid encoding costs#14954
7bec4bdThanks @volpeon! - Fixes remote imagesEtagheader handling by disabling internal cache#15052
b2bcd5aThanks @Princesseuh! - Fixes images not working in development when using setups with port forwarding#15028
87b19b8Thanks @Princesseuh! - Fixes certain aliases not working when using images in JSON files with the content layer#15118
cfa382bThanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyRemoves the
defineAstroFontProvider()type helper.If you are building a custom font provider, remove any occurrence of
defineAstroFontProvider()and use theFontProvidertype instead:#15055
4e28db8Thanks @delucis! - Reduces Astro’s install size by around 8 MB#15088
a19140fThanks @martrapp! - Enables the ClientRouter to preserve the original hash part of the target URL during server side redirects.#15117
b1e8e32Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyChanges the font format downloaded by default when using the experimental Fonts API. Additionally, adds a new
formatsconfiguration option to specify which font formats to download.Previously, Astro was opinionated about which font sources would be kept for usage, mainly keeping
woff2andwofffiles.You can now specify what font formats should be downloaded (if available). Only
woff2files are downloaded by default.What should I do?
If you were previously relying on Astro downloading the
woffformat, you will now need to specify this explicitly with the newformatsconfiguration option. Additionally, you may also specify any additional file formats to download if available:8115752Thanks @florian-lefebvre! - Fixes a vite warning log during builds when using npmv5.16.6Compare Source
Patch Changes
#14982
6849e38Thanks @Princesseuh! - Fixes images outside the project directory not working when using astro:assets in development mode#14987
9dd9fcaThanks @Princesseuh! - Fixes SVGs not working in dev mode when using the passthrough image service#15014
a178422Thanks @delucis! - Adds support for extending the type of the props accepted by Astro’s<Image>component,<Picture>component, andgetImage()API.v5.16.5Compare Source
Patch Changes
#14985
c016f10Thanks @florian-lefebvre! - Fixes a case where JSDoc annotations wouldn't show for fonts related APIs in the Astro config#14973
ed7cc2fThanks @amankumarpandeyin! - Fixes performance regression and OOM errors when building medium-sized blogs with many content entries. Replaced O(n²) object spread pattern with direct mutation ingenerateLookupMap.#14958
70eb542Thanks @ascorbic! - Gives a helpful error message if a user setsoutput: "hybrid"in their Astro config.The option was removed in Astro 5, but lots of content online still references it, and LLMs often suggest it. It's not always clear that the replacement is
output: "static", rather thanoutput: "server". This change adds a helpful error message to guide humans and robots.#14901
ef53716Thanks @Darknab! - Updates theglob()loader to log a warning when duplicated IDs are detectedUpdated dependencies [
d8305f8]:v5.16.4Compare Source
Patch Changes
#14940
2cf79c2Thanks @ematipico! - Fixes a bug where Astro didn't properly combine CSP resources from thecspconfiguration with those added using the runtime API (Astro.csp.insertDirective()) to form grammatically correct CSP headersNow Astro correctly deduplicate CSP resources. For example, if you have a global resource in the configuration file, and then you add a
a new one using the runtime APIs.
v5.16.3Compare Source
Patch Changes
#14889
4bceeb0Thanks @florian-lefebvre! - Fixes actions types when using specific TypeScript configurations#14929
e0f277dThanks @matthewp! - Fixes authentication bypass via double URL encoding in middlewarePrevents attackers from bypassing path-based authentication checks using multi-level URL encoding (e.g.,
/%2561dmininstead of/%61dmin). Pathnames are now validated after decoding to ensure no additional encoding remains.v5.16.2Compare Source
Patch Changes
#14876
b43dc7fThanks @florian-lefebvre! - Fixes a vite warning log during builds when using npm#14884
10273e0Thanks @florian-lefebvre! - Fixes a case where setting the status of a page to404in ssr would show an empty page (or404.astropage if provided) instead of using the current pagev5.16.1Compare Source
Patch Changes
#15281
a1b80c6Thanks @matthewp! - Ensures server island requests carry an encrypted component export identifier so they do not accidentally resolve to the wrong component.#15304
02ee3c7Thanks @cameronapak! - Fix: Remove await from getActionResult example#15324
ab41c3eThanks @Princesseuh! - Fixes an issue where certain unauthorized links could be rendered as clickable in the error overlayv5.16.0Compare Source
Minor Changes
#13880
1a2ed01Thanks @azat-io! - Adds experimental SVGO optimization support for SVG assetsAstro now supports automatic SVG optimization using SVGO during build time. This experimental feature helps reduce SVG file sizes while maintaining visual quality, improving your site's performance.
To enable SVG optimization with default settings, add the following to your
astro.config.mjs:To customize optimization, pass a SVGO configuration object:
For more information on enabling and using this feature in your project, see the experimental SVG optimization docs.
#14810
2e845feThanks @ascorbic! - Adds a hint for code agents to use the--yesflag to skip prompts when runningastro add#14698
f42ff9bThanks @mauriciabad! - Adds theActionInputSchemautility type to automatically infer the TypeScript type of an action's input based on its Zod schemaFor example, this type can be used to retrieve the input type of a form action:
#14574
4356485Thanks @jacobdalamb! - Adds new CLI shortcuts available when runningastro preview:o+enter: open the site in your browserq+enter: quit the previewh+enter: print all available shortcutsPatch Changes
#14813
e1dd377Thanks @ematipico! - Removespicocolorsas dependency in favor of the forkpiccolore.#14609
d774306Thanks @florian-lefebvre! - Improvesastro info#14796
c29a785Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API onlyUpdates the default
subsetsto["latin"]Subsets have been a common source of confusion: they caused a lot of files to be downloaded by default. You now have to manually pick extra subsets.
Review your Astro config and update subsets if you need, for example if you need greek characters:
v5.15.9Compare Source
Patch Changes
#14786
758a891Thanks @mef! - Add handling of invalid encrypted props and slots in server islands.#14783
504958fThanks @florian-lefebvre! - Improves the experimental Fonts API build log to show the number of downloaded files. This can help spotting excessive downloading because of misconfiguration#14791
9e9c528Thanks @Princesseuh! - Changes the remote protocol checks for images to require explicit authorization in order to use data URIs.In order to allow data URIs for remote images, you will need to update your
astro.config.mjsfile to include the following configuration:#14787
0f75f6bThanks @matthewp! - Fixes wildcard hostname pattern matching to correctly reject hostnames without dotsPreviously, hostnames like
localhostor other single-part names would incorrectly match patterns like*.example.com. The wildcard matching logic has been corrected to ensure that only valid subdomains matching the pattern are accepted.#14776
3537876Thanks @ktym4a! - Fixes the behavior ofpassthroughImageServiceso it does not generate webp.Updated dependencies [
9e9c528,0f75f6b]:v5.15.8Compare Source
Patch Changes
#14772
00c579aThanks @matthewp! - Improves the security of Server Islands slots by encrypting them before transmission to the browser, matching the security model used for props. This improves the integrity of slot content and prevents injection attacks, even when component templates don't explicitly support slots.Slots continue to work as expected for normal usage—this change has no breaking changes for legitimate requests.
#14771
6f80081Thanks @matthewp! - Fix middleware pathname matching by normalizing URL-encoded pathsMiddleware now receives normalized pathname values, ensuring that encoded paths like
/%61dminare properly decoded to/adminbefore middleware checks. This prevents potential security issues where middleware checks might be bypassed through URL encoding.v5.15.7Compare Source
Patch Changes
#14765
03fb47cThanks @florian-lefebvre! - Fixes a case whereprocess.envwouldn't be properly populated during the build#14690
ae7197dThanks @fredriknorlin! - Fixes a bug where Astro's i18n fallback system withfallbackType: 'rewrite'would not generate fallback files for pages whose filename started with a locale key.v5.15.6Compare Source
Patch Changes
#14751
18c55e1Thanks @delucis! - Fixes hydration of client components when running the dev server and using a barrel file that re-exports both Astro and UI framework components.#14750
35122c2Thanks @florian-lefebvre! - Updates the experimental Fonts API to log a warning if families with a conflictingcssVariableare provided#14737
74c8852Thanks @Arecsu! - Fixes an error when usingtransition:persistwith components that use declarative Shadow DOM. Astro now avoids re-attaching a shadow root if one already exists, preventing"Unable to re-attach to existing ShadowDOM"navigation errors.#14750
35122c2Thanks @florian-lefebvre! - Updates the experimental Fonts API to allow for more granular configuration of remote font familiesA font family is defined by a combination of properties such as weights and styles (e.g.
weights: [500, 600]andstyles: ["normal", "bold"]), but you may want to download only certain combinations of these.For greater control over which font files are downloaded, you can specify the same font (ie. with the same
cssVariable,name, andproviderproperties) multiple times with different combinations. Astro will merge the results and download only the required files. For example, it is possible to download normal500and600while downloading only italic500:v5.15.5Compare Source
Patch Changes
#14712
91780cfThanks @florian-lefebvre! - Fixes a case where build'sprocess.envwould be inlined in the server output#14713
666d5a7Thanks @florian-lefebvre! - Improves fallbacks generation when using the experimental Fonts API#14743
dafbb1bThanks @matthewp! - ImprovesX-Forwardedheader validation to prevent cache poisoning and header injection attacks. Now properly validatesX-Forwarded-Proto,X-Forwarded-Host, andX-Forwarded-Portheaders against configuredallowedDomainspatterns, rejecting malformed or suspicious values. This is especially important when running behind a reverse proxy or load balancer.v5.15.4Compare Source
Patch Changes
#14703
970ac0fThanks @ArmandPhilippot! - Adds missing documentation for some public utilities exported fromastro:i18n.#14715
3d55c5dThanks @ascorbic! - Adds support for client hydration ingetContainerRenderer()The
getContainerRenderer()function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually callcontainer.addClientRenderer()with the appropriate client renderer entrypoint.See the
container-with-vitestdemo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.#14711
a4d284dThanks @deining! - Fixes typos in documenting our error messages and public APIs.#14701
9be54c7Thanks @florian-lefebvre! - Fixes a case where the experimental Fonts API would filter available font files too aggressively, which could prevent the download of woff files when using the google providerv5.15.3Compare Source
Patch Changes
#14627
b368de0Thanks @matthewp! - Fixes skew protection support for images and font URLsAdapter-level query parameters (
assetQueryParams) are now applied to all image and font asset URLs, including:/_imageendpoint#14631
3ad33f9Thanks @KurtGokhan! - Adds theastro/jsx-dev-runtimeexport as an alias forastro/jsx-runtimev5.15.2Compare Source
Patch Changes
#14623
c5fe295Thanks @delucis! - Fixes a leak of server runtime code when importing SVGs in client-side code. Previously, when importing an SVG file in client code, Astro could end up adding code for rendering SVGs on the server to the client bundle.#14621
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVEv5.15.1Compare Source
Patch Changes
18552c7Thanks @ematipico! - Fixes a regression introduced in Astro v5.14.7 that caused?urlimports to not work correctly. This release reverts #14142.v5.15.0Compare Source
Minor Changes
#14543
9b3241dThanks @matthewp! - Adds two new adapter configuration optionsassetQueryParamsandinternalFetchHeadersto the Adapter API.Official and community-built adapters can now use
client.assetQueryParamsto specify query parameters that should be appended to asset URLs (CSS, JavaScript, images, fonts, etc.). The query parameters are automatically appended to all generated asset URLs during the build process.Adapters can also use
client.internalFetchHeadersto specify headers that should be included in Astro's internal fetch calls (Actions, View Transitions, Server Islands, Prefetch).This enables features like Netlify's skew protection, which requires the deploy ID to be sent with both internal requests and asset URLs to ensure client and server versions match during deployments.
#14489
add4277Thanks @dev-shetty! - Adds a new Copy to Clipboard button to the error overlay stack trace.When an error occurs in dev mode, you can now copy the stack trace with a single click to more easily share it in a bug report, a support thread, or with your favorite LLM.
#14564
5e7cebbThanks @florian-lefebvre! - Updatesastro add cloudflareto scaffold more configuration filesRunning
astro add cloudflarewill now emitwrangler.jsoncandpublic/.assetsignore, allowing your Astro project to work out of the box as a worker.Patch Changes
#14591
3e887ecThanks @matthewp! - Adds TypeScript support for thecomponentsprop on MDXContentcomponent when usingawait render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.#14598
7b45c65Thanks @delucis! - Reduces terminal text styling dependency size by switching fromkleurtopicocolors#13826
8079482Thanks @florian-lefebvre! - Adds the option to specify in thepreloaddirective which weights, styles, or subsets to preload for a given font family when using the experimental Fonts API:Variable weight font files will be preloaded if any weight within its range is requested. For example, a font file for font weight
100 900will be included when400is specified in apreloadobject.v5.14.8Compare Source
Patch Changes
577d051Thanks @matthewp! - Fixes image path resolution in content layer collections to support bare filenames. Theimage()helper now normalizes bare filenames like"cover.jpg"to relative paths"./cover.jpg"for consistent resolution behavior between markdown frontmatter and JSON content collections.v5.14.7Compare Source
Patch Changes
#14582
7958c6bThanks @florian-lefebvre! - Fixes a regression that caused Actions to throw errors while loading#14567
94500bbThanks @matthewp! - Fixes the actions endpoint to return 404 for nonexistent actions instead of throwing an unhandled error#14566
946fe68Thanks @matthewp! - Fixes handling malformed cookies gracefully by returning the unparsed value instead of throwingWhen a cookie with an invalid value is present (e.g., containing invalid URI sequences),
Astro.cookies.get()now returns the raw cookie value instead of throwing a URIError. This aligns with the behavior of the underlyingcookiepackage and prevents crashes when manually-set or corrupted cookies are encountered.#14142
73c5de9Thanks @P4tt4te! - Updates handling of CSS for hydrated client components to prevent duplicates#14576
2af62c6Thanks @aprici7y! - Fixes a regression that causedAstro.siteto always beundefinedingetStaticPaths()v5.14.6Compare Source
Patch Changes
#14562
722bba0Thanks @erbierc! - Fixes a bug where the behavior of the "muted" HTML attribute was inconsistent with that of other attributes.#14538
51ebe6aThanks @florian-lefebvre! - Improves how Actions are implemented#14548
6cdade4Thanks @ascorbic! - Removes support for themaxAgeproperty incacheHintobjects returned by live loaders.⚠️ Breaking change for experimental live content collections only
Feedback showed that this did not make sense to set at the loader level, since the loader does not know how long each individual entry should be cached for.
If your live loader returns cache hints with
maxAge, you need to remove this property:The
cacheHintobject now only supportstagsandlastModifiedproperties. If you want to set the max age for a page, you can set the headers manually:#14548
6cdade4Thanks @ascorbic! - Adds missingrenderedproperty to experimental live collections entry typeLive collections support a
renderedproperty that allows you to provide pre-rendered HTML for each entry. While this property was documented and implemented, it was missing from the TypeScript types. This could lead to type errors when trying to use it in a TypeScript project.No changes to your project code are necessary. You can continue to use the
renderedproperty as before, and it will no longer produce TypeScript errors.v5.14.5Compare Source
Patch Changes
#14525
4f55781Thanks @penx! - FixesdefineLiveCollection()types#14441
62ec8eaThanks @upsuper! - Updates redirect handling to be consistent acrossstaticandserveroutput, aligning with the behavior of other adapters.Previously, the Node.js adapter used default HTML files with meta refresh tags when in
staticoutput. This often resulted in an extra flash of the page on redirect, while also not applying the proper status code for redirections. It's also likely less friendly to search engines.This update ensures that configured redirects are always handled as HTTP redirects regardless of output mode, and the default HTML files for the redirects are no longer generated in
staticoutput. It makes the Node.js adapter more consistent with the other official adapters.No change to your project is required to take advantage of this new adapter functionality. It is not expected to cause any breaking changes. However, if you relied on the previous redirecting behavior, you may need to handle your redirects differently now. Otherwise, you should notice smoother redirects, with more accurate HTTP status codes, and may potentially see some SEO gains.
#14506
ec3cbe1Thanks @abdo-spices! - Updates the<Font />component so that preload links are generated after the style tag, as recommended by capo.jsv5.14.4Compare Source
Patch Changes
7e04cafThanks @ArmandPhilippot! - Fixes an error in the docs that specified an incorrect version for thesecurity.allowedDomainsrelease.v5.14.3Compare Source
Patch Changes
#14505
28b2a1dThanks @matthewp! - FixesCannot set property manifesterror in test utilities by adding a protected setter for the manifest property#14235
c4d84bbThanks @toxeeec! - Fixes a bug where the "tap" prefetch strategy worked only on the first clicked link with view transitions enabledv5.14.1Compare Source
Patch Changes
a3e16abThanks @florian-lefebvre! - Fixes a case where the URLs generated by the experimental Fonts API would be incorrect in devv5.14.0Compare Source
Minor Changes
#13520
a31edb8Thanks @openscript! - Adds a new propertyroutePatternavailable toGetStaticPathsOptionsThis provides the original, dynamic segment definition in a routing file path (e.g.
/[...locale]/[files]/[slug]) from the Astro render context that would not otherwise be available within the scope ofgetStaticPaths(). This can be useful to calculate theparamsandpropsfor each page route.For example, you can now localize your route segments and return an array of static paths by passing
routePatternto a customgetLocalizedData()helper function. Theparamsobject will be set with explicit values for each route segment (e.g.locale,files, andslug). Then, these values will be used to generate the routes and can be used in your page template viaAstro.params.For more information about this advanced routing pattern, see Astro's routing reference.
#13651
dcfbd8cThanks @ADTC! - Adds a newSvgComponenttypeYou can now more easily enforce type safety for your
.svgassets by directly importingSVGComponentfromastro/types:#14206
16a23e2Thanks @Fryuni! - Warn on prerendered routes collision.Previously, when two dynamic routes
/[foo]and/[bar]returned values on theirgetStaticPathsthat resulted in the same final path, only one of the routes would be rendered while the other would be silently ignored. Now, when this happens, a warning will be displayed explaining which routes collided and on which path.Additionally, a new experimental flag
failOnPrerenderConflictcan be used to fail the build when such a collision occurs.Patch Changes
#13811
69572c0Thanks @florian-lefebvre! - Adds a newgetFontData()method to retrieve lower-level font family data programmatically when using the experimental Fonts APIThe
getFontData()helper function fromastro:assetsprovides access to font family data for use outside of Astro. This can then be used in an API Route or to generate your own meta tags.For example,
getFontData()can get the font buffer from the URL when using satori to generate Open Graph images:See the experimental Fonts API documentation for more information.
v5.13.11Compare Source
Patch Changes
#14409
250a595Thanks @louisescher! - Fixes an issue whereastro infowould log errors to console in certain cases.#14398
a7df80dThanks @idawnlight! - Fixes an unsatisfiable type definition when callingaddServerRendereron an experimental container instance#13747
120866fThanks @jp-knj! - Adds automatic request signal abortion when the underlying socket closes in the Node.js adapterThe Node.js adapter now automatically aborts the
request.signalwhen the client connection is terminated. This enables better resource management and allows applications to properly handle client disconnections through the standardAbortSignalAPI.#14428
32a8acbThanks @drfuzzyness! - Force sharpService to return a Uint8Array if Sharp returns a SharedArrayBuffer#14411
a601186Thanks @GameRoMan! - Fixes relative links to docs that could not be opened in the editor.v5.13.10Compare Source
Patch Changes
1e2499e]:v5.13.9Compare Source
Patch Changes
54dcd04Thanks @FredKSchott! - Removes warning that caused unexpected console spam when using Bunv5.13.8Compare Source
Patch Changes
#14300
bd4a70bThanks @louisescher! - Adds Vite version & integration versions to output ofastro info#14341
f75fd99Thanks @delucis! - Fixes support for declarative Shadow DOM when using the<ClientRouter>component#14350
f59581fThanks @ascorbic! - Improves error reporting for content collections by adding logging for configuration errors that had previously been silently ignored. Also adds a new error that is thrown if a live collection is used incontent.config.tsrather thanlive.config.ts.#14343
13f7d36Thanks @florian-lefebvre! - Fixes a regression in non node runtimesv5.13.7Compare Source
Patch Changes
#14330
72e14abThanks @ascorbic! - Removes pinned package that is no longer needed.#14335
17c7b03Thanks @florian-lefebvre! - Bumpssharpminimal version to0.34.0v5.13.6Compare Source
Patch Changes
#14294
e005855Thanks @martrapp! - Restores the ability to use Google AnalyticsHistory change triggerwith the<ClientRouter />.#14326
c24a8f4Thanks @jsparkdev! - Updatesviteversion to fix CVE#14108
218e070Thanks @JusticeMatthew! - Updates dynamic route split regex to avoid infinite retries/exponential complexity#14327
c1033beThanks @ascorbic! - Pins simple-swizzle to avoid compromised versionv5.13.5Compare Source
Patch Changes
#14286
09c5db3Thanks @ematipico! - BREAKING CHANGES only to the experimental CSP featureThe following runtime APIs of the
Astroglobal have been renamed:Astro.insertDirectivetoAstro.csp.insertDirectiveAstro.insertStyleResourcetoAstro.csp.insertStyleResourceAstro.insertStyleHashtoAstro.csp.insertStyleHashAstro.insertScriptResourcetoAstro.csp.insertScriptResourceAstro.insertScriptHashtoAstro.csp.insertScriptHashThe following runtime APIs of the
APIContexthave been renamed:ctx.insertDirectivetoctx.csp.insertDirectivectx.insertStyleResourcetoctx.csp.insertStyleResourcectx.insertStyleHashtoctx.csp.insertStyleHashctx.insertScriptResourcetoctx.csp.insertScriptResourcectx.insertScriptHashtoctx.csp.insertScriptHash#14283
3224637Thanks @ematipico! - Fixes an issue where CSP headers were incorrectly injected in the development server.#14275
3e2f20dThanks @florian-lefebvre! - Adds support for experimental CSP when using experimental fontsExperimental fonts now integrate well with experimental CSP by injecting hashes for the styles it generates, as well as
font-srcdirectives.No action is required to benefit from it.
#14280
4b9fb73Thanks @ascorbic! - Fixes a bug that caused cookies to not be correctly set when using middleware sequences#14276
77281c4Thanks @ArmandPhilippot! - Adds a missing export forresolveSrc, a documented image services utility.v5.13.4Compare Source
Patch Changes
#14260
86a1e40Thanks @jp-knj! - FixesAstro.url.pathnameto respecttrailingSlash: 'never'configuration when using a base path. Previously, the root path with a base would incorrectly return/base/instead of/basewhentrailingSlashwas set to 'never'.#14248
e81c4bdThanks @julesyoungberg! - Fixes a bug where actions named 'apply' do not work due to being a function prototype method.v5.13.3Compare Source
Patch Changes
#14239
d7d93e1Thanks @wtchnm! - Fixes a bug where the types for the live content collections were not being generated correctly in dev mode#14221
eadc9ddThanks @delucis! - Fixes JSON schema support for content collections using thefile()loader#14229
1a9107aThanks @jonmichaeldarby! - EnsuresAstro.currentLocalereturns the correct locale during SSG for pages that use a locale param (such as[locale].astroor[locale]/index.astro, which produce[locale].html)v5.13.2Compare Source
Patch Changes
4d16de7Thanks @ematipico! - Improves the detection of remote paths in the_imageendpoint. Nowhrefparameters that start with//are considered remote paths.Updated dependencies [
4d16de7]:v5.13.1Compare Source
Patch Changes
#14409
250a595Thanks @louisescher! - Fixes an issue whereastro infowould log errors to console in certain cases.#14398
a7df80dThanks @idawnlight! - Fixes an unsatisfiable type definition when callingaddServerRendereron an experimental container instance#13747
120866fThanks @jp-knj! - Adds automatic request signal abortion when the underlying socket closes in the Node.js adapterThe Node.js adapter now automatically aborts the
request.signalwhen the client connection is terminated. This enables better resource management and allows applications to properly handle client disconnections through the standardAbortSignalAPI.#14428
32a8acbThanks @drfuzzyness! - Force sharpService to return a Uint8Array if Sharp returns a SharedArrayBuffer#14411
a601186Thanks @GameRoMan! - Fixes relative links to docs that could not be opened in the editor.v5.13.0Compare Source
Minor Changes
#14173
39911b8Thanks @florian-lefebvre! - Adds an experimental flagstaticImportMetaEnvto disable the replacement ofimport.meta.envvalues withprocess.envcalls and their coercion of environment variable values. This supersedes therawEnvValuesexperimental flag, which is now removed.Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via
astro:envinto the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.However, you can still access environment variables through
process.envandimport.meta.envdirectly when needed. This was the only way to use environment variables in Astro beforeastro:envwas added in Astro 5.0, and Astro's default handling ofimport.meta.envincludes some logic that was only needed for earlier versions of Astro.The
experimental.staticImportMetaEnvflag updates the behavior ofimport.meta.envto align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.Currently, non-public
import.meta.envenvironment variables are replaced by a reference toprocess.env. Additionally, Astro may also convert the value type of your environment variables used throughimport.meta.env, which can prevent access to some values such as the strings"true"(which is converted to a boolean value), and"1"(which is converted to a number).The
experimental.staticImportMetaEnvflag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace anyimport.meta.envenvironment variables with aprocess.envcall, nor will it coerce values.To enable this feature, add the experimental flag in your Astro config and remove
rawEnvValuesif it was enabled:Updating your project
If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:
If you were relying on the transformation into
process.envcalls, you may need to update your project code to apply it manually:You may also need to update types:
See the experimental static
import.meta.envdocumentation for more information about this feature. You can learn more about using environment variables in Astro, includingastro:env, in the environment variables documentation.#14122
41ed3acThanks @ascorbic! - Adds experimental support for automatic Chrome DevTools workspace foldersThis feature allows you to edit files directly in the browser and have those changes reflected in your local file system via a connected workspace folder. This allows you to apply edits such as CSS tweaks without leaving your browser tab!
With this feature enabled, the Astro dev server will automatically configure a Chrome DevTools workspace for your project. Your project will then appear as a workspace source, ready to connect. Then, changes that you make in the "Sources" panel are automatically saved to your project source code.
To enable this feature, add the experimental flag
chromeDevtoolsWorkspaceto your Astro config:See the experimental Chrome DevTools workspace feature documentation for more information.
v5.12.9Compare Source
Patch Changes
#14020
9518975Thanks @jp-knj and @asieradzk! - Prevent double-prefixed redirect paths when using fallback and redirectToDefaultLocale togetherFixes an issue where i18n fallback routes would generate double-prefixed paths (e.g.,
/es/es/test/item1/) whenfallbackandredirectToDefaultLocaleconfigurations were used together. The fix adds proper checks to prevent double prefixing in route generation.#14199
3e4cb8eThanks @ascorbic! - Fixes a bug that prevented HMR from working with inline stylesv5.12.8Compare Source
Patch Changes
0567fb7Thanks @ascorbic! - Adds//to list of internal path prefixes that do not have automated trailing slash handling#13894
b36e72fThanks @florian-lefebvre! - Removes Astro Studio commands from the CLI helpUpdated dependencies [
0567fb7]:v5.12.7Compare Source
Patch Changes
#14169
f4e8889Thanks @ascorbic! - Skips trailing slash handling for paths that start with/..#14170
34e6b3aThanks @ematipico! - Fixes an issue where static redirects couldn't correctly generate a redirect when the destination is a prerendered route, and theoutputis set to"server".#14169
f4e8889Thanks @ascorbic! - Fixes a bug that prevented images from being displayed in dev when using the Netlify adapter withtrailingSlashset toalwaysUpdated dependencies [
f4e8889]:v5.12.6Compare Source
Patch Changes
#14153
29e9283Thanks @jp-knj! - Fixes a regression introduced by a recent optimisation of how SVG images are emitted during the build.#14156
592f08dThanks @TheOtterlord! - Fix the client router not submitting forms if the active URL contained a hash#14160
d2e25c6Thanks @ascorbic! - Fixes a bug that meant some remote image URLs could cause invalid filenames to be used for processed images#14167
62bd071Thanks @ascorbic! - Fixes a bug that prevented destroyed sessions from being deleted from storage unless the session had been loadedv5.12.5Compare Source
Patch Changes
#14059
19f53ebThanks @benosmac! - Fixes a bug in i18n implementation, where Astro didn't emit the correct pages whenfallbackis enabled, and a locale uses a catch-all route, e.g.src/pages/es/[...catchAll].astro#14155
31822c3Thanks @ascorbic! - Fixes a bug that caused an error "serverEntrypointModule[_start] is not a function" in some adaptersv5.12.4Compare Source
Patch Changes
#14031
e9206c1Thanks @jp-knj! - Optimized the build pipeline for SVG images. Now, Astro doesn't reprocess images that have already been processed.#14132
976879aThanks @ematipico! - Fixes a bug where the propertyAstro.routePattern/context.routePatternwasn't updated when using a rewrite via middleware.#14131
aafc4d7Thanks @florian-lefebvre! - Fixes a case where an error occurring in a middleware would show the dev overlay instead of the custom500.astropage#14127
2309adaThanks @florian-lefebvre! - Upgrades zod#14134
186c201Thanks @ascorbic! - Throws a more helpful error in dev if trying to use a server island without an adapter#14129
3572d85Thanks @ematipico! - Fixes a bug where the CSP headers was incorrectly added to a page when using an adapter.v5.12.3Compare Source
Patch Changes
#14119
14807a4Thanks @ascorbic! - Fixes a bug that caused builds to fail if a client directive was mistakenly added to an Astro component#14001
4b03d9cThanks @dnek! - Fixes an issue wheregetImage()assigned the resized base URL to the srcset URL ofImageTransform, which matched the width, height, and format of the original image.v5.12.2Compare Source
Patch Changes
#14071
d2cb35dThanks @Grisoly! - Exposes theCodecomponentlangprop type:#14111
5452ee6Thanks @ascorbic! - Fixes a bug that prevented "key" from being used as a prop for Astro components in MDX#14106
b5b39e4Thanks @ascorbic! - Exits with non-zero exit code when config has an error#14112
37458b3Thanks @ascorbic! - Fixes a bug that meant that SVG components could no longer be serialized withJSON.stringify#14061
c7a7dd5Thanks @jonasgeiler! - Add module declaration for?no-inlineasset imports#14109
5a08fa2Thanks @ascorbic! - Throw a more helpful error if defineLiveCollection is used outside of a live.config file#14110
e7dd4e1Thanks @ascorbic! - Warn if duplicate IDs are found by file loaderv5.12.1Compare Source
Patch Changes
#14094
22e9087Thanks @ascorbic! - Correct types to allowpriorityon all images#14091
26c6b6dThanks @ascorbic! - Fixes a bug that caused a type error when defining session options without a driver#14082
93322cbThanks @louisescher! - Fixes an issue where Astro's default 404 route would incorrectly match routes containing "/404" in dev#14089
687d253Thanks @florian-lefebvre! - Fixes a case whereastro:envwould not load the right environments variables in dev#14092
6692c71Thanks @ascorbic! - Improves error handling in live collections#14074
144a950Thanks @abcfy2! - Fixes a bug that caused some image service builds to fail#14092
6692c71Thanks @ascorbic! - Fixes a case where zod could not be imported fromastro:contentvirtual module in live collection configv5.12.0Compare Source
Minor Changes
#13971
fe35ee2Thanks @adamhl8! - Adds an experimental flagrawEnvValuesto disable coercion ofimport.meta.envvalues (e.g. converting strings to other data types) that are populated fromprocess.envAstro allows you to configure a type-safe schema for your environment variables, and converts variables imported via
astro:envinto the expected type.However, Astro also converts your environment variables used through
import.meta.envin some cases, and this can prevent access to some values such as the strings"true"(which is converted to a boolean value), and"1"(which is converted to a number).The
experimental.rawEnvValuesflag disables coercion ofimport.meta.envvalues that are populated fromprocess.env, allowing you to use the raw value.To enable this feature, add the experimental flag in your Astro config:
If you were relying on this coercion, you may need to update your project code to apply it manually:
See the experimental raw environment variables reference docs for more information.
#13941
6bd5f75Thanks @aditsachde! - Adds support for TOML files to Astro's built-inglob()andfile()content loaders.In Astro 5.2, Astro added support for using TOML frontmatter in Markdown files instead of YAML. However, if you wanted to use TOML files as local content collection entries themselves, you needed to write your own loader.
Astro 5.12 now directly supports loading data from TOML files in content collections in both the
glob()and thefile()loaders.If you had added your own TOML content parser for the
file()loader, you can now remove it as this functionality is now included:Note that TOML does not support top-level arrays. Instead, the
file()loader considers each top-level table to be an independent entry. The table header is populated in theidfield of the entry object.See Astro's content collections guide for more information on using the built-in content loaders.
Patch Changes
6bd5f75]:v5.11.2Compare Source
Patch Changes
#14064
2eb77d8Thanks @jp-knj! - Allows usingtsconfigcompilerOptions.pathswithout settingcompilerOptions.baseUrl#14068
10189c0Thanks @jsparkdev! - Fixes the incorrect CSS import path shown in the terminal message during Tailwind integration setup.v5.11.1Compare Source
Patch Changes
#14045
3276b79Thanks @ghubo! - Fixes a problem where importing animated.aviffiles returns aNoImageMetadataerror.#14041
0c4d5f8Thanks @dixslyf! - Fixes a<ClientRouter />bug where the fallback view transition animations when exiting a pageran too early for browsers that do not support the View Transition API.
This bug prevented
event.viewTransition?.skipTransition()from skipping the page exit animationwhen used in an
astro:before-swapevent hook.v5.11.0Compare Source
Minor Changes
#13972
db8f8beThanks @ematipico! - Updates theNodeApp.match()function in the Adapter API to accept a second, optional parameter to allow adapter authors to add headers to static, prerendered pages.NodeApp.match(request)currently checks whether there is a route that matches the givenRequest. If there is a prerendered route, the function returnsundefined, because static routes are already rendered and their headers cannot be updated.When the new, optional boolean parameter is passed (e.g.
NodeApp.match(request, true)), Astro will return the first matched route, even when it's a prerendered route. This allows your adapter to now access static routes and provides the opportunity to set headers for these pages, for example, to implement a Content Security Policy (CSP).Patch Changes
#14029
42562f9Thanks @ematipico! - Fixes a bug where server islands wouldn't be correctly rendered when they are rendered inside fragments.Now the following examples work as expected:
#14017
8d238bcThanks @dmgawel! - Fixes a bug where i18n fallback rewrites didn't work in dynamic pages.v5.10.2Compare Source
Patch Changes
#14000
3cbedaeThanks @feelixe! - Fix routePattern JSDoc examples to show correct return values#13990
de6cfd6Thanks @isVivek99! - Fixes a case whereastro:config/clientandastro:config/servervirtual modules would not contain config passed to integrationsupdateConfig()during the build#14019
a160d1eThanks @ascorbic! - Removes the requirement to settype: 'live'when defining experimental live content collectionsPreviously, live collections required a
typeandloaderconfigured. Now, Astro can determine that your collection is alivecollection without defining it explicitly.This means it is now safe to remove
type: 'live'from your collections defined insrc/live.config.ts:This is not a breaking change: your existing live collections will continue to work even if you still include
type: 'live'. However, we suggest removing this line at your earliest convenience for future compatibility when the feature becomes stable and this config option may be removed entirely.#13966
598da21Thanks @msamoylov! - Fixes a broken link on the default 404 page in developmentv5.10.1Compare Source
Patch Changes
#13988
609044cThanks @ascorbic! - Fixes a bug in live collections that caused it to incorrectly complain about the collection being defined in the wrong file#13909
b258d86Thanks @isVivek99! - Fixes rendering of special boolean attributes for custom elements#13983
e718375Thanks @florian-lefebvre! - Fixes a case where the toolbar audit would incorrectly flag images processed by Astro in content collections documents#13999
f077b68Thanks @ascorbic! - AddslastModifiedfield to experimental live collection cache hintsLive loaders can now set a
lastModifiedfield in the cache hints for entries and collections to indicate when the data was last modified. This is then available in thecacheHintfield returned bygetCollectionandgetEntry.#13987
08f34b1Thanks @ematipico! - Adds an informative message in dev mode when the CSP feature is enabled.#14005
82aad62Thanks @ematipico! - Fixes a bug where inline styles and scripts didn't work when CSP was enabled. Now when adding<styles>elements inside an Astro component, their hashes care correctly computed.#13985
0b4c641Thanks @jsparkdev! - Updates wrong linkv5.10.0Compare Source
Minor Changes
#13917
e615216Thanks @ascorbic! - Adds a newpriorityattribute for Astro's image components.This change introduces a new
priorityoption for the<Image />and<Picture />components, which automatically sets theloading,decoding, andfetchpriorityattributes to their optimal values for above-the-fold images which should be loaded immediately.It is a boolean prop, and you can use the shorthand syntax by simply adding
priorityas 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 your images further.
By default, the Astro
<Image />component generates<img>tags that lazy-load their content by settingloading="lazy"anddecoding="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.The new
priorityattribute will override those defaults and automatically add the best settings for your high-priority assets.This option was previously available for experimental responsive images, but now it is a standard feature for all images.
Usage
#13917
e615216Thanks @ascorbic! - The responsive images feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.The new responsive images feature in Astro automatically generates optimized images for different screen sizes and resolutions, and applies the correct attributes to ensure that images are displayed correctly on all devices.
Enable the
image.responsiveStylesoption in your Astro config. Then, set alayoutattribute on any or component, or configure a defaultimage.layout, for instantly responsive images with automatically generatedsrcsetandsizesattributes based on the image's dimensions and the layout type.Displaying images correctly on the web can be challenging, and is one of the most common performance issues seen in sites. This new feature simplifies the most challenging part of the process: serving your site visitor an image optimized for their viewing experience, and for your website's performance.
For full details, see the updated Image guide.
Migration from Experimental Responsive Images
The
experimental.responsiveImagesflag has been removed, and all experimental image configuration options have been renamed to their final names.If you were using the experimental responsive images feature, you'll need to update your configuration:
Remove the experimental flag
Update image configuration options
During the experimental phase, default styles were applied automatically to responsive images. Now, you need to explicitly set the
responsiveStylesoption totrueif you want these styles applied.The experimental image configuration options have been renamed:
Before:
After:
Component usage remains the same
The
layout,fit, andpositionprops on<Image>and<Picture>components work exactly the same as before:If you weren't using the experimental responsive images feature, no changes are required.
Please see the Image guide for more information on using responsive images in Astro.
#13685
3c04c1fThanks @ascorbic! - Adds experimental support for live content collectionsLive content collections are a new type of content collection that fetch their data at runtime rather than build time. This allows you to access frequently-updated data from CMSs, APIs, databases, or other sources using a unified API, without needing to rebuild your site when the data changes.
Live collections vs build-time collections
In Astro 5.0, the content layer API added support for adding diverse content sources to content collections. You can create loaders that fetch data from any source at build time, and then access it inside a page via
getEntry()andgetCollection(). The data is cached between builds, giving fast access and updates.However there is no method for updating the data store between builds, meaning any updates to the data need a full site deploy, even if the pages are rendered on-demand. This means that content collections are not suitable for pages that update frequently. Instead, today these pages tend to access the APIs directly in the frontmatter. This works, but leads to a lot of boilerplate, and means users don't benefit from the simple, unified API that content loaders offer. In most cases users tend to individually create loader libraries that they share between pages.
Live content collections solve this problem by allowing you to create loaders that fetch data at runtime, rather than build time. This means that the data is always up-to-date, without needing to rebuild the site.
How to use
To enable live collections add the
experimental.liveContentCollectionsflag to yourastro.config.mjsfile:Then create a new
src/live.config.tsfile (alongside yoursrc/content.config.tsif you have one) to define your live collections with a live loader and optionally a schema using the newdefineLiveCollection()function from theastro:contentmodule.You can then use the dedicated
getLiveCollection()andgetLiveEntry()functions to access your live data:See the docs for the experimental live content collections feature for more details on how to use this feature, including how to create a live loader. Please give feedback on the RFC PR if you have any suggestions or issues.
Patch Changes
#13957
304df34Thanks @ematipico! - Fixes an issue wherereport-uriwasn't available inexperimental.csp.directives, causing a typing error and a runtime validation error.#13957
304df34Thanks @ematipico! - Fixes a type error for the CSP directivesupgrade-insecure-requests,sandbox, andtrusted-type.#13862
fe8f61aThanks @florian-lefebvre! - Fixes a case where the dev toolbar would crash if it could not retrieve some essential data#13976
0a31d99Thanks @florian-lefebvre! - Fixes a case where Astro Actions types would be broken when using atsconfig.jsonwith"moduleResolution": "nodenext"v5.9.4Compare Source
Patch Changes
#13951
7eb88f1Thanks @ascorbic! - Fixes an issue that caused errors when using an adapter-provided session driver with custom options#13953
448bddcThanks @zaitovalisher! - Fixes a bug where quotes were not added to the 'strict-dynamic' CSP directivev5.9.3Compare Source
Patch Changes
#13923
a9ac5edThanks @ematipico! - BREAKING CHANGE to the experimental Content Security Policy (CSP) onlyChanges the behavior of experimental Content Security Policy (CSP) to now serve hashes differently depending on whether or not a page is prerendered:
<meta>element for static pages.Responseheadercontent-security-policyfor 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
953a249Thanks @ematipico! - Adds a new Astro Adapter Feature calledexperimentalStaticHeadersto allow your adapter to receive theHeadersfor 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
experimentalRouteToHeaderswill contain a map ofMap<IntegrationResolvedRoute, Headers>where theHeaderstype contains the headers emitted by the rendered static route.To enable support for this experimental Astro Adapter Feature, add it to your
adapterFeaturesin your adapter config:See the Adapter API docs for more information about providing adapter features.
#13697
af83b85Thanks @benosmac! - Fixes issues with fallback route pattern matching wheni18n.routing.fallbackTypeisrewrite.generatePathwhen building fallback routes and checking for existing translated pagesNow for a route to be matched it needs to be inside a named
[locale]folder. This fixes an issue whereroute.pattern.test()incorrectly matched dynamic routes, causing the page to be skipped.findRouteToRewriteNow the requested pathname must exist in
route.distURLfor a dynamic route to match. This fixes an issue whereroute.pattern.test()incorrectly matched dynamic routes, causing the build to fail.#13924
1cd8c3bThanks @qw-in! - Fixes an edge case whereisPrerenderedwas incorrectly set tofalsefor static redirects.#13926
953a249Thanks @ematipico! - Fixes an issue where the experimental CSPmetaelement wasn't placed in the<head>element as early as possible, causing these policies to not apply to styles and scripts that came before themetaelement.v5.9.2Compare Source
Patch Changes
#13919
423fe60Thanks @ematipico! - Fixes a bug where Astro added quotes to the CSP resources.Only certain resources require quotes (e.g.
'self'but nothttps://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:#13914
76c5480Thanks @ematipico! - BREAKING CHANGE to the experimental Content Security Policy feature onlyRemoves 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.
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.
v5.9.1Compare Source
Patch Changes
#13899
7a1303dThanks @reknih! - Fix bug where error pages would return invalid bodies if the upstream response was compressed#13902
051bc30Thanks @arHSM! - Fixes a bug where vite virtual module ids were incorrectly added in the dev server#13905
81f71caThanks @jsparkdev! - Fixes wrong contents in CSP meta tag.#13907
8246bccThanks @martrapp! - Fixes a bug that caused view transition names to be lost.#13901
37fa0a2Thanks @ansg191! - fix fallback not being removed when server island is renderedv5.9.0Compare Source
Minor Changes
#13802
0eafe14Thanks @ematipico! - Adds experimental Content Security Policy (CSP) supportCSP is an important feature to provide fine-grained control over resources that can or cannot be downloaded and executed by a document. In particular, it can help protect against cross-site scripting (XSS) attacks.
Enabling this feature adds additional security to Astro's handling of processed and bundled scripts and styles by default, and allows you to further configure these, and additional, content types. This new experimental feature has been designed to work in every Astro rendering environment (static pages, dynamic pages and single page applications), while giving you maximum flexibility and with type-safety in mind.
It is compatible with most of Astro's features such as client islands, and server islands, although Astro's view transitions using the
<ClientRouter />are not yet fully supported. Inline scripts are not supported out of the box, but you can provide your own hashes for external and inline scripts.To enable this feature, add the experimental flag in your Astro config:
For more information on enabling and using this feature in your project, see the Experimental CSP docs.
For a complete overview, and to give feedback on this experimental API, see the Content Security Policy RFC.
#13850
1766d22Thanks @ascorbic! - Provides a Markdown renderer to content loadersWhen creating a content loader, you will now have access to a
renderMarkdownfunction that allows you to render Markdown content directly within your loaders. It uses the same settings and plugins as the renderer used for Markdown files in Astro, and follows any Markdown settings you have configured in your Astro project.This allows you to render Markdown content from various sources, such as a CMS or other data sources, directly in your loaders without needing to preprocess the Markdown content separately.
The return value of
renderMarkdownis an object with two properties:htmlandmetadata. These match therenderedproperty of content entries in content collections, so you can use them to render the content in your components or pages.For more information, see the Content Loader API docs.
#13887
62f0668Thanks @yanthomasdev! - Adds an option for integration authors to suppress adapter warning/errors insupportedAstroFeatures. This is useful when either a warning/error isn't applicable in a specific context or the default one might conflict and confuse users.To do so, you can add
suppress: "all"(to suppress both the default and custom message) orsuppress: "default"(to only suppress the default one):For more information, see the Adapter API reference docs.
v5.8.2Compare Source
Patch Changes
#13877
5a7797fThanks @yuhang-dong! - Fixes a bug that causedAstro.rewriteto fail when used insequenced middleware#13872
442b841Thanks @isVivek99! - Fixes rendering of thedownloadattribute when it has a boolean valuev5.8.1Compare Source
Patch Changes
#13037
de2fc9bThanks @nanarino! - Fixes rendering of thepopoverattribute when it has a boolean value#13851
45ae95aThanks @ascorbic! - Allows disabling default styles for responsive imagesThis change adds a new
image.experimentalDefaultStylesoption that allows you to disable the default styles applied to responsive images.When using experimental responsive images, Astro applies default styles to ensure the images resize correctly. In most cases this is what you want – and they are applied with low specificity so your own styles override them. However in some cases you may want to disable these default styles entirely. This is particularly useful when using Tailwind 4, because it uses CSS cascade layers to apply styles, making it difficult to override the default styles.
image.experimentalDefaultStylesis a boolean option that defaults totrue, so you can change it in your Astro config file like this:#13858
cb1a168Thanks @florian-lefebvre! - Fixes the warning shown when client directives are used on Astro components#12574
da266d0Thanks @apatel369! - Allows using server islands in mdx files#13843
fbcfa68Thanks @z1haze! - Export typeAstroSessionto allow use in explicitly typed safe code.v5.8.0Compare Source
Minor Changes
#13809
3c3b492Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.
⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.
Patch Changes
3c3b492]:v5.7.14Compare Source
Patch Changes
#13773
3aa5337Thanks @sijad! - Ignores lightningcss unsupported pseudo-class warning.#13833
5a6d2aeThanks @ascorbic! - Fixes an issue where session modules would fail to resolve in Node.js < 20.6#13383
f7f712cThanks @Haberkamp! - Stop toolbar settings from overflowing#13794
85b19d8Thanks @alexcarpenter! - Exclude pre tags froma11y-no-noninteractive-tabindexaudit check.#13373
50ef568Thanks @jpwienekus! - Fixes a bug where highlights and tooltips render over the audit list window.#13769
e9fc456Thanks @romanstetsyk! - Expand ActionError codes to include all IANA-registered HTTP error codes.#13668
866285aThanks @sapphi-red! - Replaces internal CSS chunking behavior for Astro components' scoped styles to use Vite'scssScopeTofeature. The feature is a port of Astro's implementation so this should not change the behavior.v5.7.13Compare Source
Patch Changes
#13761
a2e8463Thanks @jp-knj! - Adds new content collections errors#13788
7d0b7acThanks @florian-lefebvre! - Fixes a case where an error would not be thrown when using the<Font />component from the experimental fonts API without adding fonts in the Astro config#13784
d7a1889Thanks @florian-lefebvre! - Fixes the experimental fonts API to correctly takeconfig.base,config.build.assetsandconfig.build.assetsPrefixinto account#13777
a56b8eaThanks @L4Ph! - Fixed an issue where looping GIF animation would stop when converted to WebP#13566
0489d8fThanks @TheOtterlord! - Fix build errors being ignored when build.concurrency > 1v5.7.12Compare Source
Patch Changes
#13752
a079c21Thanks @florian-lefebvre! - Improves handling of font URLs not ending with a file extension when using the experimental fonts API#13750
7d3127dThanks @martrapp! - Allows the ClientRouter to open new tabs or windows when submitting forms by clicking while holding the Cmd, Ctrl, or Shift key.#13765
d874fe0Thanks @florian-lefebvre! - Fixes a case where font sources with relative protocol URLs would fail when using the experimental fonts API#13640
5e582e7Thanks @florian-lefebvre! - Allows inferringweightandstylewhen using the local provider of the experimental fonts APIIf you want Astro to infer those properties directly from your local font files, leave them undefined:
v5.7.11Compare Source
Patch Changes
#13734
30aec73Thanks @ascorbic! - Loosen content layer schema types#13751
5816b8aThanks @florian-lefebvre! - Updatesunifontto support subsets when using thegoogleprovider with the experimental fonts API#13756
d4547baThanks @florian-lefebvre! - Adds a terminal warning when a remote provider returns no data for a family when using the experimental fonts API#13742
f599463Thanks @florian-lefebvre! - Fixes optimized fallback css generation to properly add asrcwhen using the experimental fonts API#13740
6935540Thanks @vixalien! - Fix cookies set after middleware did a rewrite withnext(url)not being applied#13759
4a56d0aThanks @jp-knj! - Improved the error handling of certain error cases.v5.7.10Compare Source
Patch Changes
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVEv5.7.9Compare Source
Patch Changes
2103991Thanks @ascorbic! - Fixes height for responsive imagesv5.7.8Compare Source
Patch Changes
b32dffaThanks @florian-lefebvre! - Updatesunifontto fix a case where aunicodeRangerelated error would be thrown when using the experimental fonts APIv5.7.7Compare Source
Patch Changes
#13705
28f8716Thanks @florian-lefebvre! - Updates unifont to latest and adds support forfetchoptions from remote providers when using the experimental fonts API#13692
60d5be4Thanks @Le0Developer! - Fixes a bug where Astro couldn't probably useinferSizefor images that contain apostrophe'in their name.#13698
ab98f88Thanks @sarah11918! - Improves the configuration reference docs for theadapterentry with more relevant text and links.#13706
b4929aeThanks @ascorbic! - Fixes typechecking for content config schema#13653
a7b2dc6Thanks @florian-lefebvre! - Reduces the amount of preloaded files for the local provider when using the experimental fonts API#13653
a7b2dc6Thanks @florian-lefebvre! - Fixes a case where invalid CSS was emitted when using an experimental fonts API family name containing a spacev5.7.6Compare Source
Patch Changes
#13703
659904bThanks @ascorbic! - Fixes a bug where empty fallbacks could not be provided when using the experimental fonts API#13680
18e1b97Thanks @florian-lefebvre! - Improves theUnsupportedExternalRedirecterror message to include more details such as the concerned destination#13703
659904bThanks @ascorbic! - Simplifies styles for experimental responsive images⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️
The generated styles for image layouts are now simpler and easier to override. Previously the responsive image component used CSS to set the size and aspect ratio of the images, but this is no longer needed. Now the styles just include
object-fitandobject-positionfor all images, and setsmax-width: 100%for constrained images andwidth: 100%for full-width images.This is an implementation change only, and most users will see no change. However, it may affect any custom styles you have added to your responsive images. Please check your rendered images to determine whether any change to your CSS is needed.
The styles now use the
:where()pseudo-class, which has a specificity of 0, meaning that it is easy to override with your own styles. You can now be sure that your own classes will always override the applied styles, as will global styles onimg.An exception is Tailwind 4, which uses cascade layers, meaning the rules are always lower specificity. Astro supports browsers that do not support cascade layers, so we cannot use this. If you need to override the styles using Tailwind 4, you must use
!importantclasses. Do check if this is needed though: there may be a layout that is more appropriate for your use case.#13703
659904bThanks @ascorbic! - Adds warnings about using local font files in thepublicDirwhen the experimental fonts API is enabled.#13703
659904bThanks @ascorbic! - Renames experimental responsive image layout option from "responsive" to "constrained"⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️
The layout option called
"responsive"is renamed to"constrained"to better reflect its behavior.The previous name was causing confusion, because it is also the name of the feature. The
responsivelayout option is specifically for images that are displayed at the requested size, unless they do not fit the width of their container, at which point they would be scaled down to fit. They do not get scaled beyond the intrinsic size of the source image, or thewidthprop if provided.It became clear from user feedback that many people (understandably) thought that they needed to set
layouttoresponsiveif they wanted to use responsive images. They then struggled with overriding styles to make the image scale up for full-width hero images, for example, when they should have been usingfull-widthlayout. Renaming the layout toconstrainedshould make it clearer that this layout is for when you want to constrain the maximum size of the image, but allow it to scale-down.Upgrading
If you set a default
image.experimentalLayoutin yourastro.config.mjs, or set it on a per-image basis using thelayoutprop, you will need to change all occurrences toconstrained:Please give feedback on the RFC if you have any questions or comments about the responsive images API.
v5.7.5Compare Source
Patch Changes
#13660
620d15dThanks @mingjunlu! - Addsserver.allowedHostsdocs comment toAstroUserConfig#13591
5dd2d3fThanks @florian-lefebvre! - Removes unused code#13669
73f24d4Thanks @ematipico! - Fixes an issue whereAstro.originPathnamewasn't returning the correct value when using rewrites.#13674
42388b2Thanks @florian-lefebvre! - Fixes a case where an experimental fonts API error would be thrown when using anotherastro:assetsAPI#13654
4931457Thanks @florian-lefebvre! - FixesfontProviders.google()so it can forward options to the unifont provider, when using the experimental fonts APIUpdated dependencies [
5dd2d3f]:v5.7.4Compare Source
Patch Changes
#13647
ffbe8f2Thanks @ascorbic! - Fixes a bug that caused a session error to be logged when using actions without sessions#13646
6744842Thanks @florian-lefebvre! - Fixes a case where extra font sources were removed when using the experimental fonts API#13635
d75cac4Thanks @florian-lefebvre! - The experimental fonts API now generates optimized fallbacks for every weight and stylev5.7.3Compare Source
Patch Changes
#13643
67b7493Thanks @tanishqmanuja! - Fixes a case where the font facesrcformat would be invalid when using the experimental fonts API#13639
23410c6Thanks @florian-lefebvre! - Fixes a case where some font families would not be downloaded when using the same font provider several times, using the experimental fonts APIv5.7.2Compare Source
Patch Changes
#13632
cb05cfbThanks @florian-lefebvre! - Improves the optimized fallback name generated by the experimental Fonts API#13630
3e7db4fThanks @florian-lefebvre! - Fixes a case where fonts using a local provider would not work because of an invalid generatedsrc#13634
516de7dThanks @ematipico! - Fixes a regression where usingnext('/')didn't correctly return the requested route.#13632
cb05cfbThanks @florian-lefebvre! - Improves the quality of optimized fallbacks generated by the experimental Fonts API#13616
d475afcThanks @lfilho! - Fixes a regression where relative static redirects didn't work as expected.v5.7.1Compare Source
Patch Changes
#13773
3aa5337Thanks @sijad! - Ignores lightningcss unsupported pseudo-class warning.#13833
5a6d2aeThanks @ascorbic! - Fixes an issue where session modules would fail to resolve in Node.js < 20.6#13383
f7f712cThanks @Haberkamp! - Stop toolbar settings from overflowing#13794
85b19d8Thanks @alexcarpenter! - Exclude pre tags froma11y-no-noninteractive-tabindexaudit check.#13373
50ef568Thanks @jpwienekus! - Fixes a bug where highlights and tooltips render over the audit list window.#13769
e9fc456Thanks @romanstetsyk! - Expand ActionError codes to include all IANA-registered HTTP error codes.#13668
866285aThanks @sapphi-red! - Replaces internal CSS chunking behavior for Astro components' scoped styles to use Vite'scssScopeTofeature. The feature is a port of Astro's implementation so this should not change the behavior.v5.7.0Compare Source
Minor Changes
#13527
2fd6a6bThanks @ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:
Configuring session storage
Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.
If you are using an adapter that doesn't have a default driver, or if you want to choose a different driver, you can configure it using the
sessionconfiguration option:Using sessions
Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.
In pages and components, you can access the session using
Astro.session:In endpoints, actions, and middleware, you can access the session using
context.session:If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be
undefinedand an error will be logged in the console:Upgrading from Experimental to Stable
If you were previously using the experimental API, please remove the
experimental.sessionflag from your configuration:See the sessions guide for more information.
#12775
b1fe521Thanks @florian-lefebvre! - Adds a new, experimental Fonts API to provide first-party support for fonts in Astro.This experimental feature allows you to use fonts from both your file system and several built-in supported providers (e.g. Google, Fontsource, Bunny) through a unified API. Keep your site performant thanks to sensible defaults and automatic optimizations including fallback font generation.
To enable this feature, configure an
experimental.fontsobject with one or more fonts:Then, add a
<Font />component and site-wide styling in your<head>:Visit the experimental Fonts documentation for the full API, how to get started, and even how to build your own custom
AstroFontProviderif we don't yet support your preferred font service.For a complete overview, and to give feedback on this experimental API, see the Fonts RFC and help shape its future.
#13560
df3fd54Thanks @ematipico! - The virtual moduleastro:configintroduced behind a flag in v5.2.0 is no longer experimental and is available for general use.This virtual module exposes two sub-paths for type-safe, 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 and directory paths.Access these in any file inside your project to import and use select values from your Astro config:
If you were previously using this feature, please remove the experimental flag from your Astro config:
If you have been waiting for feature stabilization before using configuration imports, you can now do so.
Please see the
astro:configreference for more about this feature.#13578
406501aThanks @stramel! - The SVG import feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.This feature allows you to import SVG files directly into your Astro project as components and inline them into your HTML.
To use this feature, import an SVG file in your Astro project, passing any common SVG attributes to the imported component.
If you have been waiting for stabilization before using the SVG Components feature, you can now do so.
If you were previously using this feature, please remove the experimental flag from your Astro config:
Additionally, a few features that were available during the experimental stage were removed in a previous release. Please see the v5.6.0 changelog for details if you have not yet already updated your project code for the experimental feature accordingly.
Please see the SVG Components guide in docs for more about this feature.
Patch Changes
#13602
3213450Thanks @natemoo-re! - Updates the Audit dev toolbar app to automatically stripdata-astro-source-fileanddata-astro-source-locattributes in dev mode.#13598
f5de51eThanks @dreyfus92! - Fix routing with base paths when trailingSlash is set to 'never'. This ensures requests to '/base' are correctly matched when the base path is set to '/base', without requiring a trailing slash.#13603
d038030Thanks @sarah11918! - Adds the minimal starter template to the list ofcreate astrooptionsGood news if you're taking the introductory tutorial in docs, making a minimal reproduction, or just want to start a project with as little to rip out as possible. Astro's
minimal(empty) template is now back as one of the options when runningcreate astro@latestand starting a new project!v5.6.2Compare Source
Patch Changes
#13606
793ecd9Thanks @natemoo-re! - Fixes a regression that allowed prerendered code to leak into the server bundle.#13576
1c60ec3Thanks @ascorbic! - Reduces duplicate code in server islands scripts by extracting shared logic into a helper function.#13588
57e59beThanks @natemoo-re! - Fixes a memory leak when using SVG assets.#13589
5a0563dThanks @ematipico! - Deprecates the asset utility functionemitESMImage()and adds a newemitImageMetadata()to be used insteadThe function
emitESMImage()is now deprecated. It will continue to function, but it is no longer recommended nor supported. This function will be completely removed in a next major release of Astro.Please replace it with the new function
emitImageMetadata()as soon as you are able to do so:The new function returns the same signature as the previous one. However, the new function removes two deprecated arguments that were not meant to be exposed for public use:
_watchModeandexperimentalSvgEnabled. Since it was possible to access these with the old function, you may need to verify that your code still works as intended withemitImageMetadata().#13596
3752519Thanks @jsparkdev! - update vite to latest version to fix CVE#13547
360cb91Thanks @jsparkdev! - Updates vite to the latest version#13548
e588527Thanks @ryuapp! - Support for Deno to install npm packages.Deno requires npm prefix to install packages on npm. For example, to install react, we need to run
deno add npm:react. But currently the command executed isdeno add react, which doesn't work. So, we change the package names to have an npm prefix if you are using Deno.#13587
a0774b3Thanks @robertoms99! - Fixes an issue with the client router where some attributes of the root element were not updated during swap, including the transition scope.v5.6.1Compare Source
Patch Changes
#13519
3323f5cThanks @florian-lefebvre! - Refactors some internals to improve Rolldown compatibility#13545
a7aff41Thanks @stramel! - Prevent empty attributes from appearing in the SVG output#13552
9cd0fd4Thanks @ematipico! - Fixes an issue where Astro validated the i18n configuration incorrectly, causing false positives in downstream libraries.v5.6.0Compare Source
Minor Changes
#13403
dcb9526Thanks @yurynix! - Adds a new optionalprerenderedErrorPageFetchoption in the Adapter API to allow adapters to provide custom implementations for fetching prerendered error pages.Now, adapters can override the default
fetch()behavior, for example whenfetch()is unavailable or when you cannot call the server from itself.The following example provides a custom fetch for
500.htmland404.html, reading them from disk instead of performing an HTTP call:If no value is provided, Astro will fall back to its default behavior for fetching error pages.
Read more about this feature in the Adapter API reference.
#13482
ff257dfThanks @florian-lefebvre! - Updates Astro config validation to also run for the Integration API. An error log will specify which integration is failing the validation.Now, Astro will first validate the user configuration, then validate the updated configuration after each integration
astro:config:setuphook has run. This meansupdateConfig()calls will no longer accept invalid configuration.This fixes a situation where integrations could potentially update a project with a malformed configuration. These issues should now be caught and logged so that you can update your integration to only set valid configurations.
#13405
21e7e80Thanks @Marocco2! - Adds a neweagernessoption forprefetch()when usingexperimental.clientPrerenderWith the experimental
clientPrerenderflag enabled, you can use theeagernessoption onprefetch()to suggest to the browser how eagerly it should prefetch/prerender link targets.This follows the same API described in the Speculation Rules API and allows you to balance the benefit of reduced wait times against bandwidth, memory, and CPU costs for your site visitors.
For example, you can now use
prefetch()programmatically with large sets of links and avoid browser limits in place to guard against over-speculating (prerendering/prefetching too many links). Seteagerness: 'moderate'to take advantage of First In, First Out (FIFO) strategies and browser heuristics to let the browser decide when to prerender/prefetch them and in what order:#13482
ff257dfThanks @florian-lefebvre! - Improves integrations error handlingIf an error is thrown from an integration hook, an error log will now provide information about the concerned integration and hook
Patch Changes
#13539
c43bf8cThanks @ascorbic! - Adds a newsession.load()method to the experimental session API that allows you to load a session by ID.When using the experimental sessions API, you don't normally need to worry about managing the session ID and cookies: Astro automatically reads the user's cookies and loads the correct session when needed. However, sometimes you need more control over which session to load.
The new
load()method allows you to manually load a session by ID. This is useful if you are handling the session ID yourself, or if you want to keep track of a session without using cookies. For example, you might want to restore a session from a logged-in user on another device, or work with an API endpoint that doesn't use cookies.If a session with that ID doesn't exist, a new one will be created. This allows you to generate a session ID in the client if needed.
For more information, see the experimental sessions docs.
#13488
d777420Thanks @stramel! - BREAKING CHANGE to the experimental SVG Component API onlyRemoves some previously available prop, attribute, and configuration options from the experimental SVG API. These items are no longer available and must be removed from your code:
The
titleprop has been removed until we can settle on the correct balance between developer experience and accessibility. Please replace anytitleprops on your components witharia-label:Sprite mode has been temporarily removed while we consider a new implementation that addresses how this feature was being used in practice. This means that there are no longer multiple
modeoptions, and all SVGs will be inline. All instances ofmodemust be removed from your project as you can no longer control a mode:The default
roleis no longer applied due to developer feedback. Please add the appropriateroleon each component individually as needed:The
sizeprop has been removed to better work in combination withviewBoxand additional styles/attributes. Please replacesizewith explicitwidthandheightattributes:v5.5.6Compare Source
Patch Changes
#13429
06de673Thanks @ematipico! - TheActionAPIContext.rewritemethod is deprecated and will be removed in a future major version of Astro#13524
82cd583Thanks @ematipico! - Fixes a bug where the functionsAstro.preferredLocaleandAstro.preferredLocaleListwould return the incorrect localeswhen the Astro configuration specifies a list of
codes. Before, the functions would return thepath, instead now the functionsreturn a list built from
codes.#13526
ff9d69eThanks @jsparkdev! - updateviteto the latest versionv5.5.5Compare Source
Patch Changes
#13510
5b14d33Thanks @florian-lefebvre! - Fixes a case whereastro:envsecrets used in actions would not be available#13485
018fbe9Thanks @ascorbic! - Fixes a bug that caused cookies to ignore custom decode function if has() had been called before#13505
a98ae5bThanks @ematipico! - Updates the dependencyviteto the latest.#13483
fc2dcb8Thanks @ematipico! - Fixes a bug where an Astro adapter couldn't call the middleware when there isn't a route that matches the incoming request.v5.5.4Compare Source
Patch Changes
#13457
968e713Thanks @ascorbic! - Sets correct response status text for custom error pages#13447
d80ba2bThanks @ematipico! - Fixes an issue wheresitewas added to the generated redirects.#13481
e9e9245Thanks @martrapp! - Makes server island work with the client router again.#13484
8b5e4dcThanks @ascorbic! - Display useful errors when config loading fails because of Node addons being disabled on Stackblitzv5.5.3Compare Source
Patch Changes
#13437
013fa87Thanks @Vardhaman619! - Handle server.allowedHosts when the value is true without attempting to push it into an array.#13324
ea74336Thanks @ematipico! - Upgrade to shiki v3#13372
7783dbfThanks @ascorbic! - Fixes a bug that caused some very large data stores to save incomplete data.#13358
8c21663Thanks @ematipico! - Adds a new function calledinsertPageRouteto the Astro Container API.The new function is useful when testing routes that, for some business logic, use
Astro.rewrite.For example, if you have a route
/blog/postand for some business decision there's a rewrite to/generic-error, the container API implementation will look like this:This new method only works for page routes, which means that endpoints aren't supported.
#13426
565583bThanks @ascorbic! - Fixes a bug that caused theastro addcommand to ignore the--yesflag for third-party integrations#13428
9cac9f3Thanks @matthewp! - Prevent bad value in x-forwarded-host from crashing request#13432
defad33Thanks @P4tt4te! - Fix an issue in the Container API, where therenderToStringfunction doesn't render adequately nested slots when they are components.Updated dependencies [
ea74336]:v5.5.2Compare Source
Patch Changes
#13415
be866a1Thanks @ascorbic! - Reuses experimental session storage object between requests. This prevents memory leaks and improves performance for drivers that open persistent connections to a database.#13420
2f039b9Thanks @ematipico! - It fixes an issue that caused some regressions in how styles are bundled.v5.5.1Compare Source
Patch Changes
65903c9Thanks @ascorbic! - Makes experimental flag optionalv5.5.0Compare Source
Minor Changes
#13402
3e7b498Thanks @ematipico! - Adds a new experimental flag calledexperimental.preserveScriptOrderthat renders<script>and<style>tags in the same order as they are defined.When rendering multiple
<style>and<script>tags on the same page, Astro currently reverses their order in your generated HTML output. This can give unexpected results, for example CSS styles being overridden by earlier defined style tags when your site is built.With the new
preserveScriptOrderflag enabled, Astro will generate the styles in the order they are defined:For example, the following component has two
<style>tags, and both define the same style for thebodytag:Once the project is compiled, Astro will create an inline style where
yellowappears first, and thenred. Ultimately, theredbackground is applied:When
experimental.preserveScriptOrderis set totrue, the order of the two styles is kept as it is, and in the style generatedredappears first, and thenyellow:This is a breaking change to how Astro renders project code that contains multiple
<style>and<script>tags in the same component. If you were previously compensating for Astro's behavior by writing these out of order, you will need to update your code.This will eventually become the new default Astro behavior, so we encourage you to add this experimental style and script ordering as soon as you are able! This will help us test the new behavior and ensure your code is ready when this becomes the new normal.
For more information as this feature develops, please see the experimental script order docs.
#13352
cb886dcThanks @delucis! - Adds support for a newexperimental.headingIdCompatflagBy default, Astro removes a trailing
-from the end of IDs it generates for headings ending withspecial characters. This differs from the behavior of common Markdown processors.
You can now disable this behavior with a new configuration flag:
This can be useful when heading IDs and anchor links need to behave consistently across your site
and other platforms such as GitHub and npm.
If you are using the
rehypeHeadingIdsplugin directly, you can also pass this new option:#13311
a3327ffThanks @chrisirhc! - Adds a new configuration option for Markdown syntax highlightingexcludeLangsThis option provides better support for diagramming tools that rely on Markdown code blocks, such as Mermaid.js and D2 by allowing you to exclude specific languages from Astro's default syntax highlighting.
This option allows you to avoid rendering conflicts with tools that depend on the code not being highlighted without forcing you to disable syntax highlighting for other code blocks.
The following example configuration will exclude highlighting for
mermaidandmathcode blocks:Read more about this new option in the Markdown syntax highlighting configuration docs.
Patch Changes
#13404
4e78b4dThanks @ascorbic! - Fixes a bug in error handling that saving a content file with a schema error would display an "unhandled rejection" error instead of the correct schema error#13379
d59eb22Thanks @martrapp! - Fixes an edge case where the client router executed scripts twice when used with a custom swap function that only swaps parts of the DOM.#13393
6b8fdb8Thanks @renovate! - Updatesprimsjsto version 1.30.0, which adds support for more languages and fixes a security advisory which does not affect Astro.#13374
7b75bc5Thanks @ArmandPhilippot! - Fixes the documentation of the i18n configuration wheremanualwas presented as a key ofroutinginstead of an available value.#13380
9bfa6e6Thanks @martrapp! - Fixes an issue where astro:page-load fires before all scripts are executed#13407
0efdc22Thanks @ascorbic! - Displays correct error message when sharp isn't installedUpdated dependencies [
cb886dc,a3327ff]:v5.4.3Compare Source
Patch Changes
#13381
249d52aThanks @martrapp! - Adds thetypesproperty to the viewTransition object when the ClientRouter simulates parts of the View Transition API on browsers w/o native support.#13367
3ce4ad9Thanks @ematipico! - Adds documentation to various utility functions used for remote image services#13347
d83f92aThanks @bluwy! - Updates internal CSS chunking behavior for Astro components' scoped styles. This may result in slightly more CSS chunks created, but should allow the scoped styles to only be included on pages that use them.#13388
afadc70Thanks @ematipico! - Fixes a bug whereastro:config/serverandastro:config/clienthad incorrect types.#13355
042d1deThanks @ematipico! - Adds documentation to the assets utilities for remote service images.#13395
6d1c63fThanks @bluwy! - Usespackage-manager-detectorto detect the package manager used in the project#13363
a793636Thanks @ematipico! - Fixes an issue where the internal functionmakeSvgComponentwas incorrectly exposed as a public API.Updated dependencies [
042d1de]:v5.4.2Compare Source
Patch Changes
#12985
84e94ccThanks @matthewp! - Prevent re-executing scripts in client router#13349
50e2e0bThanks @ascorbic! - Correctly escapes attributes in Markdown images#13262
0025df3Thanks @ematipico! - Refactor Astro Actions to not use a middleware. Doing so should avoid unexpected issues when using the Astro middleware at the edge.v5.4.1Compare Source
Patch Changes
#13336
8f632efThanks @ematipico! - Fixes a regression where some asset utilities were move across monorepo, and not re-exported anymore.#13320
b5dabe9Thanks @{! - Adds support for typing experimental session dataYou can add optional types to your session data by creating a
src/env.d.tsfile in your project that extends the globalApp.SessionDatainterface. For example:Any keys not defined in this interface will be treated as
any.Then when you access
Astro.sessionin your components, any defined keys will be typed correctly:See the experimental session docs for more information.
#13330
5e7646eThanks @ematipico! - Fixes an issue with the conditional rendering of scripts.This change updates a v5.0 breaking change when
experimental.directRenderScriptbecame the default script handling behavior.If you have already successfully upgraded to Astro v5, you may need to review your script tags again and make sure they still behave as desired after this release. See the v5 Upgrade Guide for more details.
v5.4.0Compare Source
Minor Changes
5be12b2Thanks @Fryuni! - Exposes extra APIs for scripting and testing.Config helpers
Two new helper functions exported from
astro/config:mergeConfig()allows users to merge partially defined Astro configurations on top of a base config while following the merge rules ofupdateConfig()available for integrations.validateConfig()allows users to validate that a given value is a valid Astro configuration and fills in default values as necessary.These helpers are particularly useful for integration authors and for developers writing scripts that need to manipulate Astro configurations programmatically.
Programmatic build
The
buildAPI now receives a second optionalBuildOptionsargument where users can specify:devOutput(defaultfalse): output a development-based build similar to code transformed inastro dev.teardownCompiler(defaulttrue): teardown the compiler WASM instance after build.These options provide more control when running Astro builds programmatically, especially for testing scenarios or custom build pipelines.
#13278
4a43c4bThanks @ematipico! - Adds a new configuration optionserver.allowedHostsand CLI option--allowed-hosts.Now you can specify the hostnames that the dev and preview servers are allowed to respond to. This is useful for allowing additional subdomains, or running the dev server in a web container.
allowedHostschecks the Host header on HTTP requests from browsers and if it doesn't match, it will reject the request to prevent CSRF and XSS attacks.This feature is the same as Vite's
server.allowHostsconfiguration.#13254
1e11f5eThanks @p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown filesPreviously, Astro only allowed local images to be optimized when included using
![]()syntax in plain Markdown files. Astro's image service could only display remote images without any processing.Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.
No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the HTML
<img>tag instead. Note that images located in yourpublic/folder are still never processed.Patch Changes
#13256
509fa67Thanks @p0lyw0lf! - Adds experimental responsive image support in MarkdownPreviously, the
experimental.responsiveImagesfeature could only provide responsive images when using the<Image />and<Picture />components.Now, images written with the
![]()Markdown syntax in Markdown and MDX files will generate responsive images by default when using this experimental feature.To try this experimental feature, set
experimental.responsiveImagesto true in yourastro.config.mjsfile:Learn more about using this feature in the experimental responsive images feature reference.
For a complete overview, and to give feedback on this experimental API, see the Responsive Images RFC.
#13323
80926faThanks @ematipico! - Updatesesbuildandviteto the latest to avoid false positives audits warnings caused byesbuild.#13313
9e7c71dThanks @martrapp! - Fixes an issue where a form field named "attributes" shadows the form.attributes property.#12052
5be12b2Thanks @Fryuni! - Fixes incorrect config update when callingupdateConfigfromastro:build:setuphook.The function previously called a custom update config function made for merging an Astro config. Now it calls the appropriate
mergeConfig()utility exported by Vite that updates functional options correctly.#13303
5f72a58Thanks @ematipico! - Fixes an issue where the dev server was applying second decoding of the URL of the incoming request, causing issues for certain URLs.Updated dependencies [
1e11f5e,1e11f5e]:v5.3.1Compare Source
Patch Changes
#13233
32fafebThanks @joshmkennedy! - Ensures consistent behaviour ofAstro.rewrite/ctx.rewritewhen usingbaseandtrailingSlashoptions.#13003
ea79054Thanks @chaegumi! - Fixes a bug that caused thevite.basevalue to be ignored when runningastro dev#13299
2e1321eThanks @bluwy! - Usestinyglobbyfor globbing files#13233
32fafebThanks @joshmkennedy! - Ensures thatAstro.url/ctx.urlis correctly updated with thebasepath after rewrites.This change fixes an issue where
Astro.url/ctx.urldid not include the configured base path after Astro.rewrite was called. Now, the base path is correctly reflected in Astro.url.Previously, any rewrites performed through
Astro.rewrite/ctx.rewritefailed to append the base path toAstro.url/ctx.rewrite, which could lead to incorrect URL handling in downstream logic. By fixing this, we ensure that all routes remain consistent and predictable after a rewrite.If you were relying on the workaround of including the base path in astro.rewrite you can now remove it from the path.
v5.3.0Compare Source
Minor Changes
#13210
344e9bcThanks @VitaliyR! - HandleHEADrequests to an endpoint when a handler is not defined.If an endpoint defines a handler for
GET, but does not define a handler forHEAD, Astro will call theGEThandler and return the headers and status but an empty body.#13195
3b66955Thanks @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
8d4e566Thanks @ascorbic! - Adds support for adapters auto-configuring experimental session storage drivers.Adapters can now configure a default session storage driver when the
experimental.sessionflag 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
8d4e566Thanks @ascorbic! - ⚠️ BREAKING CHANGE FOR EXPERIMENTAL SESSIONS ONLY ⚠️Changes the
experimental.sessionoption 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 theexperimental.sessionflag, and then configure the session driver using the top-levelsessionkey if providing manual configuration.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.
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
sessionconfig option. For more information, see the experimental session docs.#13101
2ed67d5Thanks @corneliusroemer! - Fixes a bug whereHEADandOPTIONSrequests for non-prerendered pages were incorrectly rejected with 403 FORBIDDENv5.2.6Compare Source
Patch Changes
#13188
7bc8256Thanks @ematipico! - Fixes the wording of an error message#13205
9d56602Thanks @ematipico! - Fixes and issue where a server island component returns 404 whenbaseis configured in i18n project.#13212
fb38840Thanks @joshmkennedy! - An additional has been added during the build command to add clarity around output and buildOutput.#13213
6bac644Thanks @joshmkennedy! - Allows readonly arrays to be passed to thepaginate()functionv5.2.5Compare Source
Patch Changes
#13133
e76aa83Thanks @ematipico! - Fixes a bug where Astro was failing to build an external redirect when the middleware was triggered#13119
ac43580Thanks @Hacksore! - Adds extra guidance in the terminal when using theastro add tailwindCLI commandNow, 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.
v5.2.4Compare Source
Patch Changes
#13130
b71bd10Thanks @ascorbic! - Fixes a bug that caused duplicate slashes inside query params to be collapsed#13131
d60c742Thanks @ascorbic! - Ignores trailing slashes for endpoints with file extensions in the routeUpdated dependencies [
b71bd10]:v5.2.3Compare Source
Patch Changes
#13113
3a26e45Thanks @unprintable123! - Fixes the bug that rewrite will pass encoded url to the dynamic routing and cause params mismatch.#13111
23978ddThanks @ascorbic! - Fixes a bug that caused injected endpoint routes to return not found when trailingSlash was set to always#13112
0fa5c82Thanks @ematipico! - Fixes a bug where the i18n middleware was blocking a server island request when theprefixDefaultLocaleoption is set totruev5.2.2Compare Source
Patch Changes
187c4d3Thanks @ascorbic! - Fixes a bug that caused peer dependency errors when runningastro add tailwindv5.2.1Compare Source
Patch Changes
740eb60Thanks @ascorbic! - Fixes a bug that caused some dev server asset requests to return 404 when trailingSlash was set to "always"v5.2.0Compare Source
Minor Changes
#12994
5361755Thanks @ascorbic! - Redirects trailing slashes for on-demand pagesWhen the
trailingSlashoption is set toalwaysornever, 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
e621712Thanks @ematipico! - Adds support for redirecting to external sites with theredirectsconfiguration option.Now, you can redirect routes either internally to another path or externally by providing a URL beginning with
httporhttps:#13084
0f3be31Thanks @ematipico! - Adds a new experimental virtual moduleastro:configthat exposes a type-safe subset of yourastro.config.mjsconfigurationThe 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.serializeManifestfeature flag to your Astro config:Then, you can access the module in any file inside your project to import and use values from your Astro config:
For a complete overview, and to give feedback on this experimental API, see the Serialized Manifest RFC.
Patch Changes
#13049
2ed4bd9Thanks @florian-lefebvre! - Updatesastro add tailwindto add the@tailwindcss/viteplugin instead of the@astrojs/tailwindintegration#12994
5361755Thanks @ascorbic! - Returns a more helpful 404 page in dev if there is a trailing slash mismatch between the route requested and thetrailingSlashconfiguration#12666
037495dThanks @Thodor12! - Added additional generated typings for the content layerUpdated dependencies [
5361755,db252e0]:v5.1.10Compare Source
Patch Changes
#13058
1a14b53Thanks @ascorbic! - Fixes broken type declaration#13059
e36837fThanks @ascorbic! - Fixes a bug that caused tsconfig path aliases to break if there was more than one wildcard pattern#13045
c7f1366Thanks @mtwilliams-code! - Fixes a bug where the some utility functions of theastro:i18nvirtual module would return an incorrect result whentrailingSlashis set toneverv5.1.9Compare Source
Patch Changes
#12986
8911bdaThanks @wetheredge! - Updates types and dev toolbar for ARIA 1.2 attributes and roles#12892
8f520f1Thanks @louisescher! - Adds a more descriptive error when a content collection entry has an invalid ID.#13031
f576519Thanks @florian-lefebvre! - Updates the server islands encoding logic to only escape the script end tag open delimiter and opening HTML comment syntax#13026
1d272f6Thanks @ascorbic! - Fixes a regression that prevented the import of Markdown files as raw text or URLs.v5.1.8Compare Source
Patch Changes
#12998
9ce0038Thanks @Kynson! - Fixes the issue that audit incorrectly flag images as above the fold when the scrolling container is not body#12990
2e12f1dThanks @ascorbic! - Fixes a bug that caused references to be incorrectly reported as invalid#12984
2d259cfThanks @ascorbic! - Fixes a bug in dev where files would stop being watched if the Astro config file was edited#12984
2d259cfThanks @ascorbic! - Fixes a bug where the content layer would use an outdated version of the Astro config if it was edited in dev#12982
429aa75Thanks @bluwy! - Fixes an issue where server islands do not work in projects that use an adapter but only have prerendered pages. If an adapter is added, the server island endpoint will now be added by default.#12995
78fd73aThanks @florian-lefebvre! - Fixes a case whereastro:actionstypes would not work when usingsrc/actions.ts#13011
cf30880Thanks @ascorbic! - Upgrades Vite#12733
bbf1d88Thanks @ascorbic! - Fixes a bug that caused the dev server to return an error if requesting "//"#13001
627aec3Thanks @ascorbic! - Fixes a bug that caused Astro to attempt to inject environment variables into non-source files, causing performance problems and broken buildsv5.1.7Compare Source
Patch Changes
#12361
3d89e62Thanks @LunaticMuch! - Upgrades theesbuildversion to matchvite#12980
1a026afThanks @florian-lefebvre! - Fixes a case where setting the status of a page to404in development would show the default 404 page (or custom one if provided) instead of using the current page#12182
c30070bThanks @braden-w! - Improves matching of 404 and 500 routesUpdated dependencies [
3d89e62]:v5.1.6Compare Source
Patch Changes
#12956
3aff68aThanks @kaytwo! - Removes encryption of empty props to allow server island cacheability#12977
80067c0Thanks @florian-lefebvre! - Fixes a case where accessingastro:envAPIs orimport.meta.envinside the content config file would not work#12839
57be349Thanks @mtwilliams-code! - Fix Astro.currentLocale returning the incorrect locale when using fallback rewrites in SSR mode#12962
4b7a2ceThanks @ascorbic! - Skips updating content layer files if content is unchanged#12942
f00c2ddThanks @liruifengv! - Improves the session error messages#12966
d864e09Thanks @ascorbic! - Ensures old content collection entry is deleted if a markdown frontmatter slug is changed in devv5.1.5Compare Source
Patch Changes
#12934
673a518Thanks @ematipico! - Fixes a regression where the Astro Container didn't work during the build, usingpnpm#12955
db447f2Thanks @martrapp! - Lets TypeScript know about the "blocking" and "disabled" attributes of the<link>element.#12922
faf74afThanks @adamchal! - Improves performance of static asset generation by fixing a bug that caused image transforms to be performed serially. This fix ensures that processing uses all CPUs when running in a multi-core environment.#12947
3c2292fThanks @ascorbic! - Fixes a bug that caused empty content collections when running dev with NODE_ENV setv5.1.4Compare Source
Patch Changes
#12927
ad2a752Thanks @ematipico! - Fixes a bug where Astro attempted to decode a request URL multiple times, resulting in an unexpected behaviour when decoding the character%#12912
0c0c66bThanks @florian-lefebvre! - Improves the config error for invalid combinations ofcontextandaccessproperties underenv.schema#12935
3d47e6bThanks @AirBorne04! - Fixes an issue whereAstro.localscoming from an adapter weren't available in the404.astro, when using theastro devcommand,#12925
44841fcThanks @ascorbic! - Ensures image styles are not imported unless experimental responsive images are enabled#12926
8e64bb7Thanks @oliverlynch! - Improves remote image cache efficiency by separating image data and metadata into a binary and sidecar JSON file.#12920
8b9d530Thanks @bluwy! - Processes markdown with empty body as remark and rehype plugins may add additional content or frontmatter#12918
fd12a26Thanks @lameuler! - Fixes a bug where the logged output path does not match the actual output path when usingbuild.format: 'preserve'#12676
2ffc0fcThanks @koyopro! - Allows configuring Astro modules TypeScript compilation with thevite.esbuildconfig#12938
dbb04f3Thanks @ascorbic! - Fixes a bug where content collections would sometimes appear empty when first running astro dev#12937
30edb6dThanks @ematipico! - Fixes a bug where users could useAstro.request.headersduring a rewrite inside prerendered routes. This an invalid behaviour, and now Astro will show a warning if this happens.#12937
30edb6dThanks @ematipico! - Fixes an issue where the use ofAstro.rewritewould trigger the invalid use ofAstro.request.headersv5.1.3Compare Source
Patch Changes
#12877
73a0788Thanks @bluwy! - Fixes sourcemap warning generated by theastro:server-islandsVite plugin#12906
2d89492Thanks @ascorbic! - Fixes a bug that caused pages that return an empty array from getStaticPath to match every path011fa0fThanks @florian-lefebvre! - Fixes a case whereastro:contenttypes would be erased when restarting the dev server#12907
dbf1275Thanks @florian-lefebvre! - Fixes a regression around the server islands route, which was not passed to the adaptersastro:build:donehook#12818
579bd93Thanks @ascorbic! - Fixes race condition where dev server would attempt to load collections before the content had loaded#12883
fbac92fThanks @kaytwo! - Fixes a bug where responses can be returned before session data is saved#12815
3acc654Thanks @ericswpark! - Some non-index files that were incorrectly being treated as index files are now excluded#12884
d7e97a7Thanks @ascorbic! - Addsrender()to stub content types#12883
fbac92fThanks @kaytwo! - Fixes a bug where session data could be corrupted if it is changed after calling .set()#12827
7b5dc6fThanks @sinskiy! - Fixes an issue when crawlers try to index Server Islands thinking that Server Islands are pagesv5.1.2Compare Source
Patch Changes
#12798
7b0cb85Thanks @ascorbic! - Improves warning logs for invalid content collection configuration#12781
96c4b92Thanks @ascorbic! - Fixes a regression that causeddefault()to not work withreference()#12820
892dd9fThanks @ascorbic! - Fixes a bug that caused cookies to not be deleted when destroying a session#12864
440d8a5Thanks @kaytwo! - Fixes a bug where the session ID wasn't correctly regenerated#12768
524c855Thanks @ematipico! - Fixes an issue where Astro didn't print error logs when Astro Islands were used in incorrect cases.#12814
f12f111Thanks @ematipico! - Fixes an issue where Astro didn't log anything in case a file isn't created during the build.#12875
e109002Thanks @ascorbic! - Fixes a bug in emulated legacy collections where the entry passed to the getCollection filter function did not include the legacy entry fields.#12768
524c855Thanks @ematipico! - Fixes an issue where Astro was printing the incorrect output format when running theastro buildcommand#12810
70a9f0bThanks @louisescher! - Fixes server islands failing to check content-type header under certain circumstancesSometimes a reverse proxy or similar service might modify the content-type header to include the charset or other parameters in the media type of the response. This previously wasn't handled by the client-side server island script and thus removed the script without actually placing the requested content in the DOM. This fix makes it so the script checks if the header starts with the proper content type instead of exactly matching
text/html, so the following will still be considered a valid header:text/html; charset=utf-8#12816
7fb2184Thanks @ematipico! - Fixes an issue where an injected route entrypoint wasn't correctly marked because the resolved file path contained a query parameter.This fixes some edge case where some injected entrypoint were not resolved when using an adapter.
v5.1.1Compare Source
Patch Changes
#13058
1a14b53Thanks @ascorbic! - Fixes broken type declaration#13059
e36837fThanks @ascorbic! - Fixes a bug that caused tsconfig path aliases to break if there was more than one wildcard pattern#13045
c7f1366Thanks @mtwilliams-code! - Fixes a bug where the some utility functions of theastro:i18nvirtual module would return an incorrect result whentrailingSlashis set toneverv5.1.0Compare Source
Minor Changes
#12441
b4fec3cThanks @ascorbic! - Adds experimental session supportSessions are used to store user state between requests for server-rendered pages, such as login status, shopping cart contents, or other user-specific data.
Sessions are available in on-demand rendered/SSR pages, API endpoints, actions and middleware. To enable session support, you must configure a storage driver.
If you are using the Node.js adapter, you can use the
fsdriver to store session data on the filesystem:If you are deploying to a serverless environment, you can use drivers such as
redis,netlify-blobs,vercel-kv, orcloudflare-kv-bindingand optionally pass additional configuration options.For more information, including using the session API with other adapters and a full list of supported drivers, see the docs for experimental session support. For even more details, and to leave feedback and participate in the development of this feature, the Sessions RFC.
#12426
3dc02c5Thanks @oliverlynch! - Improves asset caching of remote imagesAstro will now store entity tags and the Last-Modified date for cached remote images and use them to revalidate the cache when it goes stale.
#12721
c9d5110Thanks @florian-lefebvre! - Adds a newgetActionPath()helper available fromastro:actionsAstro 5.1 introduces a new helper function,
getActionPath()to give you more flexibility when calling your action.Calling
getActionPath()with your action returns its URL path so you can make afetch()request with custom headers, or use your action with an API such asnavigator.sendBeacon(). Then, you can handle the custom-formatted returned data as needed, just as if you had called an action directly.This example shows how to call a defined
likeaction passing theAuthorizationheader and thekeepaliveoption:This example shows how to call the same
likeaction using thesendBeaconAPI:Patch Changes
#12786
e56af4aThanks @ematipico! - Fixes an issue where Astro i18n didn't properly show the 404 page when using fallback and the optionprefixDefaultLocaleset totrue.#12758
483da89Thanks @delucis! - Adds types for?url&inlineand?url&no-inlineimport queries added in Vite 6#12763
8da2318Thanks @rbsummers! - Fixed changes to vite configuration made in the astro:build:setup integration hook having no effect when target is "client"#12767
36c1e06Thanks @ascorbic! - Clears the content layer cache when the Astro config is changedv5.0.9Compare Source
Patch Changes
95795f8Thanks @matthewp! - Remove debug logging from buildv5.0.8Compare Source
Patch Changes
039d022Thanks @matthewp! - Clean server sourcemaps from static outputv5.0.7Compare Source
Patch Changes
c879f50Thanks @matthewp! - Remove all assets created from the server buildv5.0.6Compare Source
Patch Changes
#12597
564ac6cThanks @florian-lefebvre! - Fixes an issue where image and server islands routes would not be passed to theastro:routes:resolvedhook during builds#12718
ccc5ad1Thanks @ematipico! - Fixes an issue where Astro couldn't correctly handle i18n fallback when using the i18n middleware#12728
ee66a45Thanks @argyleink! - Adds type support for theclosedbyattribute for<dialog>elements#12709
e3bfd93Thanks @mtwilliams-code! - Fixes a bug where Astro couldn't correctly parseparamsandpropswhen receiving i18n fallback URLs#12657
14dffccThanks @darkmaga! - Trailing slash support for actions#12715
029661dThanks @ascorbic! - Fixes a bug that caused errors in dev when editing sites with large numbers of MDX pages#12729
8b1cecdThanks @JoeMorgan! - "Addedinertto htmlBooleanAttributes"#12726
7c7398cThanks @florian-lefebvre! - Fixes a case where failing content entries inastro checkwould not be surfacedv5.0.5Compare Source
Patch Changes
#12705
0d1eab5Thanks @ascorbic! - Fixes a bug where MDX files with certain characters in the name would cause builds to fail#12707
2aaed2dThanks @ematipico! - Fixes a bug where the middleware was incorrectly imported during the build#12697
1c4a032Thanks @ascorbic! - Fix a bug that caused builds to fail if an image had a quote mark in its name#12694
495f46bThanks @ematipico! - Fixes a bug where the experimental featureexperimental.svgwas incorrectly used when generating ESM images#12658
3169593Thanks @jurajkapsz! - Fixes astro info copy to clipboard process not returning to prompt in certain cases.#12712
b01c74aThanks @ascorbic! - Fixes a bug which misidentified pages as markdown if a query string ended in a markdown extensionv5.0.4Compare Source
Patch Changes
#12653
e21c7e6Thanks @sarah11918! - Updates a reference in an error message#12585
a9373c0Thanks @florian-lefebvre! - Fixes a case whereprocess.envwould be frozen despite changes made to environment variables in development#12695
a203d5dThanks @ascorbic! - Throws a more helpful error when images are missingUpdated dependencies [
f13417b,87231b1,a71e9b9]:v5.0.3Compare Source
Patch Changes
#12645
8704c54Thanks @sarah11918! - Updates some reference links in error messages for new v5 docs.#12641
48ca399Thanks @ascorbic! - Fixes a bug whereastro info --copywasn't working correctly onmacOSsystems.#12461
62939adThanks @kyr0! - Removes the misleading log message telling that a custom renderer is not recognized while it clearly is and works.#12642
ff18b9cThanks @ematipico! - Provides more information when logging a warning for accessingAstro.request.headersin prerendered pages#12634
03958d9Thanks @delucis! - Improves error message formatting for user config and content collection frontmatter#12547
6b6e18dThanks @mtwilliams-code! - Fixes a bug where URL search parameters weren't passed when using the i18nfallbackfeature.#12449
e6b8017Thanks @apatel369! - Fixes an issue where the customassetFileNamesconfiguration 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
e216250Thanks @ematipico! - Fixes an issue where SSR error pages would return duplicated custom headers.#12625
74bfad0Thanks @ematipico! - Fixes an issue where theexperimental.svghad incorrect type, resulting in some errors in the editors.#12631
dec0305Thanks @ascorbic! - Fixes a bug where the class attribute was rendered twice on the image component#12623
0e4fecbThanks @ascorbic! - Correctly handles images in content collections with uppercase file extensions#12633
8a551c1Thanks @bluwy! - Cleans up content layer sync during builds and programmaticsync()calls#12640
22e405aThanks @ascorbic! - Fixes a bug that caused content collections to be returned empty when run in a test environment#12613
306c9f9Thanks @matthewp! - Fix use of cloned requests in middleware with clientAddressWhen using
context.clientAddressorAstro.clientAddressAstro 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.2Compare Source
Patch Changes
0724929Thanks @ascorbic! - Includes "undefined" in types for getEntryv5.0.1Compare Source
Patch Changes
92c269bThanks @kidonng! - fix: devtools warnings about dev toolbar form fieldsv5.0.0Compare Source
Major Changes
#11798
e9e2139Thanks @matthewp! - Unflag globalRoutePriorityThe previously experimental feature
globalRoutePriorityis 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
ee38b3aThanks @ematipico! - ### [changed]:entryPointtype inside the hookastro:build:ssrIn Astro v4.x, the
entryPointtype wasRouteData.Astro v5.0 the
entryPointtype isIntegrationRouteData, which contains a subset of theRouteDatatype. The fieldsisIndexandfallbackRouteswere removed.What should I do?
Update your adapter to change the type of
entryPointfromRouteDatatoIntegrationRouteData.#12524
9f44019Thanks @bluwy! - Bumps Vite to ^6.0.1 and handles its breaking changes#10742
b6fbdaaThanks @ematipico! - The lowest version of Node supported by Astro is now Node v18.17.1 and higher.#11916
46ea29fThanks @bluwy! - Updates how thebuild.clientandbuild.serveroption values get resolved to match existing documentation. With this fix, the option values will now correctly resolve relative to theoutDiroption. So ifoutDiris set to./dist/nested/, then by default:build.clientwill resolve to<root>/dist/nested/client/build.serverwill resolve to<root>/dist/nested/server/Previously the values were incorrectly resolved:
build.clientwas resolved to<root>/dist/nested/dist/client/build.serverwas 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
d84e444Thanks @Princesseuh! - Adds a default exclude and include value to the tsconfig presets.{projectDir}/distis now excluded by default, and{projectDir}/.astro/types.d.tsand{projectDir}/**/*are included by default.Both of these options can be overridden by setting your own values to the corresponding settings in your
tsconfig.jsonfile.#11861
3ab3b4eThanks @bluwy! - Cleans up Astro-specific metadata attached tovfile.datain 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.headingsvfile.data.imagePaths->vfile.data.astro.imagePathsThe types of
imagePathshas also been updated fromSet<string>tostring[]. Thevfile.data.astro.frontmattermetadata 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
bf90a53Thanks @florian-lefebvre! - Thelocalsobject can no longer be overriddenMiddleware, API endpoints, and pages can no longer override the
localsobject in its entirety. You can still append values onto the object, but you cannot replace the entire object and delete its existing values.If you were previously overwriting like so:
This can be changed to an assignment on the existing object instead:
#11908
518433eThanks @Princesseuh! - Theimage.endpointconfig 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/_imageconflicts with an existing route or your local server setup.#12008
5608338Thanks @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
ea71b90Thanks @florian-lefebvre! - Theastro:envfeature 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 usingastro: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
envoption 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 entireenvconfiguration unchanged to a top-level option.You can import and use your defined variables from the appropriate
/clientor/servermodule:Please see our guide to using environment variables for more about this feature.
#11806
f7f2338Thanks @Princesseuh! - Removes theassetsproperty onsupportedAstroFeaturesfor adapters, as it did not reflect reality properly in many cases.Now, relating to assets, only a single
sharpImageServiceproperty is available, determining if the adapter is compatible with the built-in sharp image service.#11864
ee38b3aThanks @ematipico! - ### [changed]:routestype inside the hookastro:build:doneIn Astro v4.x, the
routestype wasRouteData.Astro v5.0 the
routestype isIntegrationRouteData, which contains a subset of theRouteDatatype. The fieldsisIndexandfallbackRouteswere removed.What should I do?
Update your adapter to change the type of
routesfromRouteDatatoIntegrationRouteData.#11941
b6a5f39Thanks @Princesseuh! - Merges theoutput: 'hybrid'andoutput: 'static'configurations into one single configuration (now called'static') that works the same way as the previoushybridoption.It is no longer necessary to specify
output: 'hybrid'in your Astro config to use server-rendered pages. The newoutput: 'static'has this capability included. Astro will now automatically provide the ability to opt out of prerendering in your static site with no change to youroutputconfiguration required. Any page route or endpoint can includeexport const prerender = falseto be server-rendered, while the rest of your site is statically-generated.If your project used hybrid rendering, you must now remove the
output: 'hybrid'option from your Astro config as it no longer exists. However, no other changes to your project are required, and you should have no breaking changes. The previous'hybrid'behavior is now the default, under a new name'static'.If you were using the
output: 'static'(default) option, you can continue to use it as before. By default, all of your pages will continue to be prerendered and you will have a completely static site. You should have no breaking changes to your project.An adapter is still required to deploy an Astro project with any server-rendered pages. Failure to include an adapter will result in a warning in development and an error at build time.
#11788
7c0ccfcThanks @ematipico! - Updates the default value ofsecurity.checkOrigintotrue, which enables Cross-Site Request Forgery (CSRF) protection by default for pages rendered on demand.If you had previously configured
security.checkOrigin: true, you no longer need this set in your Astro config. This is now the default and it is safe to remove.To disable this behavior and opt out of automatically checking that the “origin” header matches the URL sent by each request, you must explicitly set
security.checkOrigin: false:#11825
560ef15Thanks @bluwy! - Updates internal Shiki rehype plugin to highlight code blocks as hast (using Shiki'scodeToHast()API). This allows a more direct Markdown and MDX processing, and improves the performance when building the project, but may cause issues with existing Shiki transformers.If you are using Shiki transformers passed to
markdown.shikiConfig.transformers, you must make sure they do not use thepostprocesshook as it no longer runs on code blocks in.mdand.mdxfiles. (See the Shiki documentation on transformer hooks for more information).Code blocks in
.mdocfiles and<Code />component do not use the internal Shiki rehype plugin and are unaffected.#11826
7315050Thanks @matthewp! - Deprecate Astro.globThe
Astro.globfunction has been deprecated in favor of Content Collections andimport.meta.glob.import.meta.glob(https://vitejs.dev/guide/features.html#glob-import).Also consider using glob packages from npm, like fast-glob, especially if statically generating your site, as it is faster for most use-cases.
The easiest path is to migrate to
import.meta.globlike so:#12268
4e9a3acThanks @ematipico! - The commandastro add vercelnow updates the configuration file differently, and adds@astrojs/vercelas module to import.This is a breaking change because it requires the version
8.*of@astrojs/vercel.#11741
6617491Thanks @bluwy! - Removes internal JSX handling and moves the responsibility to the@astrojs/mdxpackage directly. The following exports are also now removed:astro/jsx/babel.jsastro/jsx/component.jsastro/jsx/index.jsastro/jsx/renderer.jsastro/jsx/server.jsastro/jsx/transform-options.jsIf your project includes
.mdxfiles, you must upgrade@astrojs/mdxto the latest version so that it doesn't rely on these entrypoints to handle your JSX.#11782
9a2aaa0Thanks @Princesseuh! - Makes thecompiledContentproperty of Markdown content an async function, this change should fix underlying issues where sometimes when using a custom image service and images inside Markdown, Node would exit suddenly without any error message.#11819
2bdde80Thanks @bluwy! - Updates the Astro config loading flow to ignore processing locally-linked dependencies with Vite (e.g.npm link, in a monorepo, etc). Instead, they will be normally imported by the Node.js runtime the same way as other dependencies fromnode_modules.Previously, Astro would process locally-linked dependencies which were able to use Vite features like TypeScript when imported by the Astro config file.
However, this caused confusion as integration authors may test against a package that worked locally, but not when published. This method also restricts using CJS-only dependencies because Vite requires the code to be ESM. Therefore, Astro's behaviour is now changed to ignore processing any type of dependencies by Vite.
In most cases, make sure your locally-linked dependencies are built to JS before running the Astro project, and the config loading should work as before.
#11827
a83e362Thanks @matthewp! - Prevent usage ofastro:contentin the clientUsage of
astro:contentin the client has always been discouraged because it leads to all of your content winding up in your client bundle, and can possibly leaks secrets.This formally makes doing so impossible, adding to the previous warning with errors.
In the future Astro might add APIs for client-usage based on needs.
#11979
423dfc1Thanks @bluwy! - Bumpsvitedependency to v6.0.0-beta.2. The version is pinned and will be updated as new Vite versions publish to prevent unhandled breaking changes. For the full list of Vite-specific changes, see its changelog.#11859
3804711Thanks @florian-lefebvre! - Changes the defaulttsconfig.jsonwith better defaults, and makessrc/env.d.tsoptionalAstro's default
tsconfig.jsonin starter examples has been updated to include generated types and exclude your build output. This means thatsrc/env.d.tsis only necessary if you have added custom type declarations or if you're not using atsconfig.jsonfile.Additionally, running
astro syncno longer creates, nor updates,src/env.d.tsas it is not required for type-checking standard Astro projects.To update your project to Astro's recommended TypeScript settings, please add the following
includeandexcludeproperties totsconfig.json:#11715
d74617cThanks @Princesseuh! - Refactor the exported types from theastromodule. There should normally be no breaking changes, but if you relied on some previously deprecated types, these might now have been fully removed.In most cases, updating your code to move away from previously deprecated APIs in previous versions of Astro should be enough to fix any issues.
#12551
abf9a89Thanks @ematipico! - Refactors legacycontentanddatacollections to use the Content Layer APIglob()loader for better performance and to support backwards compatibility. Also introduces thelegacy.collectionsflag for projects that are unable to update to the new behavior immediately.⚠️ BREAKING CHANGE FOR LEGACY CONTENT COLLECTIONS ⚠️
By default, collections that use the old types (
contentordata) and do not define aloaderare now implemented under the hood using the Content Layer API's built-inglob()loader, with extra backward-compatibility handling.In order to achieve backwards compatibility with existing
contentcollections, the following have been implemented:globloader collection is defined, with patterns that match the previous handling (matchessrc/content/<collection name>/**/*.mdand other content extensions depending on installed integrations, with underscore-prefixed files and folders ignored)slugfield is added with the same format as beforerender()method is added to the entry, so they can be called usingentry.render()getEntryBySlugis supportedIn order to achieve backwards compatibility with existing
datacollections, the following have been implemented:globloader collection is defined, with patterns that match the previous handling (matchessrc/content/<collection name>/**/*{.json,.yaml}and other data extensions, with underscore-prefixed files and folders ignored)getDataEntryByIdis supportedWhile this backwards compatibility implementation is able to emulate most of the features of legacy collections, there are some differences and limitations that may cause breaking changes to existing collections:
src/content/, even if they were not defined insrc/content/config.ts. This behavior is now deprecated, and collections should always be defined insrc/content/config.ts. For existing collections, these can just be empty declarations (e.g.const blog = defineCollection({})) and Astro will implicitly define your legacy collection for you in a way that is compatible with the new loading behavior.layoutfield is not supported in Markdown collection entries. This property is intended only for standalone page files located insrc/pages/and not likely to be in your collection entries. However, if you were using this property, you must now create dynamic routes that include your page styling.getCollection(), the order in which entries are returned may be different than before. If you need a specific order, you should sort the collection entries yourself.image().refine()is not supported. If you need to validate the properties of an image you will need to do this at runtime in your page or component.keyargument ofgetEntry(collection, key)is typed asstring, rather than having types for every entry.A new legacy configuration flag
legacy.collectionsis added for users that want to keep their current legacy (content and data) collections behavior (available in Astro v2 - v4), or who are not yet ready to update their projects:When set, no changes to your existing collections are necessary, and the restrictions on storing both new and old collections continue to exist: legacy collections (only) must continue to remain in
src/content/, while new collections using a loader from the Content Layer API are forbidden in that folder.#11660
e90f559Thanks @bluwy! - Fixes attribute rendering for non-boolean HTML attributes with boolean values to match proper attribute handling in browsers.Previously, non-boolean attributes may not have included their values when rendered to HTML. In Astro v5.0, the values are now explicitly rendered as
="true"or="false"In the following
.astroexamples, onlyallowfullscreenis a boolean attribute:Astro v5.0 now preserves the full data attribute with its value when rendering the HTML of non-boolean attributes:
If you rely on attribute values, for example to locate elements or to conditionally render, update your code to match the new non-boolean attribute values:
#11770
cfa6a47Thanks @Princesseuh! - Removed support for the Squoosh image service. As the underlying librarylibsquooshis no longer maintained, and the image service sees very little usage we have decided to remove it from Astro.Our recommendation is to use the base Sharp image service, which is more powerful, faster, and more actively maintained.
If you are using this service, and cannot migrate to the base Sharp image service, a third-party extraction of the previous service is available here: https://github.com/Princesseuh/astro-image-service-squoosh
#12231
90ae100Thanks @bluwy! - Updates the automaticcharset=utf-8behavior for Markdown pages, where instead of responding withcharset=utf-8in theContent-Typeheader, Astro will now automatically add the<meta charset="utf-8">tag instead.This behaviour only applies to Markdown pages (
.mdor similar Markdown files located withinsrc/pages/) that do not use Astro's speciallayoutfrontmatter property. It matches the rendering behaviour of other non-content pages, and retains the minimal boilerplate needed to write with non-ASCII characters when adding individual Markdown pages to your site.If your Markdown pages use the
layoutfrontmatter property, then HTML encoding will be handled by the designated layout component instead, and the<meta charset="utf-8">tag will not be added to your page by default.If you require
charset=utf-8to render your page correctly, make sure that your layout components contain the<meta charset="utf-8">tag. You may need to add this if you have not already done so.#11714
8a53517Thanks @matthewp! - Remove support for functionPerRouteThis change removes support for the
functionPerRouteoption both in Astro and@astrojs/vercel.This option made it so that each route got built as separate entrypoints so that they could be loaded as separate functions. The hope was that by doing this it would decrease the size of each function. However in practice routes use most of the same code, and increases in function size limitations made the potential upsides less important.
Additionally there are downsides to functionPerRoute, such as hitting limits on the number of functions per project. The feature also never worked with some Astro features like i18n domains and request rewriting.
Given this, the feature has been removed from Astro.
#11864
ee38b3aThanks @ematipico! - ### [changed]:RouteData.distURLis now an arrayIn Astro v4.x,
RouteData.distURLwasundefinedor aURLAstro v5.0,
RouteData.distURLisundefinedor an array ofURL. This was a bug, because a route can generate multiple files on disk, especially when using dynamic routes such as[slug]or[...slug].What should I do?
Update your code to handle
RouteData.distURLas an array.#11253
4e5cc5aThanks @kevinzunigacuellar! - Changes the data returned forpage.url.current,page.url.next,page.url.prev,page.url.firstandpage.url.lastto include the value set forbasein your Astro config.Previously, you had to manually prepend your configured value for
baseto the URL path. Now, Astro automatically includes yourbasevalue innextandprevURLs.If you are using the
paginate()function for "previous" and "next" URLs, remove any existingbasevalue as it is now added for you:#12079
7febf1fThanks @ematipico! -paramspassed ingetStaticPathsare no longer automatically decoded.[changed]:
paramsaren't decoded anymore.In Astro v4.x,
paramsin were automatically decoded usingdecodeURIComponent.Astro v5.0 doesn't automatically decode
paramsingetStaticPathsanymore, so you'll need to manually decode them yourself if neededWhat should I do?
If you were relying on the automatic decode, you'll need to manually decode it using
decodeURI.Note that the use of
decodeURIComponent) is discouraged forgetStaticPathsbecause it decodes more characters than it should, for example/,?,#and more.Minor Changes
#11941
b6a5f39Thanks @Princesseuh! - Adapters can now specify the build output type they're intended for using theadapterFeatures.buildOutputproperty. This property can be used to always generate a server output, even if the project doesn't have any server-rendered pages.If your adapter specifies
buildOutput: 'static', and the user's project contains server-rendered pages, Astro will warn in development and error at build time. Note that a hybrid output, containing both static and server-rendered pages, is considered to be aserveroutput, as a server is required to serve the server-rendered pages.#12067
c48916cThanks @stramel! - Adds experimental support for built-in SVG components.This feature allows you to import SVG files directly into your Astro project as components. By default, Astro will inline the SVG content into your HTML output.
To enable this feature, set
experimental.svgtotruein your Astro config:To use this feature, import an SVG file in your Astro project, passing any common SVG attributes to the imported component. Astro also provides a
sizeattribute to set equalheightandwidthproperties:For a complete overview, and to give feedback on this experimental API, see the Feature RFC.
#12226
51d13e2Thanks @ematipico! - The following renderer fields and integration fields now acceptURLas a type:Renderers:
AstroRenderer.clientEntrypointAstroRenderer.serverEntrypointIntegrations:
InjectedRoute.entrypointAstroIntegrationMiddleware.entrypointDevToolbarAppEntry.entrypoint#12323
c280655Thanks @bluwy! - Updates to Vite 6.0.0-beta.6#12539
827093eThanks @bluwy! - Drops node 21 support#12243
eb41d13Thanks @florian-lefebvre! - ImprovesdefineConfigtype safety. TypeScript will now error if a group of related configuration options do not have consistent types. For example, you will now see an error if your language set fori18n.defaultLocaleis not one of the supported locales specified ini18n.locales.#12329
8309c61Thanks @florian-lefebvre! - Adds a newastro:routes:resolvedhook to the Integration API. Also update theastro:build:donehook by deprecatingroutesand adding a newassetsmap.When building an integration, you can now get access to routes inside the
astro:routes:resolvedhook:This hook runs before
astro:config:done, and whenever a route changes in development.The
routesarray fromastro:build:doneis now deprecated, and exposed properties are now available onastro:routes:resolved, except fordistURL. For this, you can use the newly exposedassetsmap:#11911
c3dce83Thanks @ascorbic! - The Content Layer API introduced behind a flag in 4.14.0 is now stable and ready for use in Astro v5.0.The new Content Layer API builds upon content collections, taking them beyond local files in
src/content/and allowing you to fetch content from anywhere, including remote APIs. These new collections work alongside your existing content collections, and you can migrate them to the new API at your own pace. There are significant improvements to performance with large collections of local files. For more details, see the Content Layer RFC.If you previously used this feature, you can now remove the
experimental.contentLayerflag from your Astro config:Loading your content
The core of the new Content Layer API is the loader, a function that fetches content from a source and caches it in a local data store. Astro 4.14 ships with built-in
glob()andfile()loaders to handle your local Markdown, MDX, Markdoc, and JSON files:You can then query using the existing content collections functions, and use a simplified
render()function to display your content:Creating a loader
You're not restricted to the built-in loaders – we hope you'll try building your own. You can fetch content from anywhere and return an array of entries:
For more advanced loading logic, you can define an object loader. This allows incremental updates and conditional loading, and gives full access to the data store. It also allows a loader to define its own schema, including generating it dynamically based on the source API. See the the Content Layer API RFC for more details.
Sharing your loaders
Loaders are better when they're shared. You can create a package that exports a loader and publish it to npm, and then anyone can use it on their site. We're excited to see what the community comes up with! To get started, take a look at some examples. Here's how to load content using an RSS/Atom feed loader:
To learn more, see the Content Layer RFC.
#11980
a604a0cThanks @matthewp! - ViewTransitions component renamed to ClientRouterThe
<ViewTransitions />component has been renamed to<ClientRouter />. There are no other changes than the name. The old name will continue to work in Astro 5.x, but will be removed in 6.0.This change was done to clarify the role of the component within Astro's View Transitions support. Astro supports View Transitions APIs in a few different ways, and renaming the component makes it more clear that the features you get from the ClientRouter component are slightly different from what you get using the native CSS-based MPA router.
We still intend to maintain the ClientRouter as before, and it's still important for use-cases that the native support doesn't cover, such as persisting state between pages.
#11875
a8a3d2cThanks @florian-lefebvre! - Adds a new propertyisPrerenderedto the globalsAstroandAPIContext. This boolean value represents whether or not the current page is prerendered:#12047
21b5e80Thanks @rgodha24! - Adds a new optionalparserproperty to the built-infile()loader for content collections to support additional file types such astomlandcsv.The
file()loader now accepts a second argument that defines aparserfunction. This allows you to specify a custom parser (e.g.toml.parseorcsv-parse) to create a collection from a file's contents. Thefile()loader will automatically detect and parse JSON and YAML files (based on their file extension) with no need for aparser.This works with any type of custom file formats including
csvandtoml. The following example defines a content collectiondogsusing a.tomlfile.After importing TOML's parser, you can load the
dogscollection into your project by passing both a file path andparserto thefile()loader.The
parserargument also allows you to load a single collection from a nested JSON document. For example, this JSON file contains multiple collections:You can separate these collections by passing a custom
parserto thefile()loader like so:And it continues to work with maps of
idtodata#11698
05139efThanks @ematipico! - Adds a new property to the globalsAstroandAPIContextcalledroutePattern. TheroutePatternrepresents the current route (component)that is being rendered by Astro. It's usually a path pattern will look like this:
blog/[slug]:#11941
b6a5f39Thanks @Princesseuh! - Adds a newbuildOutputproperty to theastro:config:donehook returning the build output type.This can be used to know if the user's project will be built as a static site (HTML files), or a server-rendered site (whose exact output depends on the adapter).
#12377
af867f3Thanks @ascorbic! - Adds experimental support for automatic responsive imagesThis feature is experimental and may change in future versions. To enable it, set
experimental.responsiveImagestotruein yourastro.config.mjsfile.When this flag is enabled, you can pass a
layoutprop to any<Image />or<Picture />component to create a responsive image. When a layout is set, images have automatically generatedsrcsetandsizesattributes based on the image's dimensions and the layout type. Images withresponsiveandfull-widthlayouts will have styles applied to ensure they resize according to their container.This
<Image />component will generate the following HTML output:Responsive image properties
These are additional properties available to the
<Image />and<Picture />components when responsive images are enabled:layout: The layout type for the image. Can beresponsive,fixed,full-widthornone. Defaults to value ofimage.experimentalLayout.fit: Defines how the image should be cropped if the aspect ratio is changed. Values match those of CSSobject-fit. Defaults tocover, or the value ofimage.experimentalObjectFitif set.position: Defines the position of the image crop if the aspect ratio is changed. Values match those of CSSobject-position. Defaults tocenter, or the value ofimage.experimentalObjectPositionif set.priority: If set, eagerly loads the image. Otherwise, images will be lazy-loaded. Use this for your largest above-the-fold image. Defaults tofalse.Default responsive image settings
You can enable responsive images for all
<Image />and<Picture />components by settingimage.experimentalLayoutwith a default value. This can be overridden by thelayoutprop on each component.Example:
For a complete overview, and to give feedback on this experimental API, see the Responsive Images RFC.
#12150
93351bcThanks @bluwy! - Adds support for passing values other than"production"or"development"to the--modeflag (e.g."staging","testing", or any custom value) to change the value ofimport.meta.env.MODEor the loaded.envfile. This allows you take advantage of Vite's mode feature.Also adds a new
--devOutputflag forastro buildthat will output a development-based build.Note that changing the
modedoes not change the kind of code transform handled by Vite and Astro:astro dev, Astro will transform code with debug information.astro build, Astro will transform code with the most optimized output and removes debug information.astro build --devOutput(new flag), Astro will transform code with debug information like inastro dev.This enables various use cases like:
The different modes can be used to load different
.envfiles, e.g..env.stagingor.env.production, which can be customized for each environment, for example with differentAPI_URLenvironment variable values.#12510
14feaf3Thanks @bholmesdev! - Changes the generated URL query param from_astroActionto_actionwhen submitting a form using Actions. This avoids leaking the framework name into the URL bar, which may be considered a security issue.#11806
f7f2338Thanks @Princesseuh! - The value of the different properties onsupportedAstroFeaturesfor adapters can now be objects, with asupportandmessageproperties. The content of themessageproperty will be shown in the Astro CLI when the adapter is not compatible with the feature, allowing one to give a better informational message to the user.This is notably useful with the new
limitedvalue, to explain to the user why support is limited.#12071
61d248eThanks @Princesseuh! -astro addno longer automatically setsoutput: 'server'. Since the default value of output now allows for server-rendered pages, it no longer makes sense to default to full server builds when you add an adapter#11955
d813262Thanks @matthewp! - Server Islands introduced behind an experimental flag in v4.12.0 is no longer experimental and is available for general use.Server islands are Astro's solution for highly cacheable pages of mixed static and dynamic content. They allow you to specify components that should run on the server, allowing the rest of the page to be more aggressively cached, or even generated statically.
Turn any
.astrocomponent into a server island by adding theserver:deferdirective and optionally, fallback placeholder content. It will be rendered dynamically at runtime outside the context of the rest of the page, allowing you to add longer cache headers for the pages, or even prerender them.If you were previously using this feature, please remove the experimental flag from your Astro config:
If you have been waiting for stabilization before using server islands, you can now do so.
Please see the server island documentation for more about this feature.
#12373
d10f918Thanks @bholmesdev! - Changes the default behavior for Astro Action form requests to a standard POST submission.In Astro 4.x, actions called from an HTML form would trigger a redirect with the result forwarded using cookies. This caused issues for large form errors and return values that exceeded the 4 KB limit of cookie-based storage.
Astro 5.0 now renders the result of an action as a POST result without any forwarding. This will introduce a "confirm form resubmission?" dialog when a user attempts to refresh the page, though it no longer imposes a 4 KB limit on action return value.
v4.16.19Compare Source
Patch Changes
760acc8Thanks @ematipico! - Fixes an issue where remote paths weren't correctly computed when generating assetsv4.16.18Compare Source
Patch Changes
#12757
d0aaac3Thanks @matthewp! - Remove all assets created from the server build#12757
d0aaac3Thanks @matthewp! - Clean server sourcemaps from static outputv4.16.17Compare Source
Patch Changes
e7d14c3Thanks @ematipico! - Fixes an issue where thecheckOriginfeature wasn't correctly checking thecontent-typeheaderv4.16.16Compare Source
Patch Changes
#12542
65e50ebThanks @kadykov! - Fix JPEG image size determination#12525
cf0d8b0Thanks @ematipico! - Fixes an issue where withi18nenabled, Astro couldn't render the404.astrocomponent for non-existent routes.v4.16.15Compare Source
Patch Changes
b140a3fThanks @ematipico! - Fixes a regression where Astro was trying to accessRequest.headersv4.16.14Compare Source
Patch Changes
#12480
c3b7e7cThanks @matthewp! - Removes the default throw behavior inastro:env#12444
28dd3ceThanks @ematipico! - Fixes an issue where a server island hydration script might fail case the island ID misses from the DOM.#12476
80a9a52Thanks @florian-lefebvre! - Fixes a case where the Content Layerglob()loader would not update when renaming or deleting an entry#12418
25baa4eThanks @oliverlynch! - Fix cached image redownloading if it is the first asset#12477
46f6b38Thanks @ematipico! - Fixes an issue where the SSR build was emitting thedist/server/entry.mjsfile with an incorrect import at the top of the file/#12365
a23985bThanks @apatel369! - Fixes an issue whereAstro.currentLocalewas not correctly returning the locale for 404 and 500 pages.v4.16.13Compare Source
Patch Changes
#12436
453ec6bThanks @martrapp! - Fixes a potential null access in the clientside router#12392
0462219Thanks @apatel369! - Fixes an issue where scripts were not correctly injected during the build. The issue was triggered when there were injected routes with the sameentrypointand differentpatternv4.16.12Compare Source
Patch Changes
acac0afThanks @ematipico! - Fixes an issue where the dev server returns a 404 status code when a user middleware returns a validResponse.v4.16.11Compare Source
Patch Changes
#12305
f5f7109Thanks @florian-lefebvre! - Fixes a case where the error overlay would not escape the message#12402
823e73bThanks @ematipico! - Fixes a case where Astro allowed to call an action without usingAstro.callAction. This is now invalid, and Astro will show a proper error.#12401
9cca108Thanks @bholmesdev! - Fixes unexpected 200 status in dev server logs for action errors and redirects.v4.16.10Compare Source
Patch Changes
#12311
bf2723eThanks @dinesh-58! - Addscheckedto the list of boolean attributes.#12363
222f718Thanks @Fryuni! - Fixes code generated byastro addcommand when adding a version of an integration other than the defaultlatest.#12368
493fe43Thanks @bluwy! - Improves error logs when executing commands#12355
c4726d7Thanks @apatel369! - Improves error reporting for invalid frontmatter in MDX files during theastro buildcommand. The error message now includes the file path where the frontmatter parsing failed.v4.16.9Compare Source
Patch Changes
#12333
836cd91Thanks @imattacus! - Destroy the server response stream if async error is thrown#12358
7680349Thanks @spacedawwwg! - HonorsinlineAstroConfigparameter ingetViteConfigwhen creating a logger#12353
35795a1Thanks @hippotastic! - Fixes an issue in dev server watch file handling that could cause multiple restarts for a single file change.#12351
5751488Thanks @florian-lefebvre! - Reverts a change made in4.16.6that prevented usage ofastro:envsecrets inside middleware in SSR#12346
20e5a84Thanks @bluwy! - Fixes sourcemap generation when prefetch is enabled#12349
1fc83d3Thanks @norskeld! - Fixes thegetImageoptions type so it properly extendsImageTransformv4.16.8Compare Source
Patch Changes
#12338
9ca89b3Thanks @situ2001! - ResetsNODE_ENVto ensure install command run in dev mode#12286
9d6bcdbThanks @florian-lefebvre! - Fixes a case where a warning for experimentalastro:envsupport would be shown when using an adapter but not actually usingastro:env#12342
ffc836bThanks @liruifengv! - Fixes a typo in the command name of the CLI#12301
0cfc69dThanks @apatel369! - Fixes an issue with action handler context by passing the correct context (ActionAPIContext).#12312
5642ef9Thanks @koyopro! - Fixes an issue where usinggetViteConfig()returns incorrect and duplicate configuration#12245
1d4f6a4Thanks @bmenant! - Addcomponentsproperty to MDXInstance type definition (RenderResult and module import)#12340
94eaeeaThanks @ematipico! - Fixes an issue where Astro actions didn't work whenbasewas different from/v4.16.7Compare Source
Patch Changes
#12263
e9e8080Thanks @Fryuni! - Fixes conflict between server islands and on-demand dynamic routes in the form of/[...rest]or/[paramA]/[paramB].#12279
b781f88Thanks @jsparkdev! - Update wrong error message#12273
c2ee963Thanks @ascorbic! - Fixes an issue with some package managers where sites would not build if TypeScript was not installed.#12235
a75bc5eThanks @ematipico! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.#11839
ff522b9Thanks @icaliman! - Fixes error when returning a top-levelnullfrom an Astro file frontmatter#12272
388d237Thanks @ascorbic! - Correctly handles local images when using a base path in SSRv4.16.6Compare Source
Patch Changes
#11823
a3d30a6Thanks @DerTimonius! - fix: improve error message when inferSize is used in local images with the Image component#12227
8b1a641Thanks @florian-lefebvre! - Fixes a case where environment variables would not be refreshed when usingastro:env#12239
2b6daa5Thanks @ematipico! - BREAKING CHANGE to the experimental Container API onlyChanges the default page rendering behavior of Astro components in containers, and adds a new option
partial: falseto render full Astro pages as before.Previously, the Container API was rendering all Astro components as if they were full Astro pages containing
<!DOCTYPE html>by default. This was not intended, and now by default, all components will render as page partials: only the contents of the components without a page shell.To render the component as a full-fledged Astro page, pass a new option called
partial: falsetorenderToString()andrenderToResponse():v4.16.5Compare Source
Patch Changes
ff68ba5Thanks @martrapp! - Fixes an issue with cssesc in dev mode when settingvite.ssr.noExternal: truev4.16.4Compare Source
Patch Changes
#12223
79ffa5dThanks @ArmandPhilippot! - Fixes a false positive reported by the dev toolbar Audit app where a label was considered missing when associated with a buttonThe
buttonelement can be used with a label (e.g. to create a switch) and should not be reported as an accessibility issue when used as a child of alabel.#12199
c351352Thanks @ematipico! - Fixes a regression in the computation ofAstro.currentLocale#12222
fb55695Thanks @ematipico! - Fixes an issue where the edge middleware couldn't correctly compute the client IP address when callingctx.clientAddress()v4.16.3Compare Source
Patch Changes
#12220
b049359Thanks @bluwy! - Fixes accidental internalsetOnSetGetEnvparameter rename that caused runtime errors#12197
2aa2dfdThanks @ematipico! - Fix a regression where a port was incorrectly added to theAstro.urlv4.16.2Compare Source
Patch Changes
12b0022Thanks @bluwy! - Reverts #12173 which causedCan't modify immutable headerswarnings and 500 errors on Cloudflare Pagesv4.16.1Compare Source
Patch Changes
#12177
a4ffbfaThanks @matthewp! - Ensure we target scripts for execution in the routerUsing
document.scriptsis unsafe because if the application has aname="scripts"this will shadow the built-indocument.scripts. Fix is to usegetElementsByTagNameto ensure we're only grabbing real scripts.#12173
2d10de5Thanks @ematipico! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.v4.16.0Compare Source
Minor Changes
#12039
710a1a1Thanks @ematipico! - Adds amarkdown.shikiConfig.langAliasoption that allows aliasing a non-supported code language to a known language. This is useful when the language of your code samples is not a built-in Shiki language, but you want your Markdown source to contain an accurate language while also displaying syntax highlighting.The following example configures Shiki to highlight
cjscode blocks using thejavascriptsyntax highlighter:Then in your Markdown, you can use the alias as the language for a code block for syntax highlighting:
#11984
3ac2263Thanks @chaegumi! - Adds a newbuild.concurrenyconfiguration option to specify the number of pages to build in parallelIn most cases, you should not change the default value of
1.Use this option only when other attempts to reduce the overall rendering time (e.g. batch or cache long running tasks like fetch calls or data access) are not possible or are insufficient.
Use this option only if the refactors are not possible. If the number is set too high, the page rendering may slow down due to insufficient memory resources and because JS is single-threaded.
Patch Changes
#12160
c6fd1dfThanks @louisescher! - Fixes a bug whereastro.config.mtsandastro.config.ctsweren't reloading the dev server upon modifications.#12130
e96bcaeThanks @thehansys! - Fixes a bug in the parsing ofx-forwarded-\*Requestheaders, where multiple values assigned to those headers were not correctly parsed.Now, headers like
x-forwarded-proto: https,httpare correctly parsed.#12147
9db755aThanks @ascorbic! - Skips setting statusMessage header for HTTP/2 responseHTTP/2 doesn't support status message, so setting this was logging a warning.
#12151
bb6d37fThanks @ematipico! - Fixes an issue whereAstro.currentLocalewasn't incorrectly computed when thedefaultLocalebelonged to a custom locale path.Updated dependencies [
710a1a1]:v4.15.12Compare Source
Patch Changes
#12121
2490cebThanks @ascorbic! - Support passing the valuesInfinityand-Infinityas island props.#12118
f47b347Thanks @Namchee! - Removes thestrip-ansidependency in favor of the native Node API#12126
6e1dfebThanks @ascorbic! - Clear content layer cache when astro version changes#12117
a46839aThanks @ArmandPhilippot! - Updates Vite links to use their new domain#12124
499fbc9Thanks @ascorbic! - Allows special characters in Action names#12123
b8673dfThanks @Princesseuh! - Fixes missingbodyproperty on CollectionEntry types for content layer entries#12132
de35daaThanks @jcayzac! - Updates thecookiedependency to avoid the CVE 2024-47764 vulnerability.#12113
a54e520Thanks @ascorbic! - Adds a helpful error when attempting to render an undefined collection entryv4.15.11Compare Source
Patch Changes
#12097
11d447fThanks @ascorbic! - Fixes error where references in content layer schemas sometimes incorrectly report as missing#12108
918953bThanks @lameuler! - Fixes a bug where data URL images were not correctly handled. The bug resulted in anENAMETOOLONGerror.#12105
42037f3Thanks @ascorbic! - Returns custom statusText that has been set in a Response#12109
ea22558Thanks @ematipico! - Fixes a regression that was introduced by an internal refactor of how the middleware is loaded by the Astro application. The regression was introduced by #11550.When the edge middleware feature is opted in, Astro removes the middleware function from the SSR manifest, and this wasn't taken into account during the refactor.
#12106
d3a74daThanks @ascorbic! - Handles case where an immutable Response object is returned from an endpoint#12090
d49a537Thanks @markjaquith! - Server islands: changes the server island HTML placeholder comment so that it is much less likely to get removed by HTML minifiers.v4.15.10Compare Source
Patch Changes
#12084
12dae50Thanks @Princesseuh! - Adds missing filePath property on content layer entries#12046
d7779dfThanks @martrapp! - View transitions: Fixes Astro's fade animation to prevent flashing during morph transitions.#12043
1720c5bThanks @bluwy! - Fixes injected endpointprerenderoption detection#12095
76c5fbdThanks @TheOtterlord! - Fix installing non-stable versions of integrations withastro addv4.15.9Compare Source
Patch Changes
#12034
5b3ddfaThanks @ematipico! - Fixes an issue where the middleware wasn't called when a project uses404.astro.#12042
243ecb6Thanks @ematipico! - Fixes a problem in the Container API, where a polyfill wasn't correctly applied. This caused an issue in some environments wherecryptoisn't supported.#12038
26ea5e8Thanks @ascorbic! - Resolves image paths in content layer with initial slash as project-relativeWhen using the
image()schema helper, previously paths with an initial slash were treated as public URLs. This was to match the behavior of markdown images. However this is a change from before, where paths with an initial slash were treated as project-relative. This change restores the previous behavior, so that paths with an initial slash are treated as project-relative.v4.15.8Compare Source
Patch Changes
#12014
53cb41eThanks @ascorbic! - Fixes an issue where component styles were not correctly included in rendered MDX#12031
8c0cae6Thanks @ematipico! - Fixes a bug where the rewrite vianext(/*..*/)inside a middleware didn't compute the newAPIContext.params#12026
40e7a1bThanks @bluwy! - Initializes the Markdown processor only when there's.mdfiles#12028
d3bd673Thanks @bluwy! - Handles route collision detection only if it matchesgetStaticPaths#12027
dd3b753Thanks @fviolette! - Addselectedto the list of boolean attributes#12001
9be3e1bThanks @uwej711! - Remove dependency on path-to-regexpv4.15.7Compare Source
Patch Changes
#12000
a2f8c5dThanks @ArmandPhilippot! - Fixes an outdated link used to document Content Layer API#11915
0b59fe7Thanks @azhirov! - Fix: prevent island from re-rendering when using transition:persist (#11854)v4.15.6Compare Source
Patch Changes
#11993
ffba5d7Thanks @matthewp! - Fix getStaticPaths regressionThis reverts a previous change meant to remove a dependency, to fix a regression with multiple nested spread routes.
#11964
06eff60Thanks @TheOtterlord! - Add wayland (wl-copy) support toastro infov4.15.5Compare Source
Patch Changes
#11939
7b09c62Thanks @bholmesdev! - Adds support for Zod discriminated unions on Action form inputs. This allows forms with different inputs to be submitted to the same action, using a given input to decide which object should be used for validation.This example accepts either a
createorupdateform submission, and uses thetypefield to determine which object to validate against.The corresponding
createandupdateforms may look like this:#11968
86ad1fdThanks @NikolaRHristov! - Fixes a typo in the server island JSDoc#11983
633eeaaThanks @uwej711! - Remove dependency on path-to-regexpv4.15.4Compare Source
Patch Changes
#11879
bd1d4aaThanks @matthewp! - Allow passing a cryptography key via ASTRO_KEYFor Server islands Astro creates a cryptography key in order to hash props for the islands, preventing accidental leakage of secrets.
If you deploy to an environment with rolling updates then there could be multiple instances of your app with different keys, causing potential key mismatches.
To fix this you can now pass the
ASTRO_KEYenvironment variable to your build in order to reuse the same key.To generate a key use:
This will print out an environment variable to set like:
#11935
c58193aThanks @Princesseuh! - Fixesastro addnot using the proper export point when adding certain adaptersv4.15.3Compare Source
Patch Changes
#11902
d63bc50Thanks @ascorbic! - Fixes case where content layer did not update during clean dev builds on Linux and Windows#11886
7ff7134Thanks @matthewp! - Fixes a missing error message when actions throws duringastro sync#11904
ca54e3fThanks @wtchnm! - perf(assets): avoid downloading original image when using cachev4.15.2Compare Source
Patch Changes
#11870
8e5257aThanks @ArmandPhilippot! - Fixes typo in documenting thefallbackTypeproperty in i18n routing#11884
e450704Thanks @ascorbic! - Correctly handles content layer data where the transformed value does not match the input schema#11900
80b4a18Thanks @delucis! - Fixes the user-facing type of the newi18n.routing.fallbackTypeoption to be optionalv4.15.1Compare Source
Patch Changes
#11872
9327d56Thanks @bluwy! - Fixesastro addimporting adapters and integrations#11767
d1bd1a1Thanks @ascorbic! - Refactors content layer sync to use a queuev4.15.0Compare Source
Minor Changes
#11729
1c54e63Thanks @ematipico! - Adds a new variantsyncfor theastro:config:setuphook'scommandproperty. This value is set when calling the commandastro sync.If your integration previously relied on knowing how many variants existed for the
commandproperty, you must update your logic to account for this new option.#11743
cce0894Thanks @ph1p! - Adds a new, optional propertytimeoutfor theclient:idledirective.This value allows you to specify a maximum time to wait, in milliseconds, before hydrating a UI framework component, even if the page is not yet done with its initial load. This means you can delay hydration for lower-priority UI elements with more control to ensure your element is interactive within a specified time frame.
#11677
cb356a5Thanks @ematipico! - Adds a new optionfallbackTypetoi18n.routingconfiguration that allows you to control how fallback pages are handled.When
i18n.fallbackis configured, this new routing option controls whether to redirect to the fallback page, or to rewrite the fallback page's content in place.The
"redirect"option is the default value and matches the current behavior of the existing fallback system.The option
"rewrite"uses the new rewriting system to create fallback pages that render content on the original, requested URL without a browser refresh.For example, the following configuration will generate a page
/fr/index.htmlthat will contain the same HTML rendered by the page/en/index.htmlwhensrc/pages/fr/index.astrodoes not exist.#11708
62b0d20Thanks @martrapp! - Adds a new objectswapFunctionsto expose the necessary utility functions onastro:transitions/clientthat allow you to build custom swap functions to be used with view transitions.The example below uses these functions to replace Astro's built-in default
swapfunction with one that only swaps the<main>part of the page:See the view transitions guide for more information about hooking into the
astro:before-swaplifecycle event and adding a custom swap implementation.#11843
5b4070eThanks @bholmesdev! - Exposeszfrom the newastro:schemamodule. This is the new recommended import source for all Zod utilities when using Astro Actions.Migration for Astro Actions users
#11843
5b4070eThanks @bholmesdev! - The Astro Actions API introduced behind a flag in v4.8.0 is no longer experimental and is available for general use.Astro Actions allow you to define and call backend functions with type-safety, performing data fetching, JSON parsing, and input validation for you.
Actions can be called from client-side components and HTML forms. This gives you to flexibility to build apps using any technology: React, Svelte, HTMX, or just plain Astro components. This example calls a newsletter action and renders the result using an Astro component:
If you were previously using this feature, please remove the experimental flag from your Astro config:
If you have been waiting for stabilization before using Actions, you can now do so.
For more information and usage examples, see our brand new Actions guide.
Patch Changes
#11677
cb356a5Thanks @ematipico! - Fixes a bug in the logic ofAstro.rewrite()which led to the value forbase, if configured, being automatically prepended to the rewrite URL passed. This was unintended behavior and has been corrected, and Astro now processes the URLs exactly as passed.If you use the
rewrite()function on a project that hasbaseconfigured, you must now prepend the base to your existing rewrite URL:#11862
0e35afeThanks @ascorbic! - BREAKING CHANGE to experimental content layer loaders only!Passes
AstroConfiginstead ofAstroSettingsobject to content layer loaders.This will not affect you unless you have created a loader that uses the
settingsobject. If you have, you will need to update your loader to use theconfigobject instead.Other properties of the settings object are private internals, and should not be accessed directly. If you think you need access to other properties, please open an issue to discuss your use case.
#11772
6272e6cThanks @bluwy! - Usesmagicastto update the config forastro add#11845
440a4beThanks @bluwy! - Replacesexecawithtinyexecinternally#11858
8bab233Thanks @ascorbic! - Correctly resolves content layer images when filePath is not setv4.14.6Compare Source
Patch Changes
#11847
45b599cThanks @ascorbic! - Fixes a case where Vite would be imported by the SSR runtime, causing bundling errors and bloat.#11822
6fcaab8Thanks @bluwy! - Marks internalvite-plugin-fileurlplugin withenforce: 'pre'#11713
497324cThanks @voidfill! - Prevents prefetching of the same urls with different hashes.#11814
2bb72c6Thanks @eduardocereto! - Updates the documentation for experimental Content Layer API with a corrected code example#11842
1ffaae0Thanks @stephan281094! - Fixes a typo in theMissingImageDimensionerror message#11828
20d47aaThanks @bholmesdev! - Improves error message when invalid data is returned by an Action.v4.14.5Compare Source
Patch Changes
#11809
62e97a2Thanks @bholmesdev! - Fixes usage of.transform(),.refine(),.passthrough(), and other effects on Action form inputs.#11812
260c4beThanks @bholmesdev! - ExposesActionAPIContexttype from theastro:actionsmodule.#11813
3f7630aThanks @bholmesdev! - Fixes unexpectedundefinedvalue when calling an action from the client without a return value.v4.14.4Compare Source
Patch Changes
#11794
3691a62Thanks @bholmesdev! - Fixes unexpected warning log when using Actions on "hybrid" rendered projects.#11801
9f943c1Thanks @delucis! - Fixes a bug where thefilePathproperty was not available on content collection entries when using the content layerfile()loader with a JSON file that contained an object instead of an array. This was breaking use of theimage()schema utility among other things.v4.14.3Compare Source
Patch Changes
#11780
c6622adThanks @Princesseuh! - Deprecates the Squoosh image service, to be removed in Astro 5.0. We recommend migrating to the default Sharp service.#11790
41c3fcbThanks @sarah11918! - Updates the documentation for experimentalastro:envwith a corrected link to the RFC proposal#11773
86a3391Thanks @ematipico! - Changes messages logged when using unsupported, deprecated, or experimental adapter features for clarity#11745
89bab1eThanks @bluwy! - Prints prerender dynamic value usage warning only if it's used#11774
c6400abThanks @florian-lefebvre! - Fixes the path returned byinjectTypes#11730
2df49a6Thanks @florian-lefebvre! - Simplifies path operations ofastro sync#11771
49650a4Thanks @florian-lefebvre! - Fixes an error thrown byastro syncwhen anastro:envvirtual module is imported inside the Content Collections config#11744
b677429Thanks @bluwy! - Disables the WebSocket server when creating a Vite server for loading config filesv4.14.2Compare Source
Patch Changes
391324dThanks @bluwy! - Reverts back toyargs-parserpackage for CLI argument parsingv4.14.1Compare Source
Patch Changes
#11725
6c1560fThanks @ascorbic! - Prevents content layer importing node builtins in runtime#11692
35af73aThanks @matthewp! - Prevent errant HTML from crashing server islandsWhen an HTML minifier strips away the server island comment, the script can't correctly know where the end of the fallback content is. This makes it so that it simply doesn't remove any DOM in that scenario. This means the fallback isn't removed, but it also doesn't crash the browser.
#11727
3c2f93bThanks @florian-lefebvre! - Fixes a type issue when using the Content Layer in devv4.14.0Compare Source
Minor Changes
#11657
a23c69dThanks @bluwy! - Deprecates the option for route-generating files to export a dynamic value forprerender. Only static values are now supported (e.g.export const prerender = trueor= false). This allows for better treeshaking and bundling configuration in the future.Adds a new
"astro:route:setup"hook to the Integrations API to allow you to dynamically set options for a route at build or request time through an integration, such as enabling on-demand server rendering.To migrate from a dynamic export to the new hook, update or remove any dynamic
prerenderexports from individual routing files:Instead, create an integration with the
"astro:route:setup"hook and update the route'sprerenderoption:#11360
a79a8b0Thanks @ascorbic! - Adds a newinjectTypes()utility to the Integration API and refactors how type generation worksUse
injectTypes()in theastro:config:donehook to inject types into your user's project by adding a new a*.d.tsfile.The
filenameproperty will be used to generate a file at/.astro/integrations/<normalized_integration_name>/<normalized_filename>.d.tsand must end with".d.ts".The
contentproperty will create the body of the file, and must be valid TypeScript.Additionally,
injectTypes()returns a URL to the normalized path so you can overwrite its content later on, or manipulate it in any way you want.Codegen has been refactored. Although
src/env.d.tswill continue to work as is, we recommend you update it:#11605
d3d99fbThanks @jcayzac! - Adds a new propertymetato Astro's built-in<Code />component.This allows you to provide a value for Shiki's
metaattribute to pass options to transformers.The following example passes an option to highlight lines 1 and 3 to Shiki's
tranformerMetaHighlight:#11360
a79a8b0Thanks @ascorbic! - Adds support for Intellisense features (e.g. code completion, quick hints) for your content collection entries in compatible editors under theexperimental.contentIntellisenseflag.When enabled, this feature will generate and add JSON schemas to the
.astrodirectory in your project. These files can be used by the Astro language server to provide Intellisense inside content files (.md,.mdx,.mdoc).Note that at this time, this also require enabling the
astro.content-intellisenseoption in your editor, or passing thecontentIntellisense: trueinitialization parameter to the Astro language server for editors using it directly.See the experimental content Intellisense docs for more information updates as this feature develops.
#11360
a79a8b0Thanks @ascorbic! - Adds experimental support for the Content Layer API.The new Content Layer API builds upon content collections, taking them beyond local files in
src/content/and allowing you to fetch content from anywhere, including remote APIs. These new collections work alongside your existing content collections, and you can migrate them to the new API at your own pace. There are significant improvements to performance with large collections of local files.Getting started
Loading your content
Creating a loader
Sharing your loaders
Learn more
Patch Changes
#11716
f4057c1Thanks @florian-lefebvre! - Fixes content types sync in dev#11645
849e4c6Thanks @bluwy! - Refactors internally to usenode:utilparseArgsinstead ofyargs-parser#11712
791d809Thanks @matthewp! - Fix mixed use of base + trailingSlash in Server Islands#11709
3d8ae76Thanks @matthewp! - Fix adapter causing Netlify to breakv4.13.4Compare Source
Patch Changes
#11678
34da907Thanks @ematipico! - Fixes a case where omitting a semicolon and line ending with carriage return - CRLF - in theprerenderoption could throw an error.#11535
932bd2eThanks @matthewp! - Encrypt server island propsServer island props are now encrypted with a key generated at build-time. This is intended to prevent accidentally leaking secrets caused by exposing secrets through prop-passing. This is not intended to allow a server island to be trusted to skip authentication, or to protect against any other vulnerabilities other than secret leakage.
See the RFC for an explanation: https://github.com/withastro/roadmap/blob/server-islands/proposals/server-islands.md#props-serialization
#11655
dc0a297Thanks @billy-le! - Fixes Astro Actionsinputvalidation when usingdefaultvalues with a form input.#11689
c7bda4cThanks @ematipico! - Fixes an issue in the Astro actions, where the size of the generated cookie was exceeding the size permitted by theSet-Cookieheader.v4.13.3Compare Source
Patch Changes
#11653
32be549Thanks @florian-lefebvre! - Updatesastro:envdocs to reflect current developments and usage guidance#11658
13b912aThanks @bholmesdev! - FixesorThrow()type when calling an Action without aninputvalidator.#11603
f31d466Thanks @bholmesdev! - Improves user experience when render an Action result from a form POST request:?_astroAction=NAMEflag when a result is rendered.Also improves the DX of directing to a new route on success. Actions will now redirect to the route specified in your
actionstring on success, and redirect back to the previous page on error. This follows the routing convention of established backend frameworks like Laravel.For example, say you want to redirect to a
/successroute whenactions.signupsucceeds. You can add/successto youractionstring like so:/success.You can retrieve the action result from either page using the
Astro.getActionResult()function.Note on security
v4.13.2Compare Source
Patch Changes
#11648
589d351Thanks @bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions.#11600
09ec2caThanks @ArmandPhilippot! - DeprecatesgetEntryBySlugandgetDataEntryByIdfunctions exported byastro:contentin favor ofgetEntry.#11593
81d7150Thanks @bholmesdev! - Adds support forDate(),Map(), andSet()from action results. See devalue for a complete list of supported values.Also fixes serialization exceptions when deploying Actions with edge middleware on Netlify and Vercel.
#11617
196092aThanks @abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold.#11634
2716f52Thanks @bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel.#11628
9aaf58cThanks @madbook! - Ensures consistent CSS chunk hashes across different environmentsv4.13.1Compare Source
Patch Changes
#11584
a65ffe3Thanks @bholmesdev! - Removes async local storage dependency from Astro Actions. This allows Actions to run in Cloudflare and Stackblitz without opt-in flags or other configuration.This also introduces a new convention for calling actions from server code. Instead of calling actions directly, you must wrap function calls with the new
Astro.callAction()utility.Migration
v4.13.0Compare Source
Minor Changes
#11507
a62345fThanks @ematipico! - Adds color-coding to the console output during the build to highlight slow pages.Pages that take more than 500 milliseconds to render will have their build time logged in red. This change can help you discover pages of your site that are not performant and may need attention.
#11379
e5e2d3eThanks @alexanderniebuhr! - Theexperimental.contentCollectionJsonSchemafeature introduced behind a flag in v4.5.0 is no longer experimental and is available for general use.If you are working with collections of type
data, Astro will now auto-generate JSON schema files for your editor to get IntelliSense and type-checking. A separate file will be created for each data collection in your project based on your collections defined insrc/content/config.tsusing a library calledzod-to-json-schema.This feature requires you to manually set your schema's file path as the value for
$schemain each data entry file of the collection:Alternatively, you can set this value in your editor settings. For example, to set this value in VSCode's
json.schemassetting, provide the path of files to match and the location of your JSON schema:If you were previously using this feature, please remove the experimental flag from your Astro config:
If you have been waiting for stabilization before using JSON Schema generation for content collections, you can now do so.
Please see the content collections guide for more about this feature.
#11542
45ad326Thanks @ematipico! - Theexperimental.rewritingfeature introduced behind a flag in v4.8.0 is no longer experimental and is available for general use.Astro.rewrite()andcontext.rewrite()allow you to render a different page without changing the URL in the browser. Unlike using a redirect, your visitor is kept on the original page they visited.Rewrites can be useful for showing the same content at multiple paths (e.g. /products/shoes/men/ and /products/men/shoes/) without needing to maintain two identical source files.
Rewrites are supported in Astro pages, endpoints, and middleware.
Return
Astro.rewrite()in the frontmatter of a.astropage component to display a different page's content, such as fallback localized content:Use
context.rewrite()in endpoints, for example to reroute to a different page:The middleware
next()function now accepts a parameter with the same type as therewrite()function. For example, withnext("/"), you can call the next middleware function with a newRequest.If you were previously using this feature, please remove the experimental flag from your Astro config:
If you have been waiting for stabilization before using rewrites in Astro, you can now do so.
Please see the routing guide in docs for more about using this feature.
v4.12.3Compare Source
Patch Changes
#11509
dfbca06Thanks @bluwy! - Excludes hoisted scripts and styles from Astro components imported with?urlor?raw#11561
904f1e5Thanks @ArmandPhilippot! - Uses the correct pageSize default inpage.sizeJSDoc comment#11571
1c3265aThanks @bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest@astrojs/reactintegration as well if you're using React 19 features.Make
.safe()the default return value for actions. This means{ data, error }will be returned when calling an action directly. If you prefer to get the data while allowing errors to throw, chain the.orThrow()modifier.Migration
#11546
7f26de9Thanks @ArmandPhilippot! - Remove "SSR Only" mention inAstro.redirectinline documentation and update reference link.#11525
8068131Thanks @ematipico! - Fixes a case where the build was failing whenexperimental.actionswas enabled, an adapter was in use, and there were not actions inside the user code base.#11574
e3f29d4Thanks @Princesseuh! - Fixes line with the error not being properly highlighted in the error overlay#11570
84189b6Thanks @bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest@astrojs/reactintegration as well if you're using React 19 features.Updates the Astro Actions fallback to support
action={actions.name}instead of usinggetActionProps().This will submit a form to the server in zero-JS scenarios using a search parameter:You may also construct form action URLs using string concatenation, or by using the
URL()constructor, with the an action's.queryStringproperty:Migration
#11559
1953dbbThanks @bryanwood! - Allows actions to return falsy values without an error#11553
02c85b5Thanks @ematipico! - Fixes an issue in content collection caching, where two documents with the same contents were generating an error during the build.#11548
602c5bfThanks @TheOtterlord! - Fixesastro addfor packages with only prerelease versions#11566
0dcef3aThanks @Princesseuh! - Fixes DomException errors not being handled properly#11529
504c383Thanks @matthewp! - Fix server islands with trailingSlash: alwaysv4.12.2Compare Source
Patch Changes
#11505
8ff7658Thanks @ematipico! - Enhances the dev server logging when rewrites occur during the lifecycle or rendering.The dev server will log the status code before and after a rewrite:
#11506
026e8baThanks @sarah11918! - Fixes typo in documenting theslot="fallback"attribute for Server Islands experimental feature.#11508
ca335e1Thanks @cramforce! - Escapes HTML in serialized props#11501
4db78aeThanks @martrapp! - Adds the missing export for accessing thegetFallback()function of the client site router.v4.12.1Compare Source
Patch Changes
#11486
9c0c849Thanks @ematipico! - Adds a new function calledaddClientRendererto the Container API.This function should be used when rendering components using the
client:*directives. TheaddClientRendererAPI must be usedafter the use of the
addServerRenderer:#11500
4e142d3Thanks @Princesseuh! - Fixes inferRemoteSize type not working#11496
53ccd20Thanks @alfawal! - Hide the dev toolbar onwindow.print()(CTRL + P)v4.12.0Compare Source
Minor Changes
#11341
49b5145Thanks @madcampos! - Adds support for Shiki'sdefaultColoroption.This option allows you to override the values of a theme's inline style, adding only CSS variables to give you more flexibility in applying multiple color themes.
Configure
defaultColor: falsein your Shiki config to apply throughout your site, or pass to Astro's built-in<Code>component to style an individual code block.#11304
2e70741Thanks @Fryuni! - Refactors the type for integration hooks so that integration authors writing custom integration hooks can now allow runtime interactions between their integration and other integrations.This internal change should not break existing code for integration authors.
To declare your own hooks for your integration, extend the
Astro.IntegrationHooksinterface:Call your hooks on all other integrations installed in a project at the appropriate time. For example, you can call your hook on initialization before either the Vite or Astro config have resolved:
Other integrations can also now declare your hooks:
#11305
d495df5Thanks @matthewp! - Experimental Server IslandsServer Islands allow you to specify components that should run on the server, allowing the rest of the page to be more aggressively cached, or even generated statically. Turn any
.astrocomponent into a server island by adding theserver:deferdirective and optionally, fallback placeholder content:The
server:deferdirective can be used on any Astro component in a project usinghybridorservermode with an adapter. There are no special APIs needed inside of the island.Enable server islands by adding the experimental flag to your Astro config with an appropriate
outputmode and adatper:For more information, see the server islands documentation.
#11482
7c9ed71Thanks @Princesseuh! - Adds a--noSyncparameter to theastro checkcommand to skip the type-gen step. This can be useful when runningastro checkinside packages that have Astro components, but are not Astro projects#11098
36e30a3Thanks @itsmatteomanf! - Adds a newinferRemoteSize()function that can be used to infer the dimensions of a remote image.Previously, the ability to infer these values was only available by adding the [
inferSize] attribute to the<Image>and<Picture>components orgetImage(). Now, you can also access this data outside of these components.This is useful for when you need to know the dimensions of an image for styling purposes or to calculate different densities for responsive images.
#11391
6f9b527Thanks @ARipeAppleByYoursTruly! - Adds Shiki'sdefaultColoroption to the<Code />component, giving you more control in applying multiple themes#11176
a751458Thanks @tsawada! - Adds two new values to the paginationpageprop:page.firstandpage.lastfor accessing the URLs of the first and last pages.Patch Changes
#11477
7e9c4a1Thanks @ematipico! - Fixes an issue where the development server was emitting a 404 status code when the user uses a rewrite that emits a 200 status code.#11479
ca969d5Thanks @florian-lefebvre! - Fixes a case where invalidastro:envvariables at runtime would not throw correctly#11489
061f1f4Thanks @ematipico! - Move root inside the manifest and make serialisable#11415
e9334d0Thanks @florian-lefebvre! - Refactors howsyncworks and when it's called. Fixes an issue withastro:envtypes in dev not being generated#11478
3161b67Thanks @bluwy! - Supports importing Astro components with Vite queries, like?url,?raw, and?direct#11491
fe3afebThanks @matthewp! - Fix for Server Islands in Vercel adapterVercel, and probably other adapters only allow pre-defined routes. This makes it so that the
astro:build:donehook includes the_server-islands/route as part of the route data, which is used to configure available routes.#11483
34f9c25Thanks @Princesseuh! - Fixes Astro not working on low versions of Node 18 and 20Updated dependencies [
49b5145]:v4.11.6Compare Source
Patch Changes
#11459
bc2e74dThanks @mingjunlu! - Fixes false positive audit warnings on elements with the role "tabpanel".#11472
cb4e6d0Thanks @delucis! - Avoids targeting all files in thesrc/directory for eager optimization by Vite. After this change, only JSX, Vue, Svelte, and Astro components get scanned for early optimization.#11387
b498461Thanks @bluwy! - Fixes prerendering not removing unused dynamic imported chunks#11437
6ccb30eThanks @NuroDev! - Fixes a case where Astro's configexperimental.env.schemakeys did not allow numbers. Numbers are still not allowed as the first character to be able to generate valid JavaScript identifiers#11439
08baf56Thanks @bholmesdev! - Expands theisInputError()utility fromastro:actionsto accept errors of any type. This should now allow type narrowing from a try / catch block.#11452
0e66849Thanks @FugiTech! - Fixes an issue where using .nullish() in a formdata Astro action would always parse as a string#11438
619f07dThanks @bholmesdev! - Exposes utility types fromastro:actionsfor thedefineActionhandler (ActionHandler) and theActionErrorcode (ActionErrorCode).#11456
17e048dThanks @RickyC0626! - Fixesastro dev --openunexpected behavior that spawns a new tab every time a config file is saved#11337
0a4b31fThanks @florian-lefebvre! - Adds a new propertyexperimental.env.validateSecretsto allow validating private variables on the server.By default, this is set to
falseand only public variables are checked on start. If enabled, secrets will also be checked on start (dev/build modes). This is useful for example in some CIs to make sure all your secrets are correctly set before deploying.#11443
ea4bc04Thanks @bholmesdev! - Expose newActionReturnTypeutility fromastro:actions. This infers the return type of an action by passingtypeof actions.nameas a type argument. This example defines alikeaction that returnslikesas an object:In your client code, you can infer this handler return value with
ActionReturnType:#11436
7dca68fThanks @bholmesdev! - Fixesastro:actionsautocompletion for thedefineActionacceptproperty#11455
645e128Thanks @florian-lefebvre! - Improvesastro:envinvalid variables errorsv4.11.5Compare Source
Patch Changes
b9e906fThanks @matthewp! - Revert change to how boolean attributes workv4.11.4Compare Source
Patch Changes
#11362
93993b7Thanks @ematipico! - Fixes an issue where creating manually the i18n middleware could break the logic of the functions of the virtual moduleastro:i18n#11349
98d9ce4Thanks @ematipico! - Fixes an issue where Astro didn't throw an error whenAstro.rewritewas used without providing the experimental flag#11352
a55ee02Thanks @ematipico! - Fixes an issue where the rewrites didn't update the status code when using manual i18n routing.#11388
3a223b4Thanks @mingjunlu! - Adjusts the color of punctuations in error overlay.#11369
e6de11fThanks @bluwy! - Fixes attribute rendering for non-boolean attributes with boolean valuesv4.11.3Compare Source
Patch Changes
#11347
33bdc54Thanks @bluwy! - Fixes installed packages detection when runningastro check#11327
0df8142Thanks @ematipico! - Fixes an issue with the container APIs where a runtime error was thrown during the build, when usingpnpmas package manager.v4.11.2Compare Source
Patch Changes
#11335
4c4741bThanks @ematipico! - Reverts #11292, which caused a regression to the input type#11326
41121fbThanks @florian-lefebvre! - Fixes a case where runningastro syncwhen using the experimentalastro:envfeature would fail if environment variables were missing#11338
9752a0bThanks @zaaakher! - Fixes svg icon margin in devtool tooltip title to look coherent inrtlandltrlayouts#11331
f1b78a4Thanks @bluwy! - Removesresolvepackage and simplify internal resolve check#11339
8fdbf0eThanks @matthewp! - Remove non-fatal errors from telemetryPreviously we tracked non-fatal errors in telemetry to get a good idea of the types of errors that occur in
astro dev. However this has become noisy over time and results in a lot of data that isn't particularly useful. This removes those non-fatal errors from being tracked.v4.11.1Compare Source
Patch Changes
#11308
44c61ddThanks @ematipico! - Fixes an issue where custom404.astroand500.astrowere not returning the correct status code when rendered inside a rewriting cycle.#11302
0622567Thanks @martrapp! - Fixes an issue with the view transition router when redirecting to an URL with different origin.Updated dependencies [
b6afe6a,41064ce]:v4.11.0Compare Source
Minor Changes
#11197
4b46bd9Thanks @braebo! - AddsShikiTransformersupport to the<Code />component with a newtransformersprop.Note that
transformersonly applies classes and you must provide your own CSS rules to target the elements of your code block.#11134
9042be0Thanks @florian-lefebvre! - Improves the developer experience of the500.astrofile by passing it a newerrorprop.When an error is thrown, the special
src/pages/500.astropage now automatically receives the error as a prop. This allows you to display more specific information about the error on a custom 500 page.If an error occurs rendering this page, your host's default 500 error page will be shown to your visitor in production, and Astro's default error overlay will be shown in development.
Patch Changes
#11280
fd3645fThanks @ascorbic! - Fixes a bug that prevented cookies from being set when using experimental rewrites#11275
bab700dThanks @syhily! - Drop duplicated brackets in data collections schema generation.#11272
ea987d7Thanks @ematipico! - Fixes a case where rewriting/would cause an issue, whentrailingSlashwas set to"never".#11272
ea987d7Thanks @ematipico! - Reverts a logic where it wasn't possible to rewrite/404in static mode. It's now possible again#11264
5a9c9a6Thanks @Fryuni! - Fixes type generation for empty content collections#11279
9a08d74Thanks @ascorbic! - Improves type-checking and error handling to catch case where an image import is passed directly togetImage()#11292
7f8f347Thanks @jdtjenkins! - Fixes a case wheredefineActionautocomplete for theacceptprop would not show"form"as a possible value#11273
cb4d078Thanks @ascorbic! - Corrects an inconsistency in dev where middleware would run for prerendered 404 routes.Middleware is not run for prerendered 404 routes in production, so this was incorrect.
#11284
f4b029bThanks @ascorbic! - Fixes an issue that would breakAstro.request.urlandAstro.request.headersinastro devif HTTP/2 was enabled.HTTP/2 is now enabled by default in
astro devifhttpsis configured in the Vite config.v4.10.3Compare Source
Patch Changes
#11213
94ac7efThanks @florian-lefebvre! - Removes thePUBLIC_prefix constraint forastro:envpublic variables#11213
94ac7efThanks @florian-lefebvre! - BREAKING CHANGE to the experimentalastro:envfeature onlyServer secrets specified in the schema must now be imported from
astro:env/server. UsinggetSecret()is no longer required to use these environment variables in your schema:Note that using
getSecret()with these keys is still possible, but no longer involves any special handling and the raw value will be returned, just like retrieving secrets not specified in your schema.#11234
4385bf7Thanks @ematipico! - Adds a new function calledaddServerRendererto the Container API. Use this function to manually store renderers inside the instance of your container.This new function should be preferred when using the Container API in environments like on-demand pages:
#11249
de60c69Thanks @markgaze! - Fixes a performance issue with JSON schema generation#11242
e4fc2a0Thanks @ematipico! - Fixes a case where the virtual moduleastro:containerwasn't resolved#11236
39bc3a5Thanks @ascorbic! - Fixes a case where symlinked content collection directories were not correctly resolved#11258
d996db6Thanks @ascorbic! - Adds a new errorRewriteWithBodyUsedthat throws whenAstro.rewriteis used after the request body has already been read.#11243
ba2b14cThanks @V3RON! - Fixes a prerendering issue for libraries innode_moduleswhen a folder with an underscore is in the path.#11244
d07d2f7Thanks @ematipico! - Improves the developer experience of the custom500.astropage in development mode.Before, in development, an error thrown during the rendering phase would display the default error overlay, even when users had the
500.astropage.Now, the development server will display the
500.astroand the original error is logged in the console.#11240
2851b0aThanks @ascorbic! - Ignores query strings in module identifiers when matching ".astro" file extensions in Vite plugin#11245
e22be22Thanks @bluwy! - Refactors prerendering chunk handling to correctly remove unused code during the SSR runtimev4.10.2Compare Source
Patch Changes
#11231
58d7dbbThanks @ematipico! - Fixes a regression forgetViteConfig, where the inline config wasn't merged in the final config.#11228
1e293a1Thanks @ascorbic! - UpdatesgetCollection()to always return a cloned array#11207
7d9aac3Thanks @ematipico! - Fixes an issue in the rewriting logic where old data was not purged during the rewrite flow. This caused some false positives when checking the validity of URL path names during the rendering phase.#11189
75a8fe7Thanks @ematipico! - Improve error message when usinggetLocaleByPathon path that doesn't contain any locales.#11195
0a6ab6fThanks @florian-lefebvre! - Adds support for enums toastro:envYou can now call
envField.enum:#11210
66fc028Thanks @matthewp! - Close the iterator only after rendering is complete#11195
0a6ab6fThanks @florian-lefebvre! - Adds additional validation options toastro:envastro:envschema datatypesstringandnumbernow have new optional validation rules:#11211
97724daThanks @matthewp! - Let middleware handle the original request URL#10607
7327c6aThanks @frankbits! - Fixes an issue where a leading slash created incorrect conflict resolution between pages generated from static routes and catch-all dynamic routesv4.10.1Compare Source
Patch Changes
#11198
8b9a499Thanks @florian-lefebvre! - Fixes a case whereastro:envgetSecretwould not retrieve environment variables properly in dev and build modes#11206
734b98fThanks @florian-lefebvre! - BREAKING CHANGE to the experimentalastro:envfeature onlyUpdates the adapter
astro:enventrypoint fromastro:env/setuptoastro/env/setup#11205
8c45391Thanks @Nin3lee! - Fixes a typo in the config referencev4.10.0Compare Source
Minor Changes
#10974
2668ef9Thanks @florian-lefebvre! - Adds experimental support for theastro:envAPI.The
astro:envAPI lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate/clientor/servermodule:To define the data type and properties of your environment variables, declare a schema in your Astro config in
experimental.env.schema. TheenvFieldhelper allows you define your variable as a string, number, or boolean and pass properties in an object:There are three kinds of environment variables, determined by the combination of
context(clientorserver) andaccess(privateorpublic) settings defined in yourenv.schema:Public client variables: These variables end up in both your final client and server bundles, and can be accessed from both client and server through the
astro:env/clientmodule:Public server variables: These variables end up in your final server bundle and can be accessed on the server through the
astro:env/servermodule:Secret server variables: These variables are not part of your final bundle and can be accessed on the server through the
getSecret()helper function available from theastro:env/servermodule:Note: Secret client variables are not supported because there is no safe way to send this data to the client. Therefore, it is not possible to configure both
context: "client"andaccess: "secret"in your schema.To learn more, check out the documentation.
Patch Changes
#11192
58b10a0Thanks @liruifengv! - Improves DX by throwing the originalAstroUserErrorwhen an error is thrown inside a.mdxfile.#11136
35ef53cThanks @ematipico! - Errors that are emitted during a rewrite are now bubbled up and shown to the user. A 404 response is not returned anymore.#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.#11144
803dd80Thanks @ematipico! - BREAKING CHANGE to the experimental Container API onlyChanges the type of the
renderersoption of theAstroContainer::createfunction and adds a dedicated functionloadRenderers()to load the rendering scripts from renderer integration packages (@astrojs/react,@astrojs/preact,@astrojs/solid-js,@astrojs/svelte,@astrojs/vue,@astrojs/lit, and@astrojs/mdx).You no longer need to know the individual, direct file paths to the client and server rendering scripts for each renderer integration package. Now, there is a dedicated function to load the renderer from each package, which is available from
getContainerRenderer():The new
loadRenderers()helper function is available fromastro:container, a virtual module that can be used when running the Astro container insidevite.#11136
35ef53cThanks @ematipico! - It's not possible anymore to useAstro.rewrite("/404")inside static pages. This isn't counterproductive because Astro will end-up emitting a page that contains the HTML of 404 error page.It's still possible to use
Astro.rewrite("/404")inside on-demand pages, or pages that opt-out from prerendering.#11191
6e29a17Thanks @matthewp! - Fixes a case whereAstro.urlwould be incorrect when havingbuild.formatset to'preserve'in the Astro config#11182
40b0b4dThanks @ematipico! - Fixes an issue whereAstro.rewritewasn't carrying over the body of aRequestin on-demand pages.#11194
97fbe93Thanks @ematipico! - Fixes an issue where the functiongetViteConfigwasn't returning the correct merged Astro configurationv4.9.3Compare Source
Patch Changes
#11171
ff8004fThanks @Princesseuh! - Guard globalThis.astroAsset usage in proxy code to avoid errors in wonky situations#11178
1734c49Thanks @theoephraim! - ImprovesisPromiseutility to check the presence ofthenon an object before trying to access it - which can cause undesired side-effects on Proxy objects#11183
3cfa2acThanks @66Leo66! - Suggestpnpm dlxinstead ofpnpxin update check.#11147
2d93902Thanks @kitschpatrol! - Fixes invalid MIME types in Picture source elements for jpg and svg extensions, which was preventing otherwise valid source variations from being shown by the browser#11141
19df89fThanks @ematipico! - Fixes an internal error that prevented theAstroContainerto render theContentcomponent.You can now write code similar to the following to render content collections:
#11170
ba20c71Thanks @matthewp! - Retain client scripts in content cachev4.9.2Compare Source
Patch Changes
#11138
98e0372Thanks @ematipico! - You can now passpropswhen rendering a component using the Container APIs:v4.9.1Compare Source
Patch Changes
4bb9269Thanks @matthewp! - Prevent errors from adapters when i18n domains is not usedv4.9.0Compare Source
Minor Changes
#11051
12a1bccThanks @ematipico! - Introduces an experimental Container API to render.astrocomponents in isolation.This API introduces three new functions to allow you to create a new container and render an Astro component returning either a string or a Response:
create(): creates a new instance of the container.renderToString(): renders a component and return a string.renderToResponse(): renders a component and returns theResponseemitted by the rendering phase.The first supported use of this new API is to enable unit testing. For example, with
vitest, you can create a container to render your component with test data and check the result:For a complete reference, see the Container API docs.
For a feature overview, and to give feedback on this experimental API, see the Container API roadmap discussion.
#11021
2d4c8faThanks @ematipico! - The CSRF protection feature that was introduced behind a flag in v4.6.0 is no longer experimental and is available for general use.To enable the stable version, add the new top-level
securityoption inastro.config.mjs. If you were previously using the experimental version of this feature, also delete the experimental flag:Enabling this setting performs a check that the
"origin"header, automatically passed by all modern browsers, matches the URL sent by each Request.This check is executed only for pages rendered on demand, and only for the requests
POST,PATCH,DELETEandPUTwith one of the following"content-type"headers:'application/x-www-form-urlencoded','multipart/form-data','text/plain'.If the
"origin"header doesn't match the pathname of the request, Astro will return a 403 status code and won't render the page.For more information, see the
securityconfiguration docs.#11022
be68ab4Thanks @ematipico! - Thei18nDomainsrouting feature introduced behind a flag in v3.4.0 is no longer experimental and is available for general use.This routing option allows you to configure different domains for individual locales in entirely server-rendered projects using the @astrojs/node or @astrojs/vercel adapter with a
siteconfigured.If you were using this feature, please remove the experimental flag from your Astro config:
If you have been waiting for stabilization before using this routing option, you can now do so.
Please see the internationalization docs for more about this feature.
#11071
8ca7c73Thanks @bholmesdev! - Adds two new functionsexperimental_getActionState()andexperimental_withState()to support the React 19useActionState()hook when using Astro Actions. This introduces progressive enhancement when calling an Action with thewithState()utility.This example calls a
likeaction that accepts apostIdand returns the number of likes. Pass this action to theexperimental_withState()function to apply progressive enhancement info, and apply touseActionState()to track the result:You can also access the state stored by
useActionState()from your actionhandler. Callexperimental_getActionState()with the API context, and optionally apply a type to the result:#11101
a6916e4Thanks @linguofeng! - Updates Astro's code for adapters to use the headerx-forwarded-forto initialize theclientAddress.To take advantage of the new change, integration authors must upgrade the version of Astro in their adapter
peerDependenciesto4.9.0.#11071
8ca7c73Thanks @bholmesdev! - Adds compatibility for Astro Actions in the React 19 beta. Actions can be passed to aform actionprop directly, and Astro will automatically add metadata for progressive enhancement.Patch Changes
#11088
9566fa0Thanks @bholmesdev! - Allow actions to be called on the server. This allows you to call actions as utility functions in your Astro frontmatter, endpoints, and server-side UI components.Import and call directly from
astro:actionsas you would for client actions:#11112
29a8650Thanks @bholmesdev! - Deprecate thegetApiContext()function. API Context can now be accessed from the second parameter to your Actionhandler():v4.8.7Compare Source
Patch Changes
#11073
f5c8feeThanks @matthewp! - Prevent cache content from being left in dist folderWhen
contentCollectionsCacheis enabled temporary cached content is copied into theoutDirfor processing. This fixes it so that this content is cleaned out, along with the rest of the temporary build JS.#11054
f6b171eThanks @bholmesdev! - Respect error status when handling Actions with a progressive fallback.#11092
bfe9c73Thanks @duckycoding-dev! - Changeslotattribute ofIntrinsicAttributesto match the definition ofHTMLAttributes's ownslotattribute of typestring | undefined | null#10875
b5f95b2Thanks @W1M0R! - Fixes a typo in a JSDoc annotation#11111
a5d79ddThanks @bholmesdev! - Fix unexpectedheaderswarning on prerendered routes when using Astro Actions.#11081
af42e05Thanks @V3RON! - Correctly position inspection tooltip in RTL modeWhen RTL mode is turned on, the inspection tooltip tend to overflow the window on the left side.
Additional check has been added to prevent that.
v4.8.6Compare Source
Patch Changes
9637014Thanks @bluwy! - Fixes regression when handling hoisted scripts from content collectionsv4.8.5Compare Source
Patch Changes
#11065
1f988edThanks @ematipico! - Fixes a bug in the Astro rewrite logic, where rewriting the index with parameters -next("/?foo=bar")- didn't work as expected.#10924
3a0c02aThanks @Its-Just-Nans! - Handle image-size errors by displaying a clearer message#11058
749a7acThanks @matthewp! - Fix streaming in Node.js fast path#11052
a05ca38Thanks @florian-lefebvre! - Fixes a case where rewriting would conflict with the actions internal middleware#11062
16f12e4Thanks @ematipico! - Fixes a bug whereastro builddidn't create custom404.htmland500.htmlwhen a certain combination of i18n options was applied#10965
a8f0372Thanks @Elias-Chairi! - Update generator.ts to allow %23 (#) in dynamic urls#11069
240a70aThanks @ematipico! - Improves debug logging for on-demand pagesv4.8.4Compare Source
Patch Changes
#11026
8dfb1a2Thanks @bluwy! - Skips rendering script tags if it's inlined and empty whenexperimental.directRenderScriptis enabled#11043
d0d1710Thanks @bholmesdev! - Fixes minor type issues in actions component example#10999
5f353e3Thanks @bluwy! - The prefetch feature is updated to better support different browsers and different cache headers setup, including:<link rel="prefetch">if supported, or will fall back tofetch().prefetch()programmatic API'swithoption is deprecated in favour of an automatic approach that will also try to use<link rel="prefetch>if supported, or will fall back tofetch().This change shouldn't affect most sites and should instead make prefetching more effective.
#11041
6cc3fb9Thanks @bholmesdev! - Fixes 500 errors when sending empty params or returning an empty response from an action.#11028
771d1f7Thanks @bholmesdev! - Throw on missing server output when using Astro Actions.#11029
bd34452Thanks @bholmesdev! - Actions: include validation error in thrown error message for debugging.#11046
086694aThanks @HiDeoo! - FixesgetViteConfig()type definition to allow passing an inline Astro configuration as second argument#11026
8dfb1a2Thanks @bluwy! - Fixes CSS handling if imported in a script tag in an Astro file whenexperimental.directRenderScriptis enabled#11020
2e2d6b7Thanks @xsynaptic! - Add type declarations forimport.meta.env.ASSETS_PREFIXwhen defined as an object for handling different file types.#11030
18e7f33Thanks @bholmesdev! - Actions: Fix missing message for custom Action errors.#10981
ad9227cThanks @mo! - Adds deprecated HTML attribute "name" to the list of valid attributes. This attribute has been replaced by the globalidattribute in recent versions of HTML.#11013
4ea38e7Thanks @QingXia-Ela! - Prevents unhandledrejection error when checking for latest Astro version#11034
5f2dd45Thanks @arganaphang! - Addpopovertargetactionto the attribute that can be passed to thebuttonandinputelementv4.8.3Compare Source
Patch Changes
7418bb0Thanks @bholmesdev! - Fixlocalsaccess from action handlersv4.8.2Compare Source
Patch Changes
#10990
4161a2aThanks @liruifengv! - fix incorrect actions path on windows#10979
6fa89e8Thanks @BryceRussell! - Fix loading of non-index routes that end withindex.htmlv4.8.1Compare Source
Patch Changes
#10987
05db5f7Thanks @ematipico! - Fix a regression where the flagexperimental.rewritingwas marked mandatory. Is is now optional.#10975
6b640b3Thanks @bluwy! - Passes the scoped style attribute or class to the<picture>element in the<Picture />component so scoped styling can be applied to the<picture>elementv4.8.0Compare Source
Minor Changes
#10935
ddd8e49Thanks @bluwy! - Exportsastro/jsx/rehype.jswith utilities to generate an Astro metadata object#10625
698c2d9Thanks @goulvenclech! - Adds the ability for multiple pages to use the same component as anentrypointwhen building an Astro integration. This change is purely internal, and aligns the build process with the behaviour in the development server.#10906
7bbd664Thanks @Princesseuh! - Adds a new radio checkbox component to the dev toolbar UI library (astro-dev-toolbar-radio-checkbox)#10963
61f47a6Thanks @delucis! - Adds support for passing an inline Astro configuration object togetViteConfig()If you are using
getViteConfig()to configure the Vitest test runner, you can now pass a second argument to control how Astro is configured. This makes it possible to configure unit tests with different Astro options when using Vitest’s workspaces feature.#10867
47877a7Thanks @ematipico! - Adds experimental rewriting in Astro with a newrewrite()function and the middlewarenext()function.The feature is available via an experimental flag in
astro.config.mjs:When enabled, you can use
rewrite()to render another page without changing the URL of the browser in Astro pages and endpoints.The middleware
next()function now accepts a parameter with the same type as therewrite()function. For example, withnext("/"), you can call the next middleware function with a newRequest.#10858
c0c509bThanks @bholmesdev! - Adds experimental support for the Actions API. Actions let you define type-safe endpoints you can query from client components with progressive enhancement built in.Actions help you write type-safe backend functions you can call from anywhere. Enable server rendering using the
outputproperty and add theactionsflag to theexperimentalobject:Declare all your actions in
src/actions/index.ts. This file is the global actions handler.Define an action using the
defineAction()utility from theastro:actionsmodule. These accept thehandlerproperty to define your server-side request handler. If your action accepts arguments, apply theinputproperty to validate parameters with Zod.This example defines two actions:
likeandcomment. Thelikeaction accepts a JSON object with apostIdstring, while thecommentaction accepts FormData withpostId,author, andbodystrings. Eachhandlerupdates your database and return a type-safe response.Then, call an action from your client components using the
actionsobject fromastro:actions. You can pass a type-safe object when using JSON, or a FormData object when usingaccept: 'form'in your action definition:For a complete overview, and to give feedback on this experimental API, see the Actions RFC.
#10906
7bbd664Thanks @Princesseuh! - Adds a newbuttonBorderRadiusproperty to theastro-dev-toolbar-buttoncomponent for the dev toolbar component library. This property can be useful to make a fully rounded button with an icon in the center.Patch Changes
#10977
59571e8Thanks @BryceRussell! - Improve error message when accessingclientAddresson prerendered routes#10935
ddd8e49Thanks @bluwy! - Improves the error message when failed to render MDX components#10917
3412535Thanks @jakobhellermann! - Fixes a case where the local server would crash when the host also contained the port, eg. withX-Forwarded-Host: hostname:8080andX-Forwarded-Port: 8080headers#10959
685fc22Thanks @bluwy! - Refactors internal handling of styles and scripts for content collections to improve build performance#10889
4d905ccThanks @matthewp! - Preserve content modules properly in cache#10955
2978287Thanks @florian-lefebvre! - HandlesAstroUserErrors thrown while syncing content collections and exportsBaseSchemaandCollectionConfigtypesv4.7.1Compare Source
Patch Changes
#10911
a86dc9dThanks @bluwy! - Skips adding CSS dependencies of CSS Vite modules as style tags in the HTML#10900
36bb3b6Thanks @martrapp! - Detects overlapping navigation and view transitions and automatically aborts all but the most recent one.#10933
007d17fThanks @Princesseuh! - Fixesapp.toggleStatenot working correctly#10931
4ce5cedThanks @ktym4a! - FixestoggleNotification()'s parameter type for the notification level not using the proper levelsv4.7.0Compare Source
Minor Changes
#10665
7b4f284Thanks @Princesseuh! - Adds new utilities to ease the creation of toolbar apps includingdefineToolbarAppto make it easier to define your toolbar app andappandserverhelpers for easier communication between the toolbar and the server. These new utilities abstract away some of the boilerplate code that is common in toolbar apps, and lower the barrier of entry for app authors.For example, instead of creating an event listener for the
app-toggledevent and manually typing the value in the callback, you can now use theonAppToggledmethod. Additionally, communicating with the server does not require knowing any of the Vite APIs anymore, as a newserverobject is passed to theinitfunction that contains easy to use methods for communicating with the server.Server helpers are also available on the server side, for use in your integrations, through the new
toolbarobject:This is a backwards compatible change and your your existing dev toolbar apps will continue to function. However, we encourage you to build your apps with the new helpers, following the updated Dev Toolbar API documentation.
#10734
6fc4c0eThanks @Princesseuh! - Astro will now automatically check for updates when you run the dev server. If a new version is available, a message will appear in the terminal with instructions on how to update. Updates will be checked once per 10 days, and the message will only appear if the project is multiple versions behind the latest release.This behavior can be disabled by running
astro preferences disable checkUpdatesor setting theASTRO_DISABLE_UPDATE_CHECKenvironment variable tofalse.#10762
43ead8fThanks @bholmesdev! - Enables type checking for JavaScript files when using thestrictestTS config. This ensures consistency with Astro's other TS configs, and fixes type checking for integrations like Astro DB when using anastro.config.mjs.If you are currently using the
strictestpreset and would like to still disable.jsfiles, setallowJS: falsein yourtsconfig.json.Patch Changes
#10861
b673bc8Thanks @mingjunlu! - Fixes an issue whereastro buildwrites type declaration files tooutDirwhen it's outside of root directory.#10684
8b59d5dThanks @PeterDraex! - Update sharp to 0.33 to fix issue with Alpine Linuxv4.6.4Compare Source
Patch Changes
#10846
3294f7aThanks @matthewp! - Prevent getCollection breaking in vitest#10856
30cf82aThanks @robertvanhoesel! - Prevents inputs with a name attribute of action or method to break ViewTransitions' form submission#10833
8d5f3e8Thanks @renovate! - Updatesesbuilddependency to v0.20. This should not affect projects in most cases.#10801
204b782Thanks @rishi-raj-jain! - Fixes an issue where images in MD required a relative specifier (e.g../)Now, you can use the standard
syntax in MD files for images colocated in the same folder: no relative specifier required!There is no need to update your project; your existing images will still continue to work. However, you may wish to remove any relative specifiers from these MD images as they are no longer necessary:
#10841
a2df344Thanks @martrapp! - Due to regression on mobile WebKit browsers, reverts a change made for JavaScript animations during view transitions.v4.6.3Compare Source
Patch Changes
#10799
dc74afca9f5eebc2d61331298d6ef187d92051e0Thanks @martrapp! - Fixes an issue with persisted non-text input fields that have the focus during view transition navigation.#10773
35e43ecdaae7adc4b9a0b974192a033568cfb3f0Thanks @lilnasy! - Improves performance for frequent use of small components.#10763
63132771373ce1510be3e8814897accc0bf62ef8Thanks @matthewp! - Invalidate CC cache manifest when lockfile or config changes#10811
77822a822b04b5113726f713df104e8667333c59Thanks @AvinashReddy3108! - Update list of available integrations in theastro addCLI help.v4.6.2Compare Source
Patch Changes
#10732
a92e263beb6e0166f1f13c97803d1861793e2a99Thanks @rishi-raj-jain! - Correctly setsbuild.assetsdirectory duringviteconfig setup#10776
1607face67051b16d4648555f1001b2a9308e377Thanks @fshafiee! - Fixes cookies type inference#10796
90669472df3a05b33f0de46fd2d039e3eba7f7ddThanks @bluwy! - Disables streaming when rendering site withoutput: "static"#10782
b0589d05538fcc77dd3c38198bf93f3548362cd8Thanks @nektro! - Handles possible null value when callingwhich-pmduring dynamic package installation#10774
308b5d8c122f44e7724bb2f3ad3aa5c43a83e584Thanks @Princesseuh! - Fixesastro addsometimes modifyingbaseUrlunintentionally#10783
4dbd545304d1a8af903c8c97f237eb55c988c40bThanks @jurajkapsz! - Fixes Picture component specialFormatsFallback fallback check#10775
06843121450899ecf0390ca4efaff6c9a6fe0f75Thanks @Princesseuh! - Fixes assets endpoint in serverless returning 404 in certain situations where the website might be under a protected route#10787
699f4559a279b374bddb3e5e48c72afe2709e8e7Thanks @martrapp! - Fixes a timing issue in the view transition simulation.v4.6.1Compare Source
Patch Changes
#10708
742866c5669a2be4f8b5a4c861cadb933c381415Thanks @horo-fox! - Limits parallel imports withingetCollection()to prevent EMFILE errors when accessing files#10755
c6d59b6fb7db20af957a8706c8159c50619235efThanks @ematipico! - Fixes a case where the i18n fallback failed to correctly redirect to the index page with SSR enabledv4.6.0Compare Source
Minor Changes
#10591
39988ef8e2c4c4888543c973e06d9b9939e4ac95Thanks @mingjunlu! - Adds a new dev toolbar settings option to change the horizontal placement of the dev toolbar on your screen: bottom left, bottom center, or bottom right.#10689
683d51a5eecafbbfbfed3910a3f1fbf0b3531b99Thanks @ematipico! - Deprecate support for versions of Node.js older thanv18.17.1for Node.js 18, older thanv20.0.3for Node.js 20, and the complete Node.js v19 release line.This change is in line with Astro's Node.js support policy.
#10678
2e53b5fff6d292b7acdf8c30a6ecf5e5696846a1Thanks @ematipico! - Adds a new experimental security option to prevent Cross-Site Request Forgery (CSRF) attacks. This feature is available only for pages rendered on demand:Enabling this setting performs a check that the "origin" header, automatically passed by all modern browsers, matches the URL sent by each
Request.This experimental "origin" check is executed only for pages rendered on demand, and only for the requests
POST,PATCH,DELETEandPUTwith one of the followingcontent-type` headers: 'application/x-www-form-urlencoded', 'multipart/form-data', 'text/plain'.It the "origin" header doesn't match the pathname of the request, Astro will return a 403 status code and won't render the page.
#10193
440681e7b74511a17b152af0fd6e0e4dc4014025Thanks @ematipico! - Adds a new i18n routing optionmanualto allow you to write your own i18n middleware:Adding
routing: "manual"to your i18n config disables Astro's own i18n middleware and provides you with helper functions to write your own:redirectToDefaultLocale,notFound, andredirectToFallback:Also adds a
middlewarefunction that manually creates Astro's i18n middleware. This allows you to extend Astro's i18n routing instead of completely replacing it. Runmiddlewarein combination with your own middleware, using thesequenceutility to determine the order:#10671
9e14a78cb05667af9821948c630786f74680090dThanks @fshafiee! - Adds thehttpOnly,sameSite, andsecureoptions when deleting a cookiePatch Changes
#10747
994337c99f84304df1147a14504659439a9a7326Thanks @lilnasy! - Fixes an issue where functions could not be used as named slots.#10750
7e825604ddf90c989537e07939a39dc249343897Thanks @OliverSpeir! - Fixes a false positive for "Invalidtabindexon non-interactive element" rule for roleless elements (divandspan).#10745
d51951ce6278d4b59deed938d65e1cb72b5102dfThanks @lilnasy! - Fixes an issue where CLI commands could not report the reason for failure before exiting.#10661
e2cd7f4291912dadd4a654bc7917856c58a72a97Thanks @liruifengv! - Fixed errorOverlay theme toggle bug.Updated dependencies [
ccafa8d230f65c9302421a0ce0a0adc5824bfd55,683d51a5eecafbbfbfed3910a3f1fbf0b3531b99]:v4.5.18Compare Source
Patch Changes
#10728
f508c4b7d54316e737f454a3777204b23636d4a0Thanks @ematipico! - Fixes a regression where some very specific code rendered usingexpressive-codewas not escaped properly.#10737
8a30f257b1f3618b01212a591b82ad7a63c82fbbThanks @lilnasy! - Fixes a regression where constructing and returning 404 responses from a middleware resulted in the dev server getting stuck in a loop.#10719
b21b3ba307235510707ee9f5bd49f71473a07004Thanks @ematipico! - Fixes a false positive fordivandspanelements when running the Dev Toolbar accessibility audits.Those are special elements that don't have an interaction assigned by default. Instead, it is assigned through the
roleattribute. This means that cases like the following are now deemed correct:v4.5.17Compare Source
Patch Changes
#10688
799f6f3f29a3ef4f76347870a209ffa89651adfaThanks @bluwy! - Marks rendererjsxImportSourceandjsxTransformOptionsoptions as deprecated as they are no longer used since Astro 3.0#10657
93d353528fa1a85b67e3f1e9514ed2a1b42dfd94Thanks @natemoo-re! - Improves the color contrast for notification badges on dev toolbar apps#10693
1d26e9c7f7d8f47e33bc68d3b30bbffce25c7b63Thanks @apetta! - Adds thedisableremoteplaybackattribute to MediaHTMLAttributes interface#10695
a15975e41cb5eaf6ed8eb3ebaee676a17e433052Thanks @bluwy! - Skips prerender chunk if building with static output#10707
5e044a5eafaa206d2ef8b62c37d1bcd37f0a4078Thanks @horo-fox! - Logs an error when a page'sgetStaticPathsfails#10686
fa0f593890502faf5709ab881fe0e45519d2f7afThanks @bluwy! - Prevents inlining scripts if used by other chunks when using theexperimental.directRenderScriptoptionv4.5.16Compare Source
Patch Changes
#10679
ca6bb1f31ef041e6ccf8ef974856fa945ff5bb31Thanks @martrapp! - Generates missing popstate events for Firefox when navigating to hash targets on the same page.#10669
0464563e527f821e53d78028d9bbf3c4e1050f5bThanks @Princesseuh! - Fixes Astro waiting infinitely in CI when a required package was not installedv4.5.15Compare Source
Patch Changes
#10666
55ddb2ba4889480f776a8d29b9dcd531b9f5ab3eThanks @lilnasy! - Fixes an issue where forwarded requests did not include hostname on node-based adapters. This also makes error pages more reliable.#10642
4f5dc14f315eba7ea6ec5cc8e5dacb0cb81288ddThanks @OliverSpeir! - Fixes typing issues when usingformatandqualityoptions with remote images#10616
317d18ef8c9cf4fd13647518e3fd352774a86481Thanks @NikolaRHristov! - This change disables thesharplibvipsimage cache as it errors when thefile is too small and operations are happening too fast (runs into a race
condition)
v4.5.14Compare Source
Patch Changes
#10470
320c309ca9fbe51c40e6ba846d04a0cb49aced5fThanks @liruifengv! - improvesclient:onlyerror message#10496
ce985631129e49f7ea90e6ea690ef9f9cf0e6987Thanks @florian-lefebvre! - Makes the warning less scary when adding 3rd-party integrations usingastro addv4.5.13Compare Source
Patch Changes
#10495
046d69d517118ab5c0e71604b321729d66ddffffThanks @satyarohith! - This patch allows astro to run in node-compat mode in Deno. Deno doesn't supportconstruction of response from async iterables in node-compat mode so we need to
use ReadableStream.
#10605
a16a829f4e25ad5c9a1b4557ec089fc8ab53320fThanks @martrapp! - Fixes an issue with outdated page titles in browser history when using text fragments in view transition navigation.#10584
e648c5575a8774af739231cfa9fc27a32086aa5fThanks @duanwilliam! - Fixes a bug where JSX runtime would error on components with nullish prop values in certain conditions.#10608
e31bea0704890ff92ce4f9b0ce536c1c90715f2cThanks @matthewp! - Fixes bug with head content being pushed into bodyUpdated dependencies [
2cf116f80cb5e421ab5cc5eb4a654e7b78c1b8de,374efcdff9625ca43309d89e3b9cfc9174351512]:v4.5.12Compare Source
Patch Changes
#10596
20463a6c1e1271d8dc3cb0ab3419ee5c72abd218Thanks @Princesseuh! - AddremoveBasefunctionUpdated dependencies [
20463a6c1e1271d8dc3cb0ab3419ee5c72abd218]:v4.5.11Compare Source
Patch Changes
#10567
fbdc10f90f7baa5c49f2f53e3e4ce8f453814c01Thanks @Princesseuh! - Fixesastro:assetsnot working when using complex config withvite.build.rollupOptions.output.assetFileNames#10593
61e283e5a0d95b6ef5d3c4c985d6ee78f74bbd8eThanks @Princesseuh! - Fixes Polymorphic type helper causing TypeScript errors in certain cases after the previous update#10543
0fd36bdb383297b32cc523b57d2442132da41595Thanks @matthewp! - Fixes inline stylesheets with content collections cache#10582
a05953538fcf524786385830b99c0c5a015173e8Thanks @lilnasy! - Fixes an issue where the dev server got stuck in a loop while routing responses with a 404 status code to the 404 route.v4.5.10Compare Source
Patch Changes
#10549
54c2f9707f5d038630143f769e3075c698474654Thanks @admirsaheta! - Updates theHTMLAttributestype exported fromastroto allow data attributes#10562
348c1ca1323d0516c2dcf8e963343cd12cb5407fThanks @apetta! - Fixes minor type issues inside the built-in components of Astro#10550
34fa8e131b85531e6629390307108ffc4adb7ed1Thanks @Skn0tt! - Fixes bug where server builds would include unneeded assets in SSR Function, potentially leading to upload errors on Vercel, Netlify because of size limitsUpdated dependencies [
c585528f446ccca3d4c643f4af5d550b93c18902]:v4.5.9Compare Source
Patch Changes
#10532
8306ce1ff7b71a2a0d7908336c9be462a54d395aThanks @martrapp! - Fixes a style issue ofclient:onlycomponents in DEV mode during view transitions.#10473
627e47d67af4846cea2acf26a96b4124001b26fcThanks @bluwy! - Fixes and improves performance when rendering Astro JSXv4.5.8Compare Source
Patch Changes
#10504
8e4e554cc211e59c329c0a5d110c839c886ff120Thanks @Princesseuh! - Update Babel version to fix regression in Babel's7.24.2.Updated dependencies [
19e42c368184013fc30d1e46753b9e9383bb2bdf]:v4.5.7Compare Source
Patch Changes
e4a6462751725878bfe47632eeafa6854cad5bf2Thanks @firefoxic! -<link>tags created by astro for optimized stylesheets now do not include the closing forward slash. This slash is optional for void elements such as link, but made some html validation fail.v4.5.6Compare Source
Patch Changes
#10455
c12666166db724915e42e37a048483c99f88e6d9Thanks @lilnasy! - Adds a helpful error message that will be shown when an endpoint does not return aResponse.#10426
6a9a35ee15069541c3144012385366a3c689240aThanks @markgaze! - Fixes an issue with generating JSON schemas when the schema is a function#10448
fcece3658697248ab58f77b3d4a8b14d362f3c47Thanks @lilnasy! - Fixes an issue where multiple rendering errors resulted in a crash of the SSR app server.v4.5.5Compare Source
Patch Changes
#10379
3776ecf0aa9e08a992d3ae76e90682fd04093721Thanks @1574242600! - Fixes a routing issue with partially truncated dynamic segments.#10442
f8e0ad3c52a37b8a2175fe2f5ff2bd0cd738f499Thanks @Princesseuh! - Fixes small rendering issues with the dev toolbar in certain contexts#10438
5b48cc0fc8383b0659a595afd3a6ee28b28779c3Thanks @bholmesdev! - Generate Astro DB types when runningastro sync.#10456
1900a8f9bc337f3a882178d1770e10ab67fab0ceThanks @martrapp! - Fixes an error when usingastro:transtions/clientwithout<ViewTransitions/>v4.5.4Compare Source
Patch Changes
128c7a36397d99608dea918885b68bd302d00e7fThanks @lilnasy! - Fixes an issue where error pages did not have access to theAstro.localsfields provided by the adapter.v4.5.3Compare Source
Patch Changes
#10410
055fe293c6702dd27bcd6c4f59297c6d4385abb1Thanks @lilnasy! - Fixes an issue where configured redirects could not include certain characters in the target path.#9820
8edc42aa7c209b12d98ecf20cdecccddf7314af0Thanks @alexnguyennz! - Prevents fully formed URLs in attributes from being escapedv4.5.2Compare Source
Patch Changes
629c9d7c4d96ae5711d95601e738b3d31d268116Thanks @mingjunlu! - Fixes an issue where dev toolbar x-ray didn't escape props content.v4.5.1Compare Source
Patch Changes
#10392
02aeb01cb8b62b9cc4dfe6069857219404343b73Thanks @martrapp! - Fixes broken types for some functions ofastro:transitions/client.#10390
236cdbb611587692d3c781850cb949604677ef82Thanks @bholmesdev! - Adds--helpreference for new db and studio CLI commandsv4.5.0Compare Source
Minor Changes
#10206
dc87214141e7f8406c0fdf6a7f425dad6dea6d3eThanks @lilnasy! - Allows middleware to run when a matching page or endpoint is not found. Previously, apages/404.astroorpages/[...catch-all].astroroute had to match to allow middleware. This is now not necessary.When a route does not match in SSR deployments, your adapter may show a platform-specific 404 page instead of running Astro's SSR code. In these cases, you may still need to add a
404.astroor fallback route with spread params, or use a routing configuration option if your adapter provides one.#9960
c081adf998d30419fed97d8fccc11340cdc512e0Thanks @StandardGage! - Allows passing any props to the<Code />component#10102
e3f02f5fb1cf0dae3c54beb3a4af3dbf3b06abb7Thanks @bluwy! - Adds a newexperimental.directRenderScriptconfiguration option which provides a more reliable strategy to prevent scripts from being executed in pages where they are not used.This replaces the
experimental.optimizeHoistedScriptflag introduced in v2.10.4 to prevent unused components' scripts from being included in a page unexpectedly. That experimental option no longer exists and must be removed from your configuration, whether or not you enabledirectRenderScript:With
experimental.directRenderScriptconfigured, scripts are now directly rendered as declared in Astro files (including existing features like TypeScript, importingnode_modules, and deduplicating scripts). You can also now conditionally render scripts in your Astro file.However, this means scripts are no longer hoisted to the
<head>and multiple scripts on a page are no longer bundled together. If you enable this option, you should check that all your<script>tags behave as expected.This option will be enabled by default in Astro 5.0.
#10130
5a9528741fa98d017b269c7e4f013058028bdc5dThanks @bluwy! - Stabilizesmarkdown.shikiConfig.experimentalThemesasmarkdown.shikiConfig.themes. No behaviour changes are made to this option.#10189
1ea0a25b94125e4f6f2ac82b42f638e22d7bdffdThanks @peng! - Adds the option to pass an object tobuild.assetsPrefix. This allows for the use of multiple CDN prefixes based on the target file type.When passing an object to
build.assetsPrefix, you must also specify afallbackdomain to be used for all other file types not specified.Specify a file extension as the key (e.g. 'js', 'png') and the URL serving your assets of that file type as the value:
#10252
3307cb34f17159dfd3f03144697040fcaa10e903Thanks @Princesseuh! - Adds support for emitting warning and info notifications from dev toolbar apps.When using the
toggle-notificationevent, the severity can be specified throughdetail.level:#10186
959ca5f9f86ef2c0a5a23080cc01c25f53d613a9Thanks @Princesseuh! - Adds the ability to set colors on all the included UI elements for dev toolbar apps. Previously, only badge and buttons could be customized.#10136
9cd84bd19b92fb43ae48809f575ee12ebd43ea8fThanks @matthewp! - Changes the default behavior oftransition:persistto update the props of persisted islands upon navigation. Also adds a new view transitions optiontransition:persist-props(default:false) to prevent props from updating as needed.Islands which have the
transition:persistproperty to keep their state when using the<ViewTransitions />router will now have their props updated upon navigation. This is useful in cases where the component relies on page-specific props, such as the current page title, which should update upon navigation.For example, the component below is set to persist across navigation. This component receives a
productsprops and might have some internal state, such as which filters are applied:Upon navigation, this component persists, but the desired
productsmight change, for example if you are visiting a category of products, or you are performing a search.Previously the props would not change on navigation, and your island would have to handle updating them externally, such as with API calls.
With this change the props are now updated, while still preserving state.
You can override this new default behavior on a per-component basis using
transition:persist-props=trueto persist both props and state during navigation:#9977
0204b7de37bf626e1b97175b605adbf91d885386Thanks @OliverSpeir! - Supports adding thedata-astro-rerunattribute on script tags so that they will be re-executed after view transitions#10145
65692fa7b5f4440c644c8cf3dd9bc50103d2c33bThanks @alexanderniebuhr! - Adds experimental JSON Schema support for content collections.This feature will auto-generate a JSON Schema for content collections of
type: 'data'which can be used as the$schemavalue for TypeScript-style autocompletion/hints in tools like VSCode.To enable this feature, add the experimental flag:
This experimental implementation requires you to manually reference the schema in each data entry file of the collection:
Alternatively, you can set this in your VSCode
json.schemassettings:Note that this initial implementation uses a library with known issues for advanced Zod schemas, so you may wish to consult these limitations before enabling the experimental flag.
#10130
5a9528741fa98d017b269c7e4f013058028bdc5dThanks @bluwy! - Migratesshikijitoshiki1.0#10268
2013e70bce16366781cc12e52823bb257fe460c0Thanks @Princesseuh! - Adds support for page mutations to the audits in the dev toolbar. Astro will now rerun the audits whenever elements are added or deleted from the page.#10217
5c7862a9fe69954f8630538ebb7212cd04b8a810Thanks @Princesseuh! - Updates the UI for dev toolbar audits with new informationPatch Changes
#10360
ac766647b0e6156b7c4a0bb9a11981fe168852d7Thanks @nmattia! - Fixes an issue where some CLI commands attempted to directly read vite config files.#10291
8107a2721b6abb07c3120ac90e03c39f2a44ab0cThanks @bluwy! - Treeshakes unused Astro component scoped styles#10368
78bafc5d661ff7dd071c241cb1303c4d8a774d21Thanks @Princesseuh! - Updates the basetsconfig.jsonpreset withjsx: 'preserve'in order to fix errors when importing Astro files inside.jsand.tsfiles.Updated dependencies [
c081adf998d30419fed97d8fccc11340cdc512e0,1ea0a25b94125e4f6f2ac82b42f638e22d7bdffd,5a9528741fa98d017b269c7e4f013058028bdc5d,a31bbd7ff8f3ec62ee507f72d1d25140b82ffc18]:v4.4.15Compare Source
Patch Changes
33583e8b31ee8a33e26cf57f30bb422921f4745dThanks @lilnasy! - Fixes an issue where elements slotted within interactive framework components disappeared after hydration.v4.4.14Compare Source
Patch Changes
#10355
8ce9fffd44b0740621178d61fb1425bf4155c2d7Thanks @ematipico! - Fixes a regression where full dynamic routes were prioritized over partial dynamic routes. Now a route likefood-[name].astrois matched before[name].astro.#10356
d121311a3f4b5345e344e31f75d4e7164d65f729Thanks @mingjunlu! - Fixes an issue wheregetCollectionmight returnundefinedwhen content collection is empty#10325
f33cce8f6c3a2e17847658cdedb015bd93cc1ee3Thanks @lilnasy! - Fixes an issue wherectx.siteincluded the configuredbasein API routes and middleware, unlikeAstro.sitein astro pages.#10343
f973aa9110592fa9017bbe84387f22c24a6d7159Thanks @ematipico! - Fixes some false positive in the dev toolbar a11y audits, by adding theaelement to the list of interactive elements.#10295
fdd5bf277e5c1cfa30c1bd2ca123f4e90e8d09d9Thanks @rossrobino! - Adds a prefetch fallback when using theexperimental.clientPrerenderoption. If prerendering fails, which can happen if Chrome extensions block prerendering, it will fallback to prefetching the URL. This works by adding aprefetchfield to thespeculationrulesscript, but does not create an extra request.v4.4.13Compare Source
Patch Changes
a2e9b2b936666b2a4779feb00dcb8ff0ab82c2ecThanks @matthewp! - Fixes @astrojs/db loading TS in the fixturesv4.4.12Compare Source
Patch Changes
f2e60a96754ed1d86001fe4d5d3a0c0ef657408dThanks @FredKSchott! - Fixes an issue where slotting interactive components within a "client:only" component prevented all component code in the page from running.v4.4.11Compare Source
Patch Changes
#10281
9deb919ff95b1d2ffe5a5f70ec683e32ebfafd05Thanks @lilnasy! - Fixes an issue where404.astrowas ignored withi18nrouting enabled.#10279
9ba3e2605daee3861e3bf6c5768f1d8bced4709dThanks @lilnasy! - Fixes an issue where returning redirect responses resulted in missing files with certain adapters.#10319
19ecccedaab6d8fa0ff23711c88fa7d4fa34df38Thanks @lilnasy! - Fixes an issue where streaming SSR responses sometimes failed with "iterator.resultis not a function" on node-based adapters.#10302
992537e79f1847b590a2e226aac88a47a6304f68Thanks @florian-lefebvre! - Fixes an issue that causes static entrypoints build to fail because of the path in certain conditions. Specifically, it failed if the path had an extension (like.astro,.mdxetc) and such extension would be also within the path (like./.astro/index.astro).#10298
819d20a89c0d269333c2d397c1080884f516307aThanks @Fryuni! - Fix an incorrect conflict resolution between pages generated from static routes and rest parametersv4.4.10Compare Source
Patch Changes
4bc360cd5f25496aca3232f6efb3710424a14a34Thanks @sanman1k98! - Fixes jerky scrolling on IOS when using view transitions.v4.4.9Compare Source
Patch Changes
#10278
a548a3a99c2835c19662fc38636f92b2bda26614Thanks @Princesseuh! - Fixes original images sometimes being kept / deleted when they shouldn't in both MDX and Markdoc#10280
3488be9b59d1cb65325b0e087c33bcd74aaa4926Thanks @bholmesdev! - Finalize db API to a shared db/ directory.v4.4.8Compare Source
Patch Changes
5e3e74b61daa2ba44c761c9ab5745818661a656eThanks @Princesseuh! - Fixes dev toolbar warning about using the proper loading attributes on images usingdata:URIsv4.4.7Compare Source
Patch Changes
#10274
e556151603a2f0173059d0f98fdcbec0610b48ffThanks @lilnasy! - Fixes a regression introduced in v4.4.5 where image optimization did not work in dev mode when a base was configured.#10263
9bdbed723e0aa4243d7d6ee64d1c1df3b75b9aebThanks @martrapp! - Adds auto completion forastro:event names when adding or removing event listeners ondocument.#10284
07f89429a1ef5173d3321e0b362a9dc71fc74fe5Thanks @Princesseuh! - Fixes an issue where in Node SSR, the image endpoint could be used maliciously to reveal unintended information about the underlying system.Thanks to Google Security Team for reporting this issue.
v4.4.6Compare Source
Patch Changes
#10247
fb773c9161bf8faa5ebd7e115f3564c3359e56eaThanks @martrapp! - Fixes an issue wheretransition:animate="none"still allowed the browser-native morph animation.#10248
8ae5d99534fc09d650e10e64a09b61a2807574f2Thanks @ematipico! - Fixes an issue where multiple injected routes with the sameentrypointbut differentpatternwere incorrectly cached, causing some of them not being rendered in the dev server.#10250
57655a99db34e20e9661c039fab253b867013318Thanks @log101! - Fixes the overwriting of localised index pages with redirects#10239
9c21a9df6b03e36bd78dc553e13c55b9ef8c44cdThanks @mingjunlu! - Improves the message ofMiddlewareCantBeLoadedfor clarity#10222
ade9759cae74ca262b988260250bcb202235e811Thanks @martrapp! - Adds a warning in DEV mode when using view transitions on a device with prefer-reduced-motion enabled.#10251
9b00de0a76b4f4b5b808e8c78e4906a2497e8ecfThanks @mingjunlu! - Fixes TypeScript type definitions forCodecomponentthemeandexperimentalThemespropsv4.4.5Compare Source
Patch Changes
#10221
4db82d9c7dce3b73fe43b86020fcfa326c1357ecThanks @matthewp! - Prevents errors in templates from crashing the server#10219
afcb9d331179287629b5ffce4020931258bebefaThanks @matthewp! - Fix dynamic slots missing hydration scripts#10220
1eadb1c5290f2f4baf538c34889a09d5fcfb9bd4Thanks @Princesseuh! - Fixes some built-in apps of the dev toolbar not closing when clicking the page#10154
e64bd0740b44aed5cfaf67e5c37a1c56ed4442f4Thanks @Cherry! - Fixes an issue whereconfig.vite.build.assetsInlineLimitcould not be set as a function.#10196
8fb32f390d40cfa12a82c0645928468d27218866Thanks @lilnasy! - Fixes an issue where a warning about headers being accessed in static mode is unnecessarily shown when i18n is enabled.#10199
6aa660ae7abc6841d7a3396b29f10b9fb7910ce5Thanks @lilnasy! - Fixes an issue where prerendered pages had access to query params in dev mode.v4.4.4Compare Source
Patch Changes
#10195
903eace233033998811b72e27a54c80d8e59ff37Thanks @1574242600! - Fix build failure caused by read-only files under /public (in the presence of client-side JS).#10205
459f74bc71748279fe7dce0688f38bd74b51c5c1Thanks @martrapp! - Adds an error message for non-string transition:name values#10208
8cd38f02456640c063552aef00b2b8a216b3935dThanks @log101! - Fixes custom headers are not added to the Node standalone server responses in preview modev4.4.3Compare Source
Patch Changes
#10143
7c5fcd2fa817472f480bbfbbc11b9ed71a7210abThanks @bluwy! - Improves the defaultoptimizeDeps.entriesVite config to avoid globbing server endpoints, and respect thesrcDiroption#10197
c856c729404196900a7386c8426b81e79684a6a9Thanks @Princesseuh! - Fixes errors being logged twice in some cases#10166
598f30c7cd6c88558e3806d9bc5a15d426d83992Thanks @bluwy! - Improves Astro style tag HMR when updating imported styles#10194
3cc20109277813ccb9578ca87a8b0d680a73c35cThanks @matthewp! - Fixes an issue related to content collections usage in browser context caused bycsssecv4.4.2Compare Source
Patch Changes
a46249173edde66b03c19441144272baa8394fb4Thanks @ematipico! - Fixes an issue with thei18n.routingtypes, where an internal transformation was causing the generation of incorrect types for integrations.v4.4.1Compare Source
Patch Changes
#9795
5acc3135ba5309a566def466fbcbabd23f70cd68Thanks @lilnasy! - Refactors internals relating to middleware, endpoints, and page rendering.#10105
1f598b372410066c6fcd41cba9915f6aaf7befa8Thanks @negativems! - Fixes an issue where some astro commands failed if the astro config file or an integration used the globalcryptoobject.#10165
d50dddb71d87ce5b7928920f10eb4946a5339f86Thanks @ematipico! - Fixes an issue where thei18n.routingobject had all its fields defined as mandatory. Now they all are optionals and shouldn't break when usingastro.config.mts.#10132
1da9c5f2f3fe70b0206d1b3e0c01744fa40d511cThanks @bluwy! - Simplifies internal Vite preview server teardown#10163
b92d35f1026f3e99abb888d1a845bdda4efdc327Thanks @mingjunlu! - Fixes an issue where audit fails to initialize when encountered<a>inside<svg>#10079
80f8996514e6d0546e94bd927650cd4ab2f1fa2fThanks @ktym4a! - Fix integrationData fetch to always be called even if View Transition is enabled.#10139
3c73441eb2eaba767d6dad1b30c0353195d28791Thanks @bluwy! - Fixes style-only change detection for Astro files if both the markup and styles are updatedv4.4.0Compare Source
Minor Changes
#9614
d469bebd7b45b060dc41d82ab1cf18ee6de7e051Thanks @matthewp! - Improves Node.js streaming performance.This uses an
AsyncIterableinstead of aReadableStreamto do streaming in Node.js. This is a non-standard enhancement by Node, which is done only in that environment.#10001
748b2e87cd44d8bcc1ab9d7e504703057e2000cdThanks @bholmesdev! - Removes content collection warning when a configured collection does not have a matching directory name. This should resolvei18ncollection warnings for Starlight users.This also ensures configured collection names are always included in
getCollection()andgetEntry()types even when a matching directory is absent. We hope this allows users to discover typos during development by surfacing type information.#10074
7443929381b47db0639c49a4d32aec4177bd9102Thanks @Princesseuh! - Add a UI showing the list of found problems when using the audit app in the dev toolbar#10099
b340f8fe3aaa81e38c4f1aa41498b159dc733d86Thanks @martrapp! - Fixes a regression where view transition names containing special characters such as spaces or punctuation stopped working.Regular use naming your transitions with
transition: nameis unaffected.However, this fix may result in breaking changes if your project relies on the particular character encoding strategy Astro uses to translate
transition:namedirectives into values of the underlying CSSview-transition-nameproperty. For example,Welcome to Astrois now encoded asWelcome_20to_20Astro_2e.This mainly affects spaces and punctuation marks but no Unicode characters with codes >= 128.
#9976
91f75afbc642b6e73dd4ec18a1fe2c3128c68132Thanks @OliverSpeir! - Adds a new optionalastro:assetsimage attributeinferSizefor use with remote images.Remote images can now have their dimensions inferred just like local images. Setting
inferSizetotrueallows you to usegetImage()and the<Image />and<Picture />components without setting thewidthandheightproperties.Read more about using
inferSizewith remote images in our documentation.#10015
6884b103c8314a43e926c6acdf947cbf812a21f4Thanks @Princesseuh! - Adds initial support for performance audits to the dev toolbarPatch Changes
#10116
4bcc249a9f34aaac59658ca626c828bd6dbb8046Thanks @lilnasy! - Fixes an issue where the dev server froze when typescript aliases were used.#10096
227cd83a51bbd451dc223fd16f4cf1b87b8e44f8Thanks @Fryuni! - Fixes regression on routing priority for multi-layer index pagesThe sorting algorithm positions more specific routes before less specific routes, and considers index pages to be more specific than a dynamic route with a rest parameter inside of it.
This means that
/blogis considered more specific than/blog/[...slug].But this special case was being applied incorrectly to indexes, which could cause a problem in scenarios like the following:
//blog/blog/[...slug]The algorithm would make the following comparisons:
/is more specific than/blog(incorrect)/blog/[...slug]is more specific than/(correct)/blogis more specific than/blog/[...slug](correct)Although the incorrect first comparison is not a problem by itself, it could cause the algorithm to make the wrong decision.
Depending on the other routes in the project, the sorting could perform just the last two comparisons and by transitivity infer the inverse of the third (
/blog/[...slug>/>/blog), which is incorrect.Now the algorithm doesn't have a special case for index pages and instead does the comparison soleley for rest parameter segments and their immediate parents, which is consistent with the transitivity property.
#10120
787e6f52470cf07fb50c865948b2bc8fe45a6d31Thanks @bluwy! - Updates and supports Vite 5.1#10096
227cd83a51bbd451dc223fd16f4cf1b87b8e44f8Thanks @Fryuni! - Fixes edge case on i18n fallback routesPreviously index routes deeply nested in the default locale, like
/some/nested/index.astrocould be mistaked as the root index for the default locale, resulting in an incorrect redirect on/.#10112
476b79a61165d0aac5e98459a4ec90762050a14bThanks @Princesseuh! - Renames the home Astro Devoolbar App toastro:home#10117
51b6ff7403c1223b1c399e88373075972c82c24cThanks @hippotastic! - Fixes an issue wherecreate astro,astro addand@astrojs/upgradewould fail due to unexpected package manager CLI output.v4.3.7Compare Source
Patch Changes
#9857
73bd900754365b006ee730df9f379ba924e5b3faThanks @iamyunsin! - Fixes false positives in the dev overlay audit when multiplerolevalues exist.#10075
71273edbb429b5afdba6f8ee14681b66e4c09eccThanks @lilnasy! - Improves error messages for island hydration.#10072
8106178043050d142bf385bed2990730518f28e2Thanks @lilnasy! - Clarifies error messages in endpoint routing.#9971
d9266c4467ca0faa1213c1a5995164e5655ab375Thanks @mingjunlu! - Fixes an issue where ReadableStream wasn't canceled in dev modev4.3.6Compare Source
Patch Changes
#10063
dac759798c111494e76affd2c2504d63944871feThanks @marwan-mohamed12! - Movesshikiji-corefromdevDependenciestodependenciesto prevent type errors#10067
989ea63bb2a5a670021541198aa70b8dc7c4bd2fThanks @ematipico! - Fixes a regression in theastro:i18nmodule, where the functionsgetAbsoluteLocaleUrlandgetAbsoluteLocaleUrlListreturned a URL with double slash with a certain combination of options.#10060
1810309e65c596266355c3b7bb36cdac70f3305eThanks @lilnasy! - Fixes an issue where custom client directives added by integrations broke builds with a custom root.#9991
8fb67c81bb84530b39df4a1449c0862def0854afThanks @ktym4a! - Increases compatibility with standard browser behavior by changing where view transitions occur on browser back navigation.v4.3.5Compare Source
Patch Changes
#10022
3fc76efb2a8faa47edf67562a1f0c84a19be1b33Thanks @lilnasy! - Fixes a regression where types for theastro:contentmodule did not include required exports, leading to typescript errors.#10016
037e4f12dd2f460d66f72c9f2d992b95e74d2da9Thanks @ematipico! - Fixes a bug where routes with a name that start with the name of thei18n.defaultLocalewere incorrectly returning a 404 response.v4.3.4Compare Source
Patch Changes
#10013
e6b5306a7de779ce495d0ff076d302de0aa57eafThanks @delucis! - Fixes a regression in content collection types#10003
ce4283331f18c6178654dd705e3cf02efeef004aThanks @bholmesdev! - Adds support for.strict()on content collection schemas when a customslugis present.v4.3.3Compare Source
Patch Changes
#9998
18ac0940ea1b49b6b0ddd9be1f96aef416e2d7eeThanks @ematipico! - Fixes a bug inAstro.currentLocalethat wasn't returning the correct locale when a locale is configured viapath#9998
18ac0940ea1b49b6b0ddd9be1f96aef416e2d7eeThanks @ematipico! - Fixes a regression inAstro.currentLocalewhere it stopped working properly with dynamic routes#9956
81acac24a3cac5a9143155c1d9f838ea84a70421Thanks @matthewp! - Fixes HMR for MDX dependencies in Content Collections#9999
c53a31321a935e4be04809046d7e0ba3cc41b272Thanks @MoustaphaDev! - Rollbacks the feature which allowed to dynamically generate slots with variable slot names due to unexpected regressions.#9906
3c0876cbed5033e6b5b42cc2b9d8b393d7e5a55eThanks @florian-lefebvre! - Improves the types for theastro:contentmodule by making low fidelity types available before runningastro syncv4.3.2Compare Source
Patch Changes
#9932
9f0d89fa7e9e7c08c8600b0c49c2cce7489a7582Thanks @ematipico! - Fixes a case where a warning was logged even when the featurei18nDomainswasn't enabled#9907
6c894af5ab79f290f4ff7feb68617a66e91febc1Thanks @ktym4a! - Load 404.html on all non-existent paths on astro preview.v4.3.1Compare Source
Patch Changes
#9841
27ea080e24e2c5cdc59b63b1dfe0a83a0c696597Thanks @kristianbinau! - Makes the warning clearer when having a custombaseand requesting a public URL without it#9888
9d2fdb293d6a7323e10126cebad18ef9a2ea2800Thanks @natemoo-re! - Improves error handling logic for theastro synccommand.#9918
d52529e09450c84933dd15d6481edb32269f537bThanks @LarryIVC! - Adds thenameattribute to the<details>tag type#9938
1568afb78a163db63a4cde146dec87785a83db1dThanks @lilnasy! - Fixes a regression where middleware did not run for prerendered pages and endpoints.#9931
44674418965d658733d3602668a9354e18f8ef89Thanks @lilnasy! - Fixes a regression where a response created withResponse.redirector containingnullas the body never completed in node-based adapters.v4.3.0Compare Source
Minor Changes
#9839
58f9e393a188702eef5329e41deff3dcb65a3230Thanks @Princesseuh! - Adds a newComponentPropstype export fromastro/typesto get the props type of an Astro component.#9159
7d937c158959e76443a02f740b10e251d14dbd8cThanks @bluwy! - Adds CLI shortcuts as an easter egg for the dev server:o + enter: opens the site in your browserq + enter: quits the dev serverh + enter: prints all available shortcuts#9764
fad4f64aa149086feda2d1f3a0b655767034f1a8Thanks @matthewp! - Adds a newbuild.formatconfiguration option:'preserve'. This option will preserve your source structure in the final build.The existing configuration options,
fileanddirectory, either build all of your HTML pages as files matching the route name (e.g./about.html) or build all your files asindex.htmlwithin a nested directory structure (e.g./about/index.html), respectively. It was not previously possible to control the HTML file built on a per-file basis.One limitation of
build.format: 'file'is that it cannot createindex.htmlfiles for any individual routes (other than the base path of/) while otherwise building named files. Creating explicit index pages within your file structure still generates a file named for the page route (e.g.src/pages/about/index.astrobuilds/about.html) when using thefileconfiguration option.Rather than make a breaking change to allow
build.format: 'file'to be more flexible, we decided to create a newbuild.format: 'preserve'.The new format will preserve how the filesystem is structured and make sure that is mirrored over to production. Using this option:
about.astrobecomesabout.htmlabout/index.astrobecomesabout/index.htmlSee the
build.formatconfiguration options reference for more details.#9143
041fdd5c89920f7ccf944b095f29e451f78b0e28Thanks @ematipico! - Adds experimental support for a new i18n domain routing option ("domains") that allows you to configure different domains for individual locales in entirely server-rendered projects.To enable this in your project, first configure your
server-rendered project's i18n routing with your preferences if you have not already done so. Then, set theexperimental.i18nDomainsflag totrueand addi18n.domainsto map any of your supportedlocalesto custom URLs:With
"domains"configured, the URLs emitted bygetAbsoluteLocaleUrl()andgetAbsoluteLocaleUrlList()will use the options set ini18n.domains.Similarly, your localized files will create routes at corresponding URLs:
/en/about.astrowill be reachable at the URLhttps://example.com/about./fr/about.astrowill be reachable at the URLhttps://fr.example.com/about./es/about.astrowill be reachable at the URLhttps://example.es/about./ja/about.astrowill be reachable at the URLhttps://example.com/ja/about.See our Internationalization Guide for more details and limitations on this experimental routing feature.
#9755
d4b886141bb342ac71b1c060e67d66ca2ffbb8bdThanks @OliverSpeir! - Fixes an issue where images in Markdown required a relative specifier (e.g../)Now, you can use the standard
syntax in Markdown files for images colocated in the same folder: no relative specifier required!There is no need to update your project; your existing images will still continue to work. However, you may wish to remove any relative specifiers from these Markdown images as they are no longer necessary:
Patch Changes
#9908
2f6d1faa6f2d6de2d4ccd2a48adf5adadc82e593Thanks @lilnasy! - Improves http behavior relating to errors encountered while streaming a response.#9877
7be5f94dcfc73a78d0fb301eeff51614d987a165Thanks @fabiankachlock! - Fixes the content config type path on windows#9143
041fdd5c89920f7ccf944b095f29e451f78b0e28Thanks @ematipico! - Fixes an issue where the functiongetLocaleRelativeUrlListwasn't normalising the paths by default#9911
aaedb848b1d6f683840035865528506a346ea659Thanks @natemoo-re! - Fixes an issue where some adapters that do not include astart()export would error rather than silently proceedv4.2.8Compare Source
Patch Changes
#9884
37369550ab57ca529fd6c796e5b0e96e897ca6e5Thanks @lilnasy! - Fixes an issue where multiple cookies were sent in a single Set-Cookie header in the dev mode.#9876
e9027f194b939ac5a4d795ee1a2c24e4a6fbefc0Thanks @friedemannsommer! - Fixes an issue where usingResponse.redirectin an endpoint led to an error.#9882
13c3b712c7ba45d0081f459fc06f142216a4ec59Thanks @natemoo-re! - Improves handling of YAML parsing errors#9878
a40a0ff5883c7915dd55881dcebd052b9f94a0ebThanks @lilnasy! - Fixes an issue where setting trailingSlash to "never" had no effect onAstro.url.v4.2.7Compare Source
Patch Changes
#9840
70fdf1a5c660057152c1ca111dcc89ceda5c8840Thanks @delucis! - ExposeContentConfigtype fromastro:content#9865
00ba9f1947ca9016cd0ee4d8f6048027fab2ab9aThanks @ematipico! - Fixes a bug inAstro.currentLocalewhere the value was incorrectly computed during the build.#9838
0a06d87a1e2b94be00a954f350c184222fa0594dThanks @lilnasy! - Fixes an issue whereastro:i18ncould not be used in framework components.Updated dependencies [
44c957f893c6bf5f5b7c78301de7b21c5975584d]:v4.2.6Compare Source
Patch Changes
#9825
e4370e9e9dd862425eced25823c82e77d9516927Thanks @tugrulates! - Fixes false positive aria role errors on interactive elements#9828
a3df9d83ca92abb5f08f576631019c1604204bd9Thanks @ematipico! - Fixes a case where shared modules among pages and middleware were transformed to a no-op after the build.#9834
1885cea308a62b173a50967cf5a0b174b3c3f3f1Thanks @Princesseuh! - Fixes third-party dev toolbar apps not loading correctly when using absolute paths on Windowsv4.2.5Compare Source
Patch Changes
#9818
d688954c5adba75b0d676694fbf5fb0da1c0af13Thanks @Princesseuh! - Improves the wording of a few confusing error messages#9680
5d7db1dbb0ff06db98e08b0ca241ff09d0b8b44dThanks @loucyx! - Fixes types generation from Content Collections config file#9822
bd880e8437ea2df16f322f604865c1148a9fd4cfThanks @liruifengv! - Applies the correct escaping to identifiers used withtransition:name.#9830
f3d22136e53fd902310024519fc4de83f0a58039Thanks @lilnasy! - Fixes an issue where 404 responses from endpoints were replaced with contents of 404.astro in dev mode.#9816
2a44c8f93201958fba2d1e83046eabcaef186b7cThanks @Princesseuh! - Adds telemetry for when apps are toggled in the dev toolbar. This data is completely anonymous and only the names of built-in apps are shared with us. This data will help us monitor how much the dev toolbar is used and which apps are used more. For more information on how Astro collects telemetry, visit the following page: https://astro.build/telemetry/#9807
b3f313138bb314e2b416c29cda507383c2a9f816Thanks @bluwy! - Fixes environment variables replacement forexport const prerender#9790
267c5aa2c7706f0ea3447f20a09d85aa560866adThanks @lilnasy! - Refactors internals of theastro:i18nmodule to be more maintainable.#9776
dc75180aa698b298264362bab7f00391af427798Thanks @lilnasy! - Simplifies internals that handle middleware.v4.2.4Compare Source
Patch Changes
#9792
e22cb8b10c0ca9f6d88cab53cd2713f57875ab4bThanks @tugrulates! - Accept aria roleswitchon toolbar audit.#9606
e6945bcf23b6ad29388bbadaf5bb3cc31dd4a114Thanks @eryue0220! - Fixes escaping behavior for.htmlfiles and components#9786
5b29550996a7f5459a0d611feea6e51d44e1d8edThanks @Fryuni! - Fixes a regression in routing priority for index pages in rest parameter folders and dynamic sibling trees.Considering the following tree:
The routes are sorted in this order:
This allows for index files to be used as overrides to rest parameter routes on SSR when the rest parameter matching
undefinedis not desired.#9775
075706f26d2e11e66ef8b52288d07e3c0fa97eb1Thanks @lilnasy! - Simplifies internals that handle endpoints.#9773
9aa7a5368c502ae488d3a173e732d81f3d000e98Thanks @LunaticMuch! - Raises the required vite version to address a vulnerability invite.server.fs.denythat affected the dev mode.#9781
ccc05d54014e24c492ca5fddd4862f318aac8172Thanks @stevenbenner! - Fix build failure when image file name includes special charactersv4.2.3Compare Source
Patch Changes
eed0e8757c35dde549707e71c45862438a043fb0Thanks @Princesseuh! - Fix apps being able to crash the dev toolbar in certain casesv4.2.2Compare Source
Patch Changes
#9712
ea6cbd06a2580527786707ec735079ff9abd0ec0Thanks @bluwy! - Improves HMR behavior for style-only changes in.astrofiles#9739
3ecb3ef64326a8f77aa170df1e3c89cb5c12cc93Thanks @ematipico! - Makes i18n redirects take thebuild.formatconfiguration into account#9762
1fba85681e86aa83d24336d4209cafbc76b37607Thanks @ematipico! - Addspopovertarget" to the attribute that can be passed to thebutton` element#9605
8ce40a417c854d9e6a4fa7d5a85d50a6436b4a3cThanks @MoustaphaDev! - Adds support for dynamic slot names#9381
9e01f9cc1efcfb938355829676d51b24818ab2bbThanks @martrapp! - Improves the CLI output ofastro preferences listto include additional relevant information#9741
73d74402007896204ee965f6553dc83b3dec8d2fThanks @taktran! - Fixes an issue where dot files were not copied over from the public folder to the output folder, when build command was run in a folder other than the root of the project.#9730
8d2e5db096f1e7b098511b4fe9357434a6ff0703Thanks @Blede2000! - Allow i18n routing utilities like getRelativeLocaleUrl to also get the default local path when redirectToDefaultLocale is falseUpdated dependencies [
53c69dcc82cdf4000aff13a6c11fffe19096cf45,2f81cffa9da9db0e2802d303f94feaee8d2f54ec,a505190933365268d48139a5f197a3cfb5570870]:v4.2.1Compare Source
Patch Changes
a4b696def3a7eb18c1ae48b10fd3758a1874b6feThanks @Fryuni! - Fixes a regression in routing priority betweenindex.astroand dynamic routes with rest parametersv4.2.0Compare Source
Minor Changes
#9566
165cfc154be477337037185c32b308616d1ed6faThanks @OliverSpeir! - Allows remark plugins to pass options specifying how images in.mdfiles will be optimized#9661
d6edc7540864cf5d294d7b881eb886a3804f6d05Thanks @ematipico! - Adds new helper functions for adapter developers.Astro.clientAddresscan now be passed directly to theapp.render()method.RequestandResponseobjects are now provided as static methods on theNodeAppclass.Astro.cookies.set()can now be automatically added to theResponseobject by passing theaddCookieHeaderoption toapp.render().#9638
f1a61268061b8834f39a9b38bca043ae41caed04Thanks @ematipico! - Adds a newi18n.routingconfig optionredirectToDefaultLocaleto disable automatic redirects of the root URL (/) to the default locale whenprefixDefaultLocale: trueis set.In projects where every route, including the default locale, is prefixed with
/[locale]/path, this property allows you to control whether or notsrc/pages/index.astroshould automatically redirect your site visitors from/to/[defaultLocale].You can now opt out of this automatic redirection by setting
redirectToDefaultLocale: false:#9671
8521ff77fbf7e867701cc30d18253856914dbd1bThanks @bholmesdev! - Removes the requirement for non-content files and assets inside content collections to be prefixed with an underscore. For files with extensions like.astroor.css, you can now remove underscores without seeing a warning in the terminal.Continue to use underscores in your content collections to exclude individual content files, such as drafts, from the build output.
#9567
3a4d5ec8001ebf95c917fdc0d186d29650533d93Thanks @OliverSpeir! - Improves the a11y-missing-content rule and error message for audit feature of dev-overlay. This also fixes an error where this check was falsely reporting accessibility errors.#9643
e9a72d9a91a3741566866bcaab11172cb0dc7d31Thanks @blackmann! - Adds a newmarkdown.shikiConfig.transformersconfig option. You can use this option to transform the Shikiji hast (AST format of the generated HTML) to customize the final HTML. Also updates Shikiji to the latest stable version.See Shikiji's documentation for more details about creating your own custom transformers, and a list of common transformers you can add directly to your project.
#9644
a5f1682347e602330246129d4666a9227374c832Thanks @rossrobino! - Adds an experimental flagclientPrerenderto prerender your prefetched pages on the client with the Speculation Rules API.Enabling this feature overrides the default
prefetchbehavior globally to prerender links on the client according to yourprefetchconfiguration. Instead of appending a<link>tag to the head of the document or fetching the page with JavaScript, a<script>tag will be appended with the corresponding speculation rules.Client side prerendering requires browser support. If the Speculation Rules API is not supported,
prefetchwill fallback to the supported strategy.See the Prefetch Guide for more
prefetchoptions and usage.#9439
fd17f4a40b83d14350dce691aeb79d87e8fcaf40Thanks @Fryuni! - Adds an experimental flagglobalRoutePriorityto prioritize redirects and injected routes equally alongside file-based project routes, following the same route priority order rules for all routes.Enabling this feature ensures that all routes in your project follow the same, predictable route priority order rules. In particular, this avoids an issue where redirects or injected routes (e.g. from an integration) would always take precedence over local route definitions, making it impossible to override some routes locally.
The following table shows which route builds certain page URLs when file-based routes, injected routes, and redirects are combined as shown below:
/blog/post/[pid]/[page]/blog/[...slug]/blog/tags/[tag]->/[tag]/posts->/blogURLs are handled by the following routes:
/blog/tags/astro/blog/[...slug]/tags/[tag]/blog/post/0/blog/[...slug]/blog/post/[pid]/posts/[page]/blogIn the event of route collisions, where two routes of equal route priority attempt to build the same URL, Astro will log a warning identifying the conflicting routes.
Patch Changes
#9719
7e1db8b4ce2da9e044ea0393e533c6db2561ac90Thanks @bluwy! - Refactors Vite config to avoid Vite 5.1 warnings#9439
fd17f4a40b83d14350dce691aeb79d87e8fcaf40Thanks @Fryuni! - Updates Astro's routing priority rules to prioritize the most specifically-defined routes.Now, routes with more defined path segments will take precedence over less specific routes.
For example,
/blog/posts/[pid].astro(3 path segments) takes precedence over/blog/[...slug].astro(2 path segments). This means that:/pages/blog/posts/[id].astrowill build routes of the form/blog/posts/1and/blog/posts/a/pages/blog/[...slug].astrowill build routes of a variety of forms, includingblog/1and/blog/posts/1/a, but will not build either of the previous routes.For a complete list of Astro's routing priority rules, please see the routing guide. This should not be a breaking change, but you may wish to inspect your built routes to ensure that your project is unaffected.
#9706
1539e04a8e5865027b3a8718c6f142885e7c8d88Thanks @bluwy! - Simplifies HMR handling, improves circular dependency invalidation, and fixes Astro styles invalidationUpdated dependencies [
165cfc154be477337037185c32b308616d1ed6fa,e9a72d9a91a3741566866bcaab11172cb0dc7d31]:v4.1.3Compare Source
Patch Changes
#9665
d02a3c48a3ce204649d22e17b1e26fb5a6a60bcfThanks @bluwy! - Disables internal file watcher for one-off Vite servers to improve start-up performance#9664
1bf0ddd2777ae5f9fde3fd854a9e75aa56c080f2Thanks @bluwy! - Improves HMR for Astro style and script modules#9668
74008cc23853ed507b144efab02300202c5386edThanks @Princesseuh! - Fix the passthrough image service not generatingsrcsetvalues properly#9693
d38b2a4fe827e956662fcf457d1f1f84832c2f15Thanks @kidylee! - Disables View Transition form handling when theactionproperty points to an external URL#9678
091097e60ef38dadb87d7c8c1fc9cb939a248921Thanks @ematipico! - Adds an error during the build phase in casei18n.routing.prefixDefaultLocaleis set totrueand the index page is missing.#9659
39050c6e1f77dc21e87716d95e627a654828ee74Thanks @Princesseuh! - Fix Astro wrongfully deleting certain images imported with?urlwhen used in tandem withastro:assets#9685
35d54b3ddb3310ab4c505d49bd4937b2d25e4078Thanks @lilnasy! - Fixes an issue where anchor elements within a custom component could not trigger a view transition.v4.1.2Compare Source
Patch Changes
#9642
cdb7bfa66260afc79b829b617492a01a709a86efThanks @martrapp! - Fixes an issue where View Transitions did not work when navigating to the 404 page#9637
5cba637c4ec39c06794146b0c7fd3225d26dcabbThanks @bluwy! - Improves environment variables replacement in SSR#9658
a3b5695176cd0280438938c1d6caef478a571415Thanks @martrapp! - Fixes an issue caused by trying to load text/partytown scripts during view transitions#9657
a4f90d95ff97abe59f2a1ef0956cab257ae36838Thanks @ematipico! - Fixes a bug where the custom status code wasn't correctly computed in the dev server#9627
a700a20291e19cde23705e8e661e833aec7d3095Thanks @lilnasy! - Adds a warning when setting cookies will have no effect#9652
e72efd6a9a1e2a70488fd225529617ffd8418534Thanks @bluwy! - Improves environment variables handling by using esbuild to perform replacements#9560
8b9c4844f7b302380835154fab1c3489979fc07dThanks @bluwy! - Fixes tsconfig alias with import.meta.glob#9653
50f39183cfec4a4522c1f935d710e5d9b724993bThanks @Princesseuh! - Pin Sharp to 0.32.6 until we can raise our semver requirements. To use the latest version of Sharp, you can add it to your project's dependencies.v4.1.1Compare Source
Patch Changes
#9618
401fd3e8c8957a3bed6469a622cd67b157ca303fThanks @ldh3907! - Adds a second generic parameter toAPIRouteto type theparams#9600
47b951b3888a5a8a708d2f9b974f12fba7ec9ed3Thanks @jacobdalamb! - Improves tailwind config file detection when adding the tailwind integration usingastro add tailwindTailwind config file ending in
.ts,.mtsor.ctswill now be used instead of creating a newtailwind.config.mjswhen the tailwind integration is added usingastro add tailwind.#9622
5156c740506cbf6ec85c95e1663c14cbd438d75bThanks @bluwy! - Fixes the Sharp image servicelimitInputPixelsoption typev4.1.0Compare Source
Minor Changes
#9513
e44f6acf99195a3f29b8390fd9b2c06410551b74Thanks @wtto00! - Adds a'load'prefetch strategy to prefetch links on page load#9377
fe719e27a84c09e46b515252690678c174a25759Thanks @bluwy! - Adds "Missing ARIA roles check" and "Unsupported ARIA roles check" audit rules for the dev toolbar#9573
2a8b9c56b9c6918531c57ec38b89474571331aeeThanks @bluwy! - Allows passing a string to--openandserver.opento open a specific URL on startup in development#9544
b8a6fa8917ff7babd35dafb3d3dcd9a58cee836dThanks @bluwy! - Adds a helpful error for static sites when you use theastro previewcommand if you have not previously runastro build.#9546
08402ad5846c73b6887e74ed4575fd71a3e3c73dThanks @bluwy! - Adds an option for the Sharp image service to allow large images to be processed. SetlimitInputPixels: falseto bypass the default image size limit:#9596
fbc26976533bbcf2de9d6dba1aa3ea3dc6ce0853Thanks @Princesseuh! - Adds the ability to set arootMarginsetting when using theclient:visibledirective. This allows a component to be hydrated when it is near the viewport, rather than hydrated when it has entered the viewport.#9063
f33fe3190b482a42ebc68cc5275fd7f2c49102e6Thanks @alex-sherwin! - Cookie encoding / decoding can now be customizedAdds new
encodeanddecodefunctions to allow customizing how cookies are encoded and decoded. For example, you can bypass the default encoding viaencodeURIComponentwhen adding a URL as part of a cookie:Later, you can decode the URL in the same way:
Patch Changes
#9593
3b4e629ac8c2fdb4b491bf01abc7794e2e100173Thanks @bluwy! - Improvesastro adderror reporting when the dependencies fail to install#9563
d48ab90fb41fbc0589cd2df711682a41382c03aaThanks @martrapp! - Fixes back navigation to fragment links (e.g.#about) in Firefox when using view transitionsCo-authored-by: Florian Lefebvre 69633530+florian-lefebvre@users.noreply.github.com
Co-authored-by: Sarah Rainsberger sarah@rainsberger.ca
#9597
9fd24a546c45d48451da46637c14e7ed54dac76aThanks @lilnasy! - Fixes an issue where configuring trailingSlash had no effect on API routes.#9586
82bad5d6205672ed3f6a49d4de53d3a68367433eThanks @martrapp! - Fixes page titles in the browser's drop-down for back / forward navigation when using view transitions#9575
ab6049bd58e4d02f47d500f9db08a865bc7f09b8Thanks @bluwy! - Sets correctprocess.env.NODE_ENVdefault when using the JS API#9587
da307e4a080483f8763f1919a05fa2194bb14e22Thanks @jjenzz! - Adds aCSSPropertiesinterface that allows extending the style attribute#9513
e44f6acf99195a3f29b8390fd9b2c06410551b74Thanks @wtto00! - Ignores3gin slow connection detection. Only2gandslow-2gare considered slow connections.v4.0.9Compare Source
Patch Changes
#9571
ec71f03cfd9b8195fb21c92dfda0eff63b6ebeedThanks @bluwy! - Removes telemetry for unhandled errors in the dev server#9548
8049f0cd91b239c52e37d571e3ba3e703cf0e4cfThanks @bluwy! - Fixes error overlay display on URI malformed error#9504
8cc3d6aa46f438d668516539c34b48ad748ade39Thanks @matiboux! - Implement i18n'sgetLocaleByPathfunction#9547
22f42d11a4fd2e154a0c5873c4f516584e383b70Thanks @bluwy! - Prevents ANSI codes from rendering in the error overlay#9446
ede3f7fef6b43a08c9371f7a2531e2eef858b94dThanks @alexnguyennz! - Toggle dev toolbar hitbox height when toolbar is visible#9572
9f6453cf4972ac28eec4f07a1373feaa295c8864Thanks @bluwy! - Documents supported--hostand--portflags inastro preview --help#9540
7f212f0831d8cd899a86fb94899a7cad8ec280dbThanks @matthewp! - Fixes remote images with encoded characters#9559
8b873bf1f343efc1f486d8ef53c38380e2373c08Thanks @sygint! - Adds 'starlight' to the displayed options forastro add#9537
16e61fcacb98e6bd948ac240bc082659d70193a4Thanks @walter9388! -<Image />srcset now parses encoded paths correctlyv4.0.8Compare Source
Patch Changes
#9522
bb1438d20d325acd15f3755c6e306e45a7c64bcdThanks @Zegnat! - Add support for autocomplete attribute to the HTML button type.#9531
662f06fd9fae377bed1aaa49adbba3542cced087Thanks @bluwy! - Fixes duplicated CSS modules content when it's imported by both Astro files and framework components#9501
eb36e95596fcdb3db4a31744e910495e22e3af84Thanks @Princesseuh! - Export JSX namespace fromastro/jsx-runtimefor language tooling to consume#9492
89a2a07c2e411cda32244b7b05d3c79e93f7dd84Thanks @lilnasy! - Improves error message for the case where two similarly named files result in the same content entry.#9532
7224809b73d2c3ec8e8aee2fa07463dc3b57a7a2Thanks @bluwy! - Prevents unnecessary URI decoding when rendering a route#9478
dfef925e1fd07f3efb9fde6f4f23548f2af7dc75Thanks @lilnasy! - Improves errors in certain places to also report their causes.#9463
3b0eaed3b544ef8c4ec1f7b0d5a8f475bcfeb25eThanks @Princesseuh! - Update Sharp version to ^0.33.1#9512
1469e0e5a915e6b42b9953dbb48fe57a74518056Thanks @mingjunlu! - Prevents dev toolbar tooltip from overflowing outside of the screen#9497
7f7a7f1aeaec6b327ae0e5e7470a4f46174bf8aeThanks @lilnasy! - Adds a helpful warning message for when an exported API Route is not uppercase.v4.0.7Compare Source
Patch Changes
#9452
e83b5095fThanks @florian-lefebvre! - Upgrades vite to latest#9352
f515b1421Thanks @tmcw! - Add a more descriptive error message when image conversion fails#9486
f6714f677Thanks @martrapp! - Fixes View Transition's form submission prevention, allowingpreventDefaultto be used.#9461
429be8cc3Thanks @Skn0tt! - update import created forastro create netlify#9464
faf6c7e11Thanks @Fryuni! - Fixes an edge case with view transitions where some spec-compliantContent-Typeheaders would cause a valid HTML response to be ignored.#9400
1e984389bThanks @bluwy! - Fixes importing dev toolbar apps from integrations on Windows#9487
19169db1fThanks @ematipico! - Improves logging of the generated pages during the build#9460
047d285beThanks @Princesseuh! - Fix Astro failing to build on certain exotic platform that reports their CPU count incorrectly#9466
5062d27a1Thanks @knpwrs! - Updates view transitionsformhandling with logic for theenctypeattribute#9458
fa3078ce9Thanks @ematipico! - Correctly handle the error in case the middleware throws a runtime error#9089
5ae657882Thanks @lilnasy! - Fixes an issue where redirects did not replace slugs when the target of the redirect rule was not a verbatim route in the project.#9483
c384f6924Thanks @Princesseuh! - Fix some false positive in the audit logic of the dev toolbar#9437
354a62c86Thanks @dkobierski! - Fixes incorrect hoisted script paths when custom rollup output file names are configured#9475
7ae4928f3Thanks @ematipico! - Remove the manifest from the generated files in thedist/folder.v4.0.6Compare Source
Patch Changes
#9419
151bd429bThanks @matthewp! - Prevent Partytown from hijacking history APIs#9426
c01cc4e34Thanks @alexnguyennz! - Fixes warning for external URL redirects#9445
f963d07f2Thanks @natemoo-re! - Upgrades Astro's compiler to a crash when sourcemaps try to map multibyte characters#9126
6d2d0e279Thanks @lilnasy! - Fixes an issue where error pages were not shown when trailingSlash was set to "always".#9434
c01580a2cThanks @ematipico! - Improves the error message when a middleware doesn't return aResponse#9433
fcc2fd5b0Thanks @ematipico! - Correctly merge headers from the original response when an error page is renderedv4.0.5Compare Source
Patch Changes
#9423
bda1d294fThanks @matthewp! - Error when getImage is passed an undefined src#9424
e1a5a2d36Thanks @matthewp! - Prevents dev server from crashing on unhandled rejections, and adds a helpful error message#9404
8aa17a64bThanks @Princesseuh! - Fixed some newer HTML attributes not being included in our type definitions#9414
bebf38c0cThanks @Skn0tt! - Adds the feature name to logs about feature deprecation / experimental status.#9418
2c168af67Thanks @alexnguyennz! - Fix broken link in CI instructions#9407
546d92c86Thanks @matthewp! - Allows file URLs as import specifiersv4.0.4Compare Source
Patch Changes
#9380
ea0918259Thanks @ematipico! - Correctly handle the rendering of i18n routes whenoutput: "hybrid"is set#9374
65ddb0271Thanks @bluwy! - Fixes an issue where prerendered route paths that end with.mjswere removed from the final build#9375
26f7023d6Thanks @bluwy! - Prettifies generated route names injected by integrations#9387
a7c75b333Thanks @natemoo-re! - Fixes an edge case withastro addthat could install a prerelease instead of a stable release version.Prior to this change
astro add svelteinstallssvelte@5.0.0-next.22After this change
astro add svelteinstallssvelte@4.2.8Updated dependencies [
270c6cc27]:v4.0.3Compare Source
Patch Changes
#9342
eb942942dThanks @Princesseuh! - Fix missingis:inlinetype for the<slot />element#9343
ab0281aeeThanks @martrapp! - Adds source file properties to HTML elements only if devToolbar is enabled#9336
c76901065Thanks @FredKSchott! - dev: fix issue where 404 and 500 responses were logged as 200#9339
0bb3d5322Thanks @morinokami! - Fixed the log message to correctly display 'enabled' and 'disabled' when toggling 'Disable notifications' in the Toolbar.v4.0.2Compare Source
Patch Changes
#9331
cfb20550dThanks @natemoo-re! - Updates an internal dependency (vitefu) to avoid a commonpeerDependencywarning#9327
3878a91beThanks @doseofted! - Fixes an edge case for<form method="dialog">when using View Transitions. Forms withmethod="dialog"no longer require an additionaldata-astro-reloadattribute.v4.0.1Compare Source
Patch Changes
631e5d01bThanks @ematipico! - Fixes an issue where logs that weren't grouped together by route when building the app.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate.