packages/astro/CHANGELOG-v4.md
#12542 65e50eb Thanks @kadykov! - Fix JPEG image size determination
#12525 cf0d8b0 Thanks @ematipico! - Fixes an issue where with i18n enabled, Astro couldn't render the 404.astro component for nonexistent routes.
b140a3f Thanks @ematipico! - Fixes a regression where Astro was trying to access Request.headers#12480 c3b7e7c Thanks @matthewp! - Removes the default throw behavior in astro:env
#12444 28dd3ce Thanks @ematipico! - Fixes an issue where a server island hydration script might fail case the island ID misses from the DOM.
#12476 80a9a52 Thanks @florian-lefebvre! - Fixes a case where the Content Layer glob() loader would not update when renaming or deleting an entry
#12418 25baa4e Thanks @oliverlynch! - Fix cached image redownloading if it is the first asset
#12477 46f6b38 Thanks @ematipico! - Fixes an issue where the SSR build was emitting the dist/server/entry.mjs file with an incorrect import at the top of the file/
#12365 a23985b Thanks @apatel369! - Fixes an issue where Astro.currentLocale was not correctly returning the locale for 404 and 500 pages.
#12436 453ec6b Thanks @martrapp! - Fixes a potential null access in the clientside router
#12392 0462219 Thanks @apatel369! - Fixes an issue where scripts were not correctly injected during the build. The issue was triggered when there were injected routes with the same entrypoint and different pattern
acac0af Thanks @ematipico! - Fixes an issue where the dev server returns a 404 status code when a user middleware returns a valid Response.#12305 f5f7109 Thanks @florian-lefebvre! - Fixes a case where the error overlay would not escape the message
#12402 823e73b Thanks @ematipico! - Fixes a case where Astro allowed to call an action without using Astro.callAction. This is now invalid, and Astro will show a proper error.
---
import { actions } from "astro:actions";
-const result = actions.getUser({ userId: 123 });
+const result = Astro.callAction(actions.getUser, { userId: 123 });
---
#12401 9cca108 Thanks @bholmesdev! - Fixes unexpected 200 status in dev server logs for action errors and redirects.
#12311 bf2723e Thanks @dinesh-58! - Adds checked to the list of boolean attributes.
#12363 222f718 Thanks @Fryuni! - Fixes code generated by astro add command when adding a version of an integration other than the default latest.
#12368 493fe43 Thanks @bluwy! - Improves error logs when executing commands
#12355 c4726d7 Thanks @apatel369! - Improves error reporting for invalid frontmatter in MDX files during the astro build command. The error message now includes the file path where the frontmatter parsing failed.
#12333 836cd91 Thanks @imattacus! - Destroy the server response stream if async error is thrown
#12358 7680349 Thanks @spacedawwwg! - Honors inlineAstroConfig parameter in getViteConfig when creating a logger
#12353 35795a1 Thanks @hippotastic! - Fixes an issue in dev server watch file handling that could cause multiple restarts for a single file change.
#12351 5751488 Thanks @florian-lefebvre! - Reverts a change made in 4.16.6 that prevented usage of astro:env secrets inside middleware in SSR
#12346 20e5a84 Thanks @bluwy! - Fixes sourcemap generation when prefetch is enabled
#12349 1fc83d3 Thanks @norskeld! - Fixes the getImage options type so it properly extends ImageTransform
#12338 9ca89b3 Thanks @situ2001! - Resets NODE_ENV to ensure install command run in dev mode
#12286 9d6bcdb Thanks @florian-lefebvre! - Fixes a case where a warning for experimental astro:env support would be shown when using an adapter but not actually using astro:env
#12342 ffc836b Thanks @liruifengv! - Fixes a typo in the command name of the CLI
#12301 0cfc69d Thanks @apatel369! - Fixes an issue with action handler context by passing the correct context (ActionAPIContext).
#12312 5642ef9 Thanks @koyopro! - Fixes an issue where using getViteConfig() returns incorrect and duplicate configuration
#12245 1d4f6a4 Thanks @bmenant! - Add components property to MDXInstance type definition (RenderResult and module import)
#12340 94eaeea Thanks @ematipico! - Fixes an issue where Astro actions didn't work when base was different from /
#12263 e9e8080 Thanks @Fryuni! - Fixes conflict between server islands and on-demand dynamic routes in the form of /[...rest] or /[paramA]/[paramB].
#12279 b781f88 Thanks @jsparkdev! - Update wrong error message
#12273 c2ee963 Thanks @ascorbic! - Fixes an issue with some package managers where sites would not build if TypeScript was not installed.
#12235 a75bc5e Thanks @ematipico! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.
#11839 ff522b9 Thanks @icaliman! - Fixes error when returning a top-level null from an Astro file frontmatter
#12272 388d237 Thanks @ascorbic! - Correctly handles local images when using a base path in SSR
#11823 a3d30a6 Thanks @DerTimonius! - fix: improve error message when inferSize is used in local images with the Image component
#12227 8b1a641 Thanks @florian-lefebvre! - Fixes a case where environment variables would not be refreshed when using astro:env
#12239 2b6daa5 Thanks @ematipico! - BREAKING CHANGE to the experimental Container API only
Changes the default page rendering behavior of Astro components in containers, and adds a new option partial: false to 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: false to renderToString() and renderToResponse():
import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import Card from '../src/components/Card.astro';
const container = AstroContainer.create();
await container.renderToString(Card); // the string will not contain `<!DOCTYPE html>`
await container.renderToString(Card, { partial: false }); // the string will contain `<!DOCTYPE html>`
ff68ba5 Thanks @martrapp! - Fixes an issue with cssesc in dev mode when setting vite.ssr.noExternal: true#12223 79ffa5d Thanks @ArmandPhilippot! - Fixes a false positive reported by the dev toolbar Audit app where a label was considered missing when associated with a button
The button element 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 a label.
#12199 c351352 Thanks @ematipico! - Fixes a regression in the computation of Astro.currentLocale
#12222 fb55695 Thanks @ematipico! - Fixes an issue where the edge middleware couldn't correctly compute the client IP address when calling ctx.clientAddress()
#12220 b049359 Thanks @bluwy! - Fixes accidental internal setOnSetGetEnv parameter rename that caused runtime errors
#12197 2aa2dfd Thanks @ematipico! - Fix a regression where a port was incorrectly added to the Astro.url
12b0022 Thanks @bluwy! - Reverts https://github.com/withastro/astro/pull/12173 which caused Can't modify immutable headers warnings and 500 errors on Cloudflare Pages#12177 a4ffbfa Thanks @matthewp! - Ensure we target scripts for execution in the router
Using document.scripts is unsafe because if the application has a name="scripts" this will shadow the built-in document.scripts. Fix is to use getElementsByTagName to ensure we're only grabbing real scripts.
#12173 2d10de5 Thanks @ematipico! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.
#12039 710a1a1 Thanks @ematipico! - Adds a markdown.shikiConfig.langAlias option 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 cjs code blocks using the javascript syntax highlighter:
import { defineConfig } from 'astro/config';
export default defineConfig({
markdown: {
shikiConfig: {
langAlias: {
cjs: 'javascript',
},
},
},
});
Then in your Markdown, you can use the alias as the language for a code block for syntax highlighting:
```cjs
'use strict';
function commonJs() {
return 'I am a commonjs file';
}
```
#11984 3ac2263 Thanks @chaegumi! - Adds a new build.concurrency configuration option to specify the number of pages to build in parallel
In 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.
[!WARNING] This feature is stable and is not considered experimental. However, this feature is only intended to address difficult performance issues, and breaking changes may occur in a minor release to keep this option as performant as possible.
// astro.config.mjs
import { defineConfig } from 'astro';
export default defineConfig({
build: {
concurrency: 2,
},
});
#12160 c6fd1df Thanks @louisescher! - Fixes a bug where astro.config.mts and astro.config.cts weren't reloading the dev server upon modifications.
#12130 e96bcae Thanks @thehansys! - Fixes a bug in the parsing of x-forwarded-\* Request headers, where multiple values assigned to those headers were not correctly parsed.
Now, headers like x-forwarded-proto: https,http are correctly parsed.
#12147 9db755a Thanks @ascorbic! - Skips setting statusMessage header for HTTP/2 response
HTTP/2 doesn't support status message, so setting this was logging a warning.
#12151 bb6d37f Thanks @ematipico! - Fixes an issue where Astro.currentLocale wasn't incorrectly computed when the defaultLocale belonged to a custom locale path.
Updated dependencies [710a1a1]:
#12121 2490ceb Thanks @ascorbic! - Support passing the values Infinity and -Infinity as island props.
#12118 f47b347 Thanks @Namchee! - Removes the strip-ansi dependency in favor of the native Node API
#12126 6e1dfeb Thanks @ascorbic! - Clear content layer cache when astro version changes
#12117 a46839a Thanks @ArmandPhilippot! - Updates Vite links to use their new domain
#12124 499fbc9 Thanks @ascorbic! - Allows special characters in Action names
#12123 b8673df Thanks @Princesseuh! - Fixes missing body property on CollectionEntry types for content layer entries
#12132 de35daa Thanks @jcayzac! - Updates the cookie dependency to avoid the CVE 2024-47764 vulnerability.
#12113 a54e520 Thanks @ascorbic! - Adds a helpful error when attempting to render an undefined collection entry
#12097 11d447f Thanks @ascorbic! - Fixes error where references in content layer schemas sometimes incorrectly report as missing
#12108 918953b Thanks @lameuler! - Fixes a bug where data URL images were not correctly handled. The bug resulted in an ENAMETOOLONG error.
#12105 42037f3 Thanks @ascorbic! - Returns custom statusText that has been set in a Response
#12109 ea22558 Thanks @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 d3a74da Thanks @ascorbic! - Handles case where an immutable Response object is returned from an endpoint
#12090 d49a537 Thanks @markjaquith! - Server islands: changes the server island HTML placeholder comment so that it is much less likely to get removed by HTML minifiers.
#12084 12dae50 Thanks @Princesseuh! - Adds missing filePath property on content layer entries
#12046 d7779df Thanks @martrapp! - View transitions: Fixes Astro's fade animation to prevent flashing during morph transitions.
#12043 1720c5b Thanks @bluwy! - Fixes injected endpoint prerender option detection
#12095 76c5fbd Thanks @TheOtterlord! - Fix installing non-stable versions of integrations with astro add
#12034 5b3ddfa Thanks @ematipico! - Fixes an issue where the middleware wasn't called when a project uses 404.astro.
#12042 243ecb6 Thanks @ematipico! - Fixes a problem in the Container API, where a polyfill wasn't correctly applied. This caused an issue in some environments where crypto isn't supported.
#12038 26ea5e8 Thanks @ascorbic! - Resolves image paths in content layer with initial slash as project-relative
When 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.
#12014 53cb41e Thanks @ascorbic! - Fixes an issue where component styles were not correctly included in rendered MDX
#12031 8c0cae6 Thanks @ematipico! - Fixes a bug where the rewrite via next(/*..*/) inside a middleware didn't compute the new APIContext.params
#12026 40e7a1b Thanks @bluwy! - Initializes the Markdown processor only when there's .md files
#12028 d3bd673 Thanks @bluwy! - Handles route collision detection only if it matches getStaticPaths
#12027 dd3b753 Thanks @fviolette! - Add selected to the list of boolean attributes
#12001 9be3e1b Thanks @uwej711! - Remove dependency on path-to-regexp
#12000 a2f8c5d Thanks @ArmandPhilippot! - Fixes an outdated link used to document Content Layer API
#11915 0b59fe7 Thanks @azhirov! - Fix: prevent island from re-rendering when using transition:persist (#11854)
#11993 ffba5d7 Thanks @matthewp! - Fix getStaticPaths regression
This reverts a previous change meant to remove a dependency, to fix a regression with multiple nested spread routes.
#11964 06eff60 Thanks @TheOtterlord! - Add wayland (wl-copy) support to astro info
#11939 7b09c62 Thanks @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 create or update form submission, and uses the type field to determine which object to validate against.
import { defineAction } from 'astro:actions';
import { z } from 'astro:schema';
export const server = {
changeUser: defineAction({
accept: 'form',
input: z.discriminatedUnion('type', [
z.object({
type: z.literal('create'),
name: z.string(),
email: z.string().email(),
}),
z.object({
type: z.literal('update'),
id: z.number(),
name: z.string(),
email: z.string().email(),
}),
]),
async handler(input) {
if (input.type === 'create') {
// input is { type: 'create', name: string, email: string }
} else {
// input is { type: 'update', id: number, name: string, email: string }
}
},
}),
};
The corresponding create and update forms may look like this:
---
import { actions } from 'astro:actions';
---
<!--Create-->
<form action={actions.changeUser} method="POST">
<input type="hidden" name="type" value="create" />
<input type="text" name="name" required />
<input type="email" name="email" required />
<button type="submit">Create User</button>
</form>
<!--Update-->
<form action={actions.changeUser} method="POST">
<input type="hidden" name="type" value="update" />
<input type="hidden" name="id" value="user-123" />
<input type="text" name="name" required />
<input type="email" name="email" required />
<button type="submit">Update User</button>
</form>
#11968 86ad1fd Thanks @NikolaRHristov! - Fixes a typo in the server island JSDoc
#11983 633eeaa Thanks @uwej711! - Remove dependency on path-to-regexp
#11879 bd1d4aa Thanks @matthewp! - Allow passing a cryptography key via ASTRO_KEY
For 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_KEY environment variable to your build in order to reuse the same key.
To generate a key use:
astro create-key
This will print out an environment variable to set like:
ASTRO_KEY=PIAuyPNn2aKU/bviapEuc/nVzdzZPizKNo3OqF/5PmQ=
#11935 c58193a Thanks @Princesseuh! - Fixes astro add not using the proper export point when adding certain adapters
#11902 d63bc50 Thanks @ascorbic! - Fixes case where content layer did not update during clean dev builds on Linux and Windows
#11886 7ff7134 Thanks @matthewp! - Fixes a missing error message when actions throws during astro sync
#11904 ca54e3f Thanks @wtchnm! - perf(assets): avoid downloading original image when using cache
#11870 8e5257a Thanks @ArmandPhilippot! - Fixes typo in documenting the fallbackType property in i18n routing
#11884 e450704 Thanks @ascorbic! - Correctly handles content layer data where the transformed value does not match the input schema
#11900 80b4a18 Thanks @delucis! - Fixes the user-facing type of the new i18n.routing.fallbackType option to be optional
#11872 9327d56 Thanks @bluwy! - Fixes astro add importing adapters and integrations
#11767 d1bd1a1 Thanks @ascorbic! - Refactors content layer sync to use a queue
#11729 1c54e63 Thanks @ematipico! - Adds a new variant sync for the astro:config:setup hook's command property. This value is set when calling the command astro sync.
If your integration previously relied on knowing how many variants existed for the command property, you must update your logic to account for this new option.
#11743 cce0894 Thanks @ph1p! - Adds a new, optional property timeout for the client:idle directive.
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.
<ShowHideButton client:idle={{ timeout: 500 }} />
#11677 cb356a5 Thanks @ematipico! - Adds a new option fallbackType to i18n.routing configuration that allows you to control how fallback pages are handled.
When i18n.fallback is 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.html that will contain the same HTML rendered by the page /en/index.html when src/pages/fr/index.astro does not exist.
// astro.config.mjs
export default defineConfig({
i18n: {
locals: ['en', 'fr'],
defaultLocale: 'en',
routing: {
prefixDefaultLocale: true,
fallbackType: 'rewrite',
},
fallback: {
fr: 'en',
},
},
});
#11708 62b0d20 Thanks @martrapp! - Adds a new object swapFunctions to expose the necessary utility functions on astro:transitions/client that 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 swap function with one that only swaps the <main> part of the page:
<script>
import { swapFunctions } from 'astro:transitions/client';
document.addEventListener('astro:before-swap', (e) => { e.swap = () => swapMainOnly(e.newDocument) });
function swapMainOnly(doc: Document) {
swapFunctions.deselectScripts(doc);
swapFunctions.swapRootAttributes(doc);
swapFunctions.swapHeadElements(doc);
const restoreFocusFunction = swapFunctions.saveFocus();
const newMain = doc.querySelector('main');
const oldMain = document.querySelector('main');
if (newMain && oldMain) {
swapFunctions.swapBodyElement(newMain, oldMain);
} else {
swapFunctions.swapBodyElement(doc.body, document.body);
}
restoreFocusFunction();
};
</script>
See the view transitions guide for more information about hooking into the astro:before-swap lifecycle event and adding a custom swap implementation.
#11843 5b4070e Thanks @bholmesdev! - Exposes z from the new astro:schema module. This is the new recommended import source for all Zod utilities when using Astro Actions.
z will no longer be exposed from astro:actions. To use z in your actions, import it from astro:schema instead:
import {
defineAction,
- z,
} from 'astro:actions';
+ import { z } from 'astro:schema';
#11843 5b4070e Thanks @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:
---
// src/pages/newsletter.astro
import { actions } from 'astro:actions';
const result = Astro.getActionResult(actions.newsletter);
---
{result && !result.error && <p>Thanks for signing up!</p>}
<form method="POST" action={actions.newsletter}>
<input type="email" name="email" />
<button>Sign up</button>
</form>
If you were previously using this feature, please remove the experimental flag from your Astro config:
import { defineConfig } from 'astro'
export default defineConfig({
- experimental: {
- actions: true,
- }
})
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.
#11677 cb356a5 Thanks @ematipico! - Fixes a bug in the logic of Astro.rewrite() which led to the value for base, 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 has base configured, you must now prepend the base to your existing rewrite URL:
// astro.config.mjs
export default defineConfig({
base: '/blog',
});
// src/middleware.js
export function onRequest(ctx, next) {
- return ctx.rewrite("/about")
+ return ctx.rewrite("/blog/about")
}
#11862 0e35afe Thanks @ascorbic! - BREAKING CHANGE to experimental content layer loaders only!
Passes AstroConfig instead of AstroSettings object to content layer loaders.
This will not affect you unless you have created a loader that uses the settings object. If you have, you will need to update your loader to use the config object instead.
export default function myLoader() {
return {
name: 'my-loader'
- async load({ settings }) {
- const base = settings.config.base;
+ async load({ config }) {
+ const base = config.base;
// ...
}
}
}
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 6272e6c Thanks @bluwy! - Uses magicast to update the config for astro add
#11845 440a4be Thanks @bluwy! - Replaces execa with tinyexec internally
#11858 8bab233 Thanks @ascorbic! - Correctly resolves content layer images when filePath is not set
#11847 45b599c Thanks @ascorbic! - Fixes a case where Vite would be imported by the SSR runtime, causing bundling errors and bloat.
#11822 6fcaab8 Thanks @bluwy! - Marks internal vite-plugin-fileurl plugin with enforce: 'pre'
#11713 497324c Thanks @voidfill! - Prevents prefetching of the same urls with different hashes.
#11814 2bb72c6 Thanks @eduardocereto! - Updates the documentation for experimental Content Layer API with a corrected code example
#11842 1ffaae0 Thanks @stephan281094! - Fixes a typo in the MissingImageDimension error message
#11828 20d47aa Thanks @bholmesdev! - Improves error message when invalid data is returned by an Action.
#11809 62e97a2 Thanks @bholmesdev! - Fixes usage of .transform(), .refine(), .passthrough(), and other effects on Action form inputs.
#11812 260c4be Thanks @bholmesdev! - Exposes ActionAPIContext type from the astro:actions module.
#11813 3f7630a Thanks @bholmesdev! - Fixes unexpected undefined value when calling an action from the client without a return value.
#11794 3691a62 Thanks @bholmesdev! - Fixes unexpected warning log when using Actions on "hybrid" rendered projects.
#11801 9f943c1 Thanks @delucis! - Fixes a bug where the filePath property was not available on content collection entries when using the content layer file() loader with a JSON file that contained an object instead of an array. This was breaking use of the image() schema utility among other things.
#11780 c6622ad Thanks @Princesseuh! - Deprecates the Squoosh image service, to be removed in Astro 5.0. We recommend migrating to the default Sharp service.
#11790 41c3fcb Thanks @sarah11918! - Updates the documentation for experimental astro:env with a corrected link to the RFC proposal
#11773 86a3391 Thanks @ematipico! - Changes messages logged when using unsupported, deprecated, or experimental adapter features for clarity
#11745 89bab1e Thanks @bluwy! - Prints prerender dynamic value usage warning only if it's used
#11774 c6400ab Thanks @florian-lefebvre! - Fixes the path returned by injectTypes
#11730 2df49a6 Thanks @florian-lefebvre! - Simplifies path operations of astro sync
#11771 49650a4 Thanks @florian-lefebvre! - Fixes an error thrown by astro sync when an astro:env virtual module is imported inside the Content Collections config
#11744 b677429 Thanks @bluwy! - Disables the WebSocket server when creating a Vite server for loading config files
#11725 6c1560f Thanks @ascorbic! - Prevents content layer importing node builtins in runtime
#11692 35af73a Thanks @matthewp! - Prevent errant HTML from crashing server islands
When 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 3c2f93b Thanks @florian-lefebvre! - Fixes a type issue when using the Content Layer in dev
#11657 a23c69d Thanks @bluwy! - Deprecates the option for route-generating files to export a dynamic value for prerender. Only static values are now supported (e.g. export const prerender = true or = 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 prerender exports from individual routing files:
// src/pages/blog/[slug].astro
- export const prerender = import.meta.env.PRERENDER
Instead, create an integration with the "astro:route:setup" hook and update the route's prerender option:
// astro.config.mjs
import { defineConfig } from 'astro/config';
import { loadEnv } from 'vite';
export default defineConfig({
integrations: [setPrerender()],
});
function setPrerender() {
const { PRERENDER } = loadEnv(process.env.NODE_ENV, process.cwd(), '');
return {
name: 'set-prerender',
hooks: {
'astro:route:setup': ({ route }) => {
if (route.component.endsWith('/blog/[slug].astro')) {
route.prerender = PRERENDER;
}
},
},
};
}
#11360 a79a8b0 Thanks @ascorbic! - Adds a new injectTypes() utility to the Integration API and refactors how type generation works
Use injectTypes() in the astro:config:done hook to inject types into your user's project by adding a new *.d.ts file.
The filename property will be used to generate a file at /.astro/integrations/<normalized_integration_name>/<normalized_filename>.d.ts and must end with ".d.ts".
The content property 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.
// my-integration/index.js
export default {
name: 'my-integration',
'astro:config:done': ({ injectTypes }) => {
injectTypes({
filename: 'types.d.ts',
content: "declare module 'virtual:my-integration' {}",
});
},
};
Codegen has been refactored. Although src/env.d.ts will continue to work as is, we recommend you update it:
- /// <reference types="astro/client" />
+ /// <reference path="../.astro/types.d.ts" />
- /// <reference path="../.astro/env.d.ts" />
- /// <reference path="../.astro/actions.d.ts" />
#11605 d3d99fb Thanks @jcayzac! - Adds a new property meta to Astro's built-in <Code /> component.
This allows you to provide a value for Shiki's meta attribute to pass options to transformers.
The following example passes an option to highlight lines 1 and 3 to Shiki's transformerMetaHighlight:
---
// src/components/Card.astro
import { Code } from 'astro:components';
import { transformerMetaHighlight } from '@shikijs/transformers';
---
<Code code={code} lang="js" transformers={[transformerMetaHighlight()]} meta="{1,3}" />
#11360 a79a8b0 Thanks @ascorbic! - Adds support for Intellisense features (e.g. code completion, quick hints) for your content collection entries in compatible editors under the experimental.contentIntellisense flag.
import { defineConfig } from 'astro';
export default defineConfig({
experimental: {
contentIntellisense: true,
},
});
When enabled, this feature will generate and add JSON schemas to the .astro directory 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-intellisense option in your editor, or passing the contentIntellisense: true initialization 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 a79a8b0 Thanks @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.
To try out the new Content Layer API, enable it in your Astro config:
import { defineConfig } from 'astro';
export default defineConfig({
experimental: {
contentLayer: true,
},
});
You can then create collections in your src/content/config.ts using the Content Layer API.
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() and file() loaders to handle your local Markdown, MDX, Markdoc, and JSON files:
// src/content/config.ts
import { defineCollection, z } from 'astro:content';
import { glob } from 'astro/loaders';
const blog = defineCollection({
// The ID is a slug generated from the path of the file relative to `base`
loader: glob({ pattern: '**/*.md', base: './src/data/blog' }),
schema: z.object({
title: z.string(),
description: z.string(),
publishDate: z.coerce.date(),
}),
});
export const collections = { blog };
You can then query using the existing content collections functions, and enjoy a simplified render() function to display your content:
---
import { getEntry, render } from 'astro:content';
const post = await getEntry('blog', Astro.params.slug);
const { Content } = await render(entry);
---
<Content />
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:
// src/content/config.ts
const countries = defineCollection({
loader: async () => {
const response = await fetch('https://restcountries.com/v3.1/all');
const data = await response.json();
// Must return an array of entries with an id property,
// or an object with IDs as keys and entries as values
return data.map((country) => ({
id: country.cca3,
...country,
}));
},
// optionally add a schema to validate the data and make it type-safe for users
// schema: z.object...
});
export const collections = { countries };
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.
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:
// src/content/config.ts
import { defineCollection } from 'astro:content';
import { feedLoader } from '@ascorbic/feed-loader';
const podcasts = defineCollection({
loader: feedLoader({
url: 'https://feeds.99percentinvisible.org/99percentinvisible',
}),
});
export const collections = { podcasts };
To find out more about using the Content Layer API, check out the Content Layer RFC and share your feedback.
#11716 f4057c1 Thanks @florian-lefebvre! - Fixes content types sync in dev
#11645 849e4c6 Thanks @bluwy! - Refactors internally to use node:util parseArgs instead of yargs-parser
#11712 791d809 Thanks @matthewp! - Fix mixed use of base + trailingSlash in Server Islands
#11709 3d8ae76 Thanks @matthewp! - Fix adapter causing Netlify to break
#11678 34da907 Thanks @ematipico! - Fixes a case where omitting a semicolon and line ending with carriage return - CRLF - in the prerender option could throw an error.
#11535 932bd2e Thanks @matthewp! - Encrypt server island props
Server 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 dc0a297 Thanks @billy-le! - Fixes Astro Actions input validation when using default values with a form input.
#11689 c7bda4c Thanks @ematipico! - Fixes an issue in the Astro actions, where the size of the generated cookie was exceeding the size permitted by the Set-Cookie header.
#11653 32be549 Thanks @florian-lefebvre! - Updates astro:env docs to reflect current developments and usage guidance
#11658 13b912a Thanks @bholmesdev! - Fixes orThrow() type when calling an Action without an input validator.
#11603 f31d466 Thanks @bholmesdev! - Improves user experience when render an Action result from a form POST request:
?_astroAction=NAME flag 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 action string 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 /success route when actions.signup succeeds. You can add /success to your action string like so:
<form method="POST" action={'/success' + actions.signup}></form>
/success.You can retrieve the action result from either page using the Astro.getActionResult() function.
This uses a temporary cookie to forward the action result to the next page. The cookie will be deleted when that page is rendered.
⚠ The action result is not encrypted. In general, we recommend returning minimal data from an action handler to a) avoid leaking sensitive information, and b) avoid unexpected render issues once the temporary cookie is deleted. For example, a login function may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.
#11648 589d351 Thanks @bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions.
#11600 09ec2ca Thanks @ArmandPhilippot! - Deprecates getEntryBySlug and getDataEntryById functions exported by astro:content in favor of getEntry.
#11593 81d7150 Thanks @bholmesdev! - Adds support for Date(), Map(), and Set() 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 196092a Thanks @abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold.
#11634 2716f52 Thanks @bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel.
#11628 9aaf58c Thanks @madbook! - Ensures consistent CSS chunk hashes across different environments
#11584 a65ffe3 Thanks @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.
callAction()is meant to trigger an action from server code.getActionResult()usage with form submissions remains unchanged.
---
import { actions } from 'astro:actions';
const result = await Astro.callAction(actions.searchPosts, {
searchTerm: Astro.url.searchParams.get('search'),
});
---
{
result.data &&
{
/* render the results */
}
}
If you call actions directly from server code, update function calls to use the Astro.callAction() wrapper for pages and context.callAction() for endpoints:
---
import { actions } from 'astro:actions';
- const result = await actions.searchPosts({ searchTerm: 'test' });
+ const result = await Astro.callAction(actions.searchPosts, { searchTerm: 'test' });
---
If you deploy with Cloudflare and added the nodejs_compat or nodejs_als flags for Actions, we recommend removing these:
compatibility_flags = [
- "nodejs_compat",
- "nodejs_als"
]
You can also remove node:async_hooks from the vite.ssr.external option in your astro.config file:
// astro.config.mjs
import { defineConfig } from 'astro/config';
export default defineConfig({
- vite: {
- ssr: {
- external: ["node:async_hooks"]
- }
- }
})
#11507 a62345f Thanks @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 e5e2d3e Thanks @alexanderniebuhr! - The experimental.contentCollectionJsonSchema feature 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 in src/content/config.ts using a library called zod-to-json-schema.
This feature requires you to manually set your schema's file path as the value for $schema in each data entry file of the collection:
{
"$schema": "../../../.astro/collections/authors.schema.json",
"name": "Armand",
"skills": ["Astro", "Starlight"]
}
Alternatively, you can set this value in your editor settings. For example, to set this value in VSCode's json.schemas setting, provide the path of files to match and the location of your JSON schema:
{
"json.schemas": [
{
"fileMatch": ["/src/content/authors/**"],
"url": "./.astro/collections/authors.schema.json"
}
]
}
If you were previously using this feature, please remove the experimental flag from your Astro config:
import { defineConfig } from 'astro'
export default defineConfig({
- experimental: {
- contentCollectionJsonSchema: true
- }
})
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 45ad326 Thanks @ematipico! - The experimental.rewriting feature introduced behind a flag in v4.8.0 is no longer experimental and is available for general use.
Astro.rewrite() and context.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 .astro page component to display a different page's content, such as fallback localized content:
---
// src/pages/es-cu/articles/introduction.astro
return Astro.rewrite('/es/articles/introduction');
---
Use context.rewrite() in endpoints, for example to reroute to a different page:
// src/pages/api.js
export function GET(context) {
if (!context.locals.allowed) {
return context.rewrite('/');
}
}
The middleware next() function now accepts a parameter with the same type as the rewrite() function. For example, with next("/"), you can call the next middleware function with a new Request.
// src/middleware.js
export function onRequest(context, next) {
if (!context.cookies.get('allowed')) {
return next('/'); // new signature
}
return next();
}
If you were previously using this feature, please remove the experimental flag from your Astro config:
// astro.config.mjs
export default defineConfig({
- experimental: {
- rewriting: true
- }
})
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.
#11509 dfbca06 Thanks @bluwy! - Excludes hoisted scripts and styles from Astro components imported with ?url or ?raw
#11561 904f1e5 Thanks @ArmandPhilippot! - Uses the correct pageSize default in page.size JSDoc comment
#11571 1c3265a Thanks @bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration 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.
import { actions } from 'astro:actions';
// Before
const { data, error } = await actions.like.safe();
// After
const { data, error } = await actions.like();
// Before
const newLikes = await actions.like();
// After
const newLikes = await actions.like.orThrow();
To migrate your existing action calls:
.safe from existing safe action calls.orThrow to existing unsafe action calls#11546 7f26de9 Thanks @ArmandPhilippot! - Remove "SSR Only" mention in Astro.redirect inline documentation and update reference link.
#11525 8068131 Thanks @ematipico! - Fixes a case where the build was failing when experimental.actions was enabled, an adapter was in use, and there were not actions inside the user code base.
#11574 e3f29d4 Thanks @Princesseuh! - Fixes line with the error not being properly highlighted in the error overlay
#11570 84189b6 Thanks @bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration as well if you're using React 19 features.
Updates the Astro Actions fallback to support action={actions.name} instead of using getActionProps(). This will submit a form to the server in zero-JS scenarios using a search parameter:
---
import { actions } from 'astro:actions';
---
<form action={actions.logOut}>
<!--output: action="?_astroAction=logOut"-->
<button>Log Out</button>
</form>
You may also construct form action URLs using string concatenation, or by using the URL() constructor, with an action's .queryString property:
---
import { actions } from 'astro:actions';
const confirmationUrl = new URL('/confirmation', Astro.url);
confirmationUrl.search = actions.queryString;
---
<form method="POST" action={confirmationUrl.pathname}>
<button>Submit</button>
</form>
getActionProps() is now deprecated. To use the new fallback pattern, remove the getActionProps() input from your form and pass your action function to the form action attribute:
---
import {
actions,
- getActionProps,
} from 'astro:actions';
---
+ <form method="POST" action={actions.logOut}>
- <form method="POST">
- <input {...getActionProps(actions.logOut)} />
<button>Log Out</button>
</form>
#11559 1953dbb Thanks @bryanwood! - Allows actions to return falsy values without an error
#11553 02c85b5 Thanks @ematipico! - Fixes an issue in content collection caching, where two documents with the same contents were generating an error during the build.
#11548 602c5bf Thanks @TheOtterlord! - Fixes astro add for packages with only prerelease versions
#11566 0dcef3a Thanks @Princesseuh! - Fixes DomException errors not being handled properly
#11529 504c383 Thanks @matthewp! - Fix server islands with trailingSlash: always
#11505 8ff7658 Thanks @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:
08:16:48 [404] (rewrite) /foo/about 200ms
08:22:13 [200] (rewrite) /about 23ms
#11506 026e8ba Thanks @sarah11918! - Fixes typo in documenting the slot="fallback" attribute for Server Islands experimental feature.
#11508 ca335e1 Thanks @cramforce! - Escapes HTML in serialized props
#11501 4db78ae Thanks @martrapp! - Adds the missing export for accessing the getFallback() function of the client site router.
#11486 9c0c849 Thanks @ematipico! - Adds a new function called addClientRenderer to the Container API.
This function should be used when rendering components using the client:* directives. The addClientRenderer API must be used
after the use of the addServerRenderer:
const container = await experimental_AstroContainer.create();
container.addServerRenderer({ renderer });
container.addClientRenderer({ name: '@astrojs/react', entrypoint: '@astrojs/react/client.js' });
const response = await container.renderToResponse(Component);
#11500 4e142d3 Thanks @Princesseuh! - Fixes inferRemoteSize type not working
#11496 53ccd20 Thanks @alfawal! - Hide the dev toolbar on window.print() (CTRL + P)
#11341 49b5145 Thanks @madcampos! - Adds support for Shiki's defaultColor option.
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: false in your Shiki config to apply throughout your site, or pass to Astro's built-in <Code> component to style an individual code block.
import { defineConfig } from 'astro/config';
export default defineConfig({
markdown: {
shikiConfig: {
themes: {
light: 'github-light',
dark: 'github-dark',
},
defaultColor: false,
},
},
});
---
import { Code } from 'astro:components';
---
<Code code={`const useMyColors = true`} lang="js" defaultColor={false} />
#11304 2e70741 Thanks @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.IntegrationHooks interface:
// your-integration/types.ts
declare global {
namespace Astro {
interface IntegrationHooks {
'myLib:eventHappened': (your: string, parameters: number) => Promise<void>;
}
}
}
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:
// your-integration/index.ts
import './types.ts';
export default (): AstroIntegration => {
return {
name: 'your-integration',
hooks: {
'astro:config:setup': async ({ config }) => {
for (const integration of config.integrations) {
await integration.hooks['myLib:eventHappened'].?('your values', 123);
}
},
}
}
}
Other integrations can also now declare your hooks:
// other-integration/index.ts
import 'your-integration/types.ts';
export default (): AstroIntegration => {
return {
name: 'other-integration',
hooks: {
'myLib:eventHappened': async (your, values) => {
// ...
},
},
};
};
#11305 d495df5 Thanks @matthewp! - Experimental Server Islands
Server 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 .astro component into a server island by adding the server:defer directive and optionally, fallback placeholder content:
---
import Avatar from '../components/Avatar.astro';
import GenericUser from '../components/GenericUser.astro';
---
<header>
<h1>Page Title</h1>
<div class="header-right">
<Avatar server:defer>
<GenericUser slot="fallback" />
</Avatar>
</div>
</header>
The server:defer directive can be used on any Astro component in a project using hybrid or server mode 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 output mode and adapter:
import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify';
export default defineConfig({
output: 'hybrid',
adapter: netlify(),
experimental: {
serverIslands: true,
},
});
For more information, see the server islands documentation.
#11482 7c9ed71 Thanks @Princesseuh! - Adds a --noSync parameter to the astro check command to skip the type-gen step. This can be useful when running astro check inside packages that have Astro components, but are not Astro projects
#11098 36e30a3 Thanks @itsmatteomanf! - Adds a new inferRemoteSize() 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 or getImage(). 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.
---
import { inferRemoteSize, Image } from 'astro:assets';
const imageUrl = 'https://...';
const { width, height } = await inferRemoteSize(imageUrl);
---
<Image src={imageUrl} width={width / 2} height={height} densities={[1.5, 2]} />
#11391 6f9b527 Thanks @ARipeAppleByYoursTruly! - Adds Shiki's defaultColor option to the <Code /> component, giving you more control in applying multiple themes
#11176 a751458 Thanks @tsawada! - Adds two new values to the pagination page prop: page.first and page.last for accessing the URLs of the first and last pages.
#11477 7e9c4a1 Thanks @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 ca969d5 Thanks @florian-lefebvre! - Fixes a case where invalid astro:env variables at runtime would not throw correctly
#11489 061f1f4 Thanks @ematipico! - Move root inside the manifest and make serialisable
#11415 e9334d0 Thanks @florian-lefebvre! - Refactors how sync works and when it's called. Fixes an issue with astro:env types in dev not being generated
#11478 3161b67 Thanks @bluwy! - Supports importing Astro components with Vite queries, like ?url, ?raw, and ?direct
#11491 fe3afeb Thanks @matthewp! - Fix for Server Islands in Vercel adapter
Vercel, and probably other adapters only allow pre-defined routes. This makes it so that the astro:build:done hook includes the _server-islands/ route as part of the route data, which is used to configure available routes.
#11483 34f9c25 Thanks @Princesseuh! - Fixes Astro not working on low versions of Node 18 and 20
Updated dependencies [49b5145]:
#11459 bc2e74d Thanks @mingjunlu! - Fixes false positive audit warnings on elements with the role "tabpanel".
#11472 cb4e6d0 Thanks @delucis! - Avoids targeting all files in the src/ directory for eager optimization by Vite. After this change, only JSX, Vue, Svelte, and Astro components get scanned for early optimization.
#11387 b498461 Thanks @bluwy! - Fixes prerendering not removing unused dynamic imported chunks
#11437 6ccb30e Thanks @NuroDev! - Fixes a case where Astro's config experimental.env.schema keys did not allow numbers. Numbers are still not allowed as the first character to be able to generate valid JavaScript identifiers
#11439 08baf56 Thanks @bholmesdev! - Expands the isInputError() utility from astro:actions to accept errors of any type. This should now allow type narrowing from a try / catch block.
// example.ts
import { actions, isInputError } from 'astro:actions';
try {
await actions.like(new FormData());
} catch (error) {
if (isInputError(error)) {
console.log(error.fields);
}
}
#11452 0e66849 Thanks @FugiTech! - Fixes an issue where using .nullish() in a formdata Astro action would always parse as a string
#11438 619f07d Thanks @bholmesdev! - Exposes utility types from astro:actions for the defineAction handler (ActionHandler) and the ActionError code (ActionErrorCode).
#11456 17e048d Thanks @RickyC0626! - Fixes astro dev --open unexpected behavior that spawns a new tab every time a config file is saved
#11337 0a4b31f Thanks @florian-lefebvre! - Adds a new property experimental.env.validateSecrets to allow validating private variables on the server.
By default, this is set to false and 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.
// astro.config.mjs
import { defineConfig, envField } from 'astro/config';
export default defineConfig({
experimental: {
env: {
schema: {
// ...
},
validateSecrets: true,
},
},
});
#11443 ea4bc04 Thanks @bholmesdev! - Expose new ActionReturnType utility from astro:actions. This infers the return type of an action by passing typeof actions.name as a type argument. This example defines a like action that returns likes as an object:
// actions/index.ts
import { defineAction } from 'astro:actions';
export const server = {
like: defineAction({
handler: () => {
/* ... */
return { likes: 42 };
},
}),
};
In your client code, you can infer this handler return value with ActionReturnType:
// client.ts
import { actions, ActionReturnType } from 'astro:actions';
type LikesResult = ActionReturnType<typeof actions.like>;
// -> { likes: number }
#11436 7dca68f Thanks @bholmesdev! - Fixes astro:actions autocompletion for the defineAction accept property
#11455 645e128 Thanks @florian-lefebvre! - Improves astro:env invalid variables errors
#11362 93993b7 Thanks @ematipico! - Fixes an issue where creating manually the i18n middleware could break the logic of the functions of the virtual module astro:i18n
#11349 98d9ce4 Thanks @ematipico! - Fixes an issue where Astro didn't throw an error when Astro.rewrite was used without providing the experimental flag
#11352 a55ee02 Thanks @ematipico! - Fixes an issue where the rewrites didn't update the status code when using manual i18n routing.
#11388 3a223b4 Thanks @mingjunlu! - Adjusts the color of punctuation in error overlay.
#11369 e6de11f Thanks @bluwy! - Fixes attribute rendering for non-boolean attributes with boolean values
#11347 33bdc54 Thanks @bluwy! - Fixes installed packages detection when running astro check
#11327 0df8142 Thanks @ematipico! - Fixes an issue with the container APIs where a runtime error was thrown during the build, when using pnpm as package manager.
#11335 4c4741b Thanks @ematipico! - Reverts #11292, which caused a regression to the input type
#11326 41121fb Thanks @florian-lefebvre! - Fixes a case where running astro sync when using the experimental astro:env feature would fail if environment variables were missing
#11338 9752a0b Thanks @zaaakher! - Fixes svg icon margin in devtool tooltip title to look coherent in rtl and ltr layouts
#11331 f1b78a4 Thanks @bluwy! - Removes resolve package and simplify internal resolve check
#11339 8fdbf0e Thanks @matthewp! - Remove non-fatal errors from telemetry
Previously 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.
#11308 44c61dd Thanks @ematipico! - Fixes an issue where custom 404.astro and 500.astro were not returning the correct status code when rendered inside a rewriting cycle.
#11302 0622567 Thanks @martrapp! - Fixes an issue with the view transition router when redirecting to an URL with different origin.
Updated dependencies [b6afe6a, 41064ce]:
#11197 4b46bd9 Thanks @braebo! - Adds ShikiTransformer support to the <Code /> component with a new transformers prop.
Note that transformers only applies classes and you must provide your own CSS rules to target the elements of your code block.
---
import { transformerNotationFocus } from '@shikijs/transformers';
import { Code } from 'astro:components';
const code = `const foo = 'hello'
const bar = ' world'
console.log(foo + bar) // [!code focus]
`;
---
<Code {code} lang="js" transformers={[transformerNotationFocus()]} />
<style is:global>
pre.has-focused .line:not(.focused) {
filter: blur(1px);
}
</style>
#11134 9042be0 Thanks @florian-lefebvre! - Improves the developer experience of the 500.astro file by passing it a new error prop.
When an error is thrown, the special src/pages/500.astro page now automatically receives the error as a prop. This allows you to display more specific information about the error on a custom 500 page.
---
// src/pages/500.astro
interface Props {
error: unknown;
}
const { error } = Astro.props;
---
<div>{error instanceof Error ? error.message : 'Unknown error'}</div>
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.
#11280 fd3645f Thanks @ascorbic! - Fixes a bug that prevented cookies from being set when using experimental rewrites
#11275 bab700d Thanks @syhily! - Drop duplicated brackets in data collections schema generation.
#11272 ea987d7 Thanks @ematipico! - Fixes a case where rewriting / would cause an issue, when trailingSlash was set to "never".
#11272 ea987d7 Thanks @ematipico! - Reverts a logic where it wasn't possible to rewrite /404 in static mode. It's now possible again
#11264 5a9c9a6 Thanks @Fryuni! - Fixes type generation for empty content collections
#11279 9a08d74 Thanks @ascorbic! - Improves type-checking and error handling to catch case where an image import is passed directly to getImage()
#11292 7f8f347 Thanks @jdtjenkins! - Fixes a case where defineAction autocomplete for the accept prop would not show "form" as a possible value
#11273 cb4d078 Thanks @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 f4b029b Thanks @ascorbic! - Fixes an issue that would break Astro.request.url and Astro.request.headers in astro dev if HTTP/2 was enabled.
HTTP/2 is now enabled by default in astro dev if https is configured in the Vite config.
#11213 94ac7ef Thanks @florian-lefebvre! - Removes the PUBLIC_ prefix constraint for astro:env public variables
#11213 94ac7ef Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental astro:env feature only
Server secrets specified in the schema must now be imported from astro:env/server. Using getSecret() is no longer required to use these environment variables in your schema:
- import { getSecret } from 'astro:env/server'
- const API_SECRET = getSecret("API_SECRET")
+ import { API_SECRET } from 'astro:env/server'
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 4385bf7 Thanks @ematipico! - Adds a new function called addServerRenderer to 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:
import type { APIRoute } from 'astro';
import { experimental_AstroContainer } from 'astro/container';
import reactRenderer from '@astrojs/react/server.js';
import vueRenderer from '@astrojs/vue/server.js';
import ReactComponent from '../components/button.jsx';
import VueComponent from '../components/button.vue';
// MDX runtime is contained inside the Astro core
import mdxRenderer from 'astro/jsx/server.js';
// In case you need to import a custom renderer
import customRenderer from '../renderers/customRenderer.js';
export const GET: APIRoute = async (ctx) => {
const container = await experimental_AstroContainer.create();
container.addServerRenderer({ renderer: reactRenderer });
container.addServerRenderer({ renderer: vueRenderer });
container.addServerRenderer({ renderer: customRenderer });
// You can pass a custom name too
container.addServerRenderer({
name: 'customRenderer',
renderer: customRenderer,
});
const vueComponent = await container.renderToString(VueComponent);
return await container.renderToResponse(Component);
};
#11249 de60c69 Thanks @markgaze! - Fixes a performance issue with JSON schema generation
#11242 e4fc2a0 Thanks @ematipico! - Fixes a case where the virtual module astro:container wasn't resolved
#11236 39bc3a5 Thanks @ascorbic! - Fixes a case where symlinked content collection directories were not correctly resolved
#11258 d996db6 Thanks @ascorbic! - Adds a new error RewriteWithBodyUsed that throws when Astro.rewrite is used after the request body has already been read.
#11243 ba2b14c Thanks @V3RON! - Fixes a prerendering issue for libraries in node_modules when a folder with an underscore is in the path.
#11244 d07d2f7 Thanks @ematipico! - Improves the developer experience of the custom 500.astro page 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.astro page.
Now, the development server will display the 500.astro and the original error is logged in the console.
#11240 2851b0a Thanks @ascorbic! - Ignores query strings in module identifiers when matching ".astro" file extensions in Vite plugin
#11245 e22be22 Thanks @bluwy! - Refactors prerendering chunk handling to correctly remove unused code during the SSR runtime
#11231 58d7dbb Thanks @ematipico! - Fixes a regression for getViteConfig, where the inline config wasn't merged in the final config.
#11228 1e293a1 Thanks @ascorbic! - Updates getCollection() to always return a cloned array
#11207 7d9aac3 Thanks @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 75a8fe7 Thanks @ematipico! - Improve error message when using getLocaleByPath on path that doesn't contain any locales.
#11195 0a6ab6f Thanks @florian-lefebvre! - Adds support for enums to astro:env
You can now call envField.enum:
import { defineConfig, envField } from 'astro/config';
export default defineConfig({
experimental: {
env: {
schema: {
API_VERSION: envField.enum({
context: 'server',
access: 'secret',
values: ['v1', 'v2'],
}),
},
},
},
});
#11210 66fc028 Thanks @matthewp! - Close the iterator only after rendering is complete
#11195 0a6ab6f Thanks @florian-lefebvre! - Adds additional validation options to astro:env
astro:env schema datatypes string and number now have new optional validation rules:
import { defineConfig, envField } from 'astro/config';
export default defineConfig({
experimental: {
env: {
schema: {
FOO: envField.string({
// ...
max: 32,
min: 3,
length: 12,
url: true,
includes: 'foo',
startsWith: 'bar',
endsWith: 'baz',
}),
BAR: envField.number({
// ...
gt: 2,
min: 3,
lt: 10,
max: 9,
int: true,
}),
},
},
},
});
#11211 97724da Thanks @matthewp! - Let middleware handle the original request URL
#10607 7327c6a Thanks @frankbits! - Fixes an issue where a leading slash created incorrect conflict resolution between pages generated from static routes and catch-all dynamic routes
#11198 8b9a499 Thanks @florian-lefebvre! - Fixes a case where astro:env getSecret would not retrieve environment variables properly in dev and build modes
#11206 734b98f Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental astro:env feature only
Updates the adapter astro:env entrypoint from astro:env/setup to astro/env/setup
#11205 8c45391 Thanks @Nin3lee! - Fixes a typo in the config reference
#10974 2668ef9 Thanks @florian-lefebvre! - Adds experimental support for the astro:env API.
The astro:env API 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 /client or /server module:
---
import { PUBLIC_APP_ID } from 'astro:env/client';
import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
const API_TOKEN = getSecret('API_TOKEN');
const data = await fetch(`${PUBLIC_API_URL}/users`, {
method: 'POST',
headers: {
'Content-Type': 'application/json',
Authorization: `Bearer ${API_TOKEN}`,
},
body: JSON.stringify({ appId: PUBLIC_APP_ID }),
});
---
To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:
// astro.config.mjs
import { defineConfig, envField } from 'astro/config';
export default defineConfig({
experimental: {
env: {
schema: {
PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
API_SECRET: envField.string({ context: 'server', access: 'secret' }),
},
},
},
});
There are three kinds of environment variables, determined by the combination of context (client or server) and access (private or public) settings defined in your env.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/client module:
import { PUBLIC_API_URL } from 'astro:env/client';
Public server variables: These variables end up in your final server bundle and can be accessed on the server through the astro:env/server module:
import { PUBLIC_PORT } from 'astro:env/server';
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 the astro:env/server module:
import { getSecret } from 'astro:env/server';
const API_SECRET = getSecret('API_SECRET'); // typed
const SECRET_NOT_IN_SCHEMA = getSecret('SECRET_NOT_IN_SCHEMA'); // string | undefined
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" and access: "secret" in your schema.
To learn more, check out the documentation.
#11192 58b10a0 Thanks @liruifengv! - Improves DX by throwing the original AstroUserError when an error is thrown inside a .mdx file.
#11136 35ef53c Thanks @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 803dd80 Thanks @ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.
import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import ReactWrapper from '../src/components/ReactWrapper.astro';
import { loadRenderers } from 'astro:container';
import { getContainerRenderer } from '@astrojs/react';
test('ReactWrapper with react renderer', async () => {
const renderers = await loadRenderers([getContainerRenderer()]);
const container = await AstroContainer.create({
renderers,
});
const result = await container.renderToString(ReactWrapper);
expect(result).toContain('Counter');
expect(result).toContain('Count: <!-- -->5');
});
#11144 803dd80 Thanks @ematipico! - BREAKING CHANGE to the experimental Container API only
Changes the type of the renderers option of the AstroContainer::create function and adds a dedicated function loadRenderers() 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():
import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import ReactWrapper from '../src/components/ReactWrapper.astro';
import { loadRenderers } from "astro:container";
import { getContainerRenderer } from "@astrojs/react";
test('ReactWrapper with react renderer', async () => {
+ const renderers = await loadRenderers([getContainerRenderer()])
- const renderers = [
- {
- name: '@astrojs/react',
- clientEntrypoint: '@astrojs/react/client.js',
- serverEntrypoint: '@astrojs/react/server.js',
- },
- ];
const container = await AstroContainer.create({
renderers,
});
const result = await container.renderToString(ReactWrapper);
expect(result).toContain('Counter');
expect(result).toContain('Count: <!-- -->5');
});
The new loadRenderers() helper function is available from astro:container, a virtual module that can be used when running the Astro container inside vite.
#11136 35ef53c Thanks @ematipico! - It's not possible anymore to use Astro.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 6e29a17 Thanks @matthewp! - Fixes a case where Astro.url would be incorrect when having build.format set to 'preserve' in the Astro config
#11182 40b0b4d Thanks @ematipico! - Fixes an issue where Astro.rewrite wasn't carrying over the body of a Request in on-demand pages.
#11194 97fbe93 Thanks @ematipico! - Fixes an issue where the function getViteConfig wasn't returning the correct merged Astro configuration
#11171 ff8004f Thanks @Princesseuh! - Guard globalThis.astroAsset usage in proxy code to avoid errors in wonky situations
#11178 1734c49 Thanks @theoephraim! - Improves isPromise utility to check the presence of then on an object before trying to access it - which can cause undesired side-effects on Proxy objects
#11183 3cfa2ac Thanks @66Leo66! - Suggest pnpm dlx instead of pnpx in update check.
#11147 2d93902 Thanks @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 19df89f Thanks @ematipico! - Fixes an internal error that prevented the AstroContainer to render the Content component.
You can now write code similar to the following to render content collections:
const entry = await getEntry(collection, slug);
const { Content } = await entry.render();
const content = await container.renderToString(Content);
#11170 ba20c71 Thanks @matthewp! - Retain client scripts in content cache
#11138 98e0372 Thanks @ematipico! - You can now pass props when rendering a component using the Container APIs:
import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import Card from '../src/components/Card.astro';
const container = await AstroContainer.create();
const result = await container.renderToString(Card, {
props: {
someState: true,
},
});
#11051 12a1bcc Thanks @ematipico! - Introduces an experimental Container API to render .astro components 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 the Response emitted 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:
import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import { expect, test } from 'vitest';
import Card from '../src/components/Card.astro';
test('Card with slots', async () => {
const container = await AstroContainer.create();
const result = await container.renderToString(Card, {
slots: {
default: 'Card content',
},
});
expect(result).toContain('This is a card');
expect(result).toContain('Card content');
});
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 2d4c8fa Thanks @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 security option in astro.config.mjs. If you were previously using the experimental version of this feature, also delete the experimental flag:
export default defineConfig({
- experimental: {
- security: {
- csrfProtection: {
- origin: true
- }
- }
- },
+ security: {
+ checkOrigin: true
+ }
})
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, DELETE and PUT with 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 security configuration docs.
#11022 be68ab4 Thanks @ematipico! - The i18nDomains routing 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 site configured.
If you were using this feature, please remove the experimental flag from your Astro config:
import { defineConfig } from 'astro'
export default defineConfig({
- experimental: {
- i18nDomains: true,
- }
})
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 8ca7c73 Thanks @bholmesdev! - Adds two new functions experimental_getActionState() and experimental_withState() to support the React 19 useActionState() hook when using Astro Actions. This introduces progressive enhancement when calling an Action with the withState() utility.
This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the experimental_withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:
import { actions } from 'astro:actions';
import { experimental_withState } from '@astrojs/react/actions';
export function Like({ postId }: { postId: string }) {
const [state, action, pending] = useActionState(
experimental_withState(actions.like),
0, // initial likes
);
return (
<form action={action}>
<input type="hidden" name="postId" value={postId} />
<button disabled={pending}>{state} ❤️</button>
</form>
);
}
You can also access the state stored by useActionState() from your action handler. Call experimental_getActionState() with the API context, and optionally apply a type to the result:
import { defineAction, z } from 'astro:actions';
import { experimental_getActionState } from '@astrojs/react/actions';
export const server = {
like: defineAction({
input: z.object({
postId: z.string(),
}),
handler: async ({ postId }, ctx) => {
const currentLikes = experimental_getActionState<number>(ctx);
// write to database
return currentLikes + 1;
},
}),
};
#11101 a6916e4 Thanks @linguofeng! - Updates Astro's code for adapters to use the header x-forwarded-for to initialize the clientAddress.
To take advantage of the new change, integration authors must upgrade the version of Astro in their adapter peerDependencies to 4.9.0.
#11071 8ca7c73 Thanks @bholmesdev! - Adds compatibility for Astro Actions in the React 19 beta. Actions can be passed to a form action prop directly, and Astro will automatically add metadata for progressive enhancement.
import { actions } from 'astro:actions';
function Like() {
return (
<form action={actions.like}>
<button type="submit">Like</button>
</form>
);
}
#11088 9566fa0 Thanks @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:actions as you would for client actions:
---
// src/pages/blog/[postId].astro
import { actions } from 'astro:actions';
await actions.like({ postId: Astro.params.postId });
---
#11112 29a8650 Thanks @bholmesdev! - Deprecate the getApiContext() function. API Context can now be accessed from the second parameter to your Action handler():
// src/actions/index.ts
import {
defineAction,
z,
- getApiContext,
} from 'astro:actions';
export const server = {
login: defineAction({
input: z.object({ id: z.string }),
+ handler(input, context) {
const user = context.locals.auth(input.id);
return user;
}
}),
}
#11073 f5c8fee Thanks @matthewp! - Prevent cache content from being left in dist folder
When contentCollectionsCache is enabled temporary cached content is copied into the outDir for processing. This fixes it so that this content is cleaned out, along with the rest of the temporary build JS.
#11054 f6b171e Thanks @bholmesdev! - Respect error status when handling Actions with a progressive fallback.
#11092 bfe9c73 Thanks @duckycoding-dev! - Change slot attribute of IntrinsicAttributes to match the definition of HTMLAttributes's own slot attribute of type string | undefined | null
#10875 b5f95b2 Thanks @W1M0R! - Fixes a typo in a JSDoc annotation
#11111 a5d79dd Thanks @bholmesdev! - Fix unexpected headers warning on prerendered routes when using Astro Actions.
#11081 af42e05 Thanks @V3RON! - Correctly position inspection tooltip in RTL mode
When 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.
9637014 Thanks @bluwy! - Fixes regression when handling hoisted scripts from content collections#11065 1f988ed Thanks @ematipico! - Fixes a bug in the Astro rewrite logic, where rewriting the index with parameters - next("/?foo=bar") - didn't work as expected.
#10924 3a0c02a Thanks @Its-Just-Nans! - Handle image-size errors by displaying a clearer message
#11058 749a7ac Thanks @matthewp! - Fix streaming in Node.js fast path
#11052 a05ca38 Thanks @florian-lefebvre! - Fixes a case where rewriting would conflict with the actions internal middleware
#11062 16f12e4 Thanks @ematipico! - Fixes a bug where astro build didn't create custom 404.html and 500.html when a certain combination of i18n options was applied
#10965 a8f0372 Thanks @Elias-Chairi! - Update generator.ts to allow %23 (#) in dynamic urls
#11069 240a70a Thanks @ematipico! - Improves debug logging for on-demand pages
#11026 8dfb1a2 Thanks @bluwy! - Skips rendering script tags if it's inlined and empty when experimental.directRenderScript is enabled
#11043 d0d1710 Thanks @bholmesdev! - Fixes minor type issues in actions component example
#10999 5f353e3 Thanks @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 to fetch().prefetch() programmatic API's with option is deprecated in favour of an automatic approach that will also try to use <link rel="prefetch> if supported, or will fall back to fetch().This change shouldn't affect most sites and should instead make prefetching more effective.
#11041 6cc3fb9 Thanks @bholmesdev! - Fixes 500 errors when sending empty params or returning an empty response from an action.
#11028 771d1f7 Thanks @bholmesdev! - Throw on missing server output when using Astro Actions.
#11029 bd34452 Thanks @bholmesdev! - Actions: include validation error in thrown error message for debugging.
#11046 086694a Thanks @HiDeoo! - Fixes getViteConfig() type definition to allow passing an inline Astro configuration as second argument
#11026 8dfb1a2 Thanks @bluwy! - Fixes CSS handling if imported in a script tag in an Astro file when experimental.directRenderScript is enabled
#11020 2e2d6b7 Thanks @xsynaptic! - Add type declarations for import.meta.env.ASSETS_PREFIX when defined as an object for handling different file types.
#11030 18e7f33 Thanks @bholmesdev! - Actions: Fix missing message for custom Action errors.
#10981 ad9227c Thanks @mo! - Adds deprecated HTML attribute "name" to the list of valid attributes. This attribute has been replaced by the global id attribute in recent versions of HTML.
#11013 4ea38e7 Thanks @QingXia-Ela! - Prevents unhandledrejection error when checking for latest Astro version
#11034 5f2dd45 Thanks @arganaphang! - Add popovertargetaction to the attribute that can be passed to the button and input element
7418bb0 Thanks @bholmesdev! - Fix locals access from action handlers#10990 4161a2a Thanks @liruifengv! - fix incorrect actions path on windows
#10979 6fa89e8 Thanks @BryceRussell! - Fix loading of non-index routes that end with index.html
#10987 05db5f7 Thanks @ematipico! - Fix a regression where the flag experimental.rewriting was marked mandatory. Is is now optional.
#10975 6b640b3 Thanks @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> element
#10935 ddd8e49 Thanks @bluwy! - Exports astro/jsx/rehype.js with utilities to generate an Astro metadata object
#10625 698c2d9 Thanks @goulvenclech! - Adds the ability for multiple pages to use the same component as an entrypoint when building an Astro integration. This change is purely internal, and aligns the build process with the behaviour in the development server.
#10906 7bbd664 Thanks @Princesseuh! - Adds a new radio checkbox component to the dev toolbar UI library (astro-dev-toolbar-radio-checkbox)
#10963 61f47a6 Thanks @delucis! - Adds support for passing an inline Astro configuration object to getViteConfig()
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.
// vitest.config.ts
import { getViteConfig } from 'astro/config';
export default getViteConfig(
/* Vite configuration */
{ test: {} },
/* Astro configuration */
{
site: 'https://example.com',
trailingSlash: 'never',
},
);
#10867 47877a7 Thanks @ematipico! - Adds experimental rewriting in Astro with a new rewrite() function and the middleware next() function.
The feature is available via an experimental flag in astro.config.mjs:
export default defineConfig({
experimental: {
rewriting: true,
},
});
When enabled, you can use rewrite() to render another page without changing the URL of the browser in Astro pages and endpoints.
---
// src/pages/dashboard.astro
if (!Astro.props.allowed) {
return Astro.rewrite('/');
}
---
// src/pages/api.js
export function GET(ctx) {
if (!ctx.locals.allowed) {
return ctx.rewrite('/');
}
}
The middleware next() function now accepts a parameter with the same type as the rewrite() function. For example, with next("/"), you can call the next middleware function with a new Request.
// src/middleware.js
export function onRequest(ctx, next) {
if (!ctx.cookies.get('allowed')) {
return next('/'); // new signature
}
return next();
}
NOTE: please read the RFC to understand the current expectations of the new APIs.
#10858 c0c509b Thanks @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 output property and add the actions flag to the experimental object:
{
output: 'hybrid', // or 'server'
experimental: {
actions: true,
},
}
Declare all your actions in src/actions/index.ts. This file is the global actions handler.
Define an action using the defineAction() utility from the astro:actions module. These accept the handler property to define your server-side request handler. If your action accepts arguments, apply the input property to validate parameters with Zod.
This example defines two actions: like and comment. The like action accepts a JSON object with a postId string, while the comment action accepts FormData with postId, author, and body strings. Each handler updates your database and return a type-safe response.
// src/actions/index.ts
import { defineAction, z } from 'astro:actions';
export const server = {
like: defineAction({
input: z.object({ postId: z.string() }),
handler: async ({ postId }) => {
// update likes in db
return likes;
},
}),
comment: defineAction({
accept: 'form',
input: z.object({
postId: z.string(),
body: z.string(),
}),
handler: async ({ postId }) => {
// insert comments in db
return comment;
},
}),
};
Then, call an action from your client components using the actions object from astro:actions. You can pass a type-safe object when using JSON, or a FormData object when using accept: 'form' in your action definition:
// src/components/blog.tsx
import { actions } from 'astro:actions';
import { useState } from 'preact/hooks';
export function Like({ postId }: { postId: string }) {
const [likes, setLikes] = useState(0);
return (
<button
onClick={async () => {
const newLikes = await actions.like({ postId });
setLikes(newLikes);
}}
>
{likes} likes
</button>
);
}
export function Comment({ postId }: { postId: string }) {
return (
<form
onSubmit={async (e) => {
e.preventDefault();
const formData = new FormData(e.target);
const result = await actions.blog.comment(formData);
// handle result
}}
>
<input type="hidden" name="postId" value={postId} />
<label for="author">Author</label>
<input id="author" type="text" name="author" />
<textarea rows={10} name="body"></textarea>
<button type="submit">Post</button>
</form>
);
}
For a complete overview, and to give feedback on this experimental API, see the Actions RFC.
#10906 7bbd664 Thanks @Princesseuh! - Adds a new buttonBorderRadius property to the astro-dev-toolbar-button component for the dev toolbar component library. This property can be useful to make a fully rounded button with an icon in the center.
#10977 59571e8 Thanks @BryceRussell! - Improve error message when accessing clientAddress on prerendered routes
#10935 ddd8e49 Thanks @bluwy! - Improves the error message when failed to render MDX components
#10917 3412535 Thanks @jakobhellermann! - Fixes a case where the local server would crash when the host also contained the port, eg. with X-Forwarded-Host: hostname:8080 and X-Forwarded-Port: 8080 headers
#10959 685fc22 Thanks @bluwy! - Refactors internal handling of styles and scripts for content collections to improve build performance
#10889 4d905cc Thanks @matthewp! - Preserve content modules properly in cache
#10955 2978287 Thanks @florian-lefebvre! - Handles AstroUserErrors thrown while syncing content collections and exports BaseSchema and CollectionConfig types
#10911 a86dc9d Thanks @bluwy! - Skips adding CSS dependencies of CSS Vite modules as style tags in the HTML
#10900 36bb3b6 Thanks @martrapp! - Detects overlapping navigation and view transitions and automatically aborts all but the most recent one.
#10933 007d17f Thanks @Princesseuh! - Fixes app.toggleState not working correctly
#10931 4ce5ced Thanks @ktym4a! - Fixes toggleNotification()'s parameter type for the notification level not using the proper levels
#10665 7b4f284 Thanks @Princesseuh! - Adds new utilities to ease the creation of toolbar apps including defineToolbarApp to make it easier to define your toolbar app and app and server helpers 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-toggled event and manually typing the value in the callback, you can now use the onAppToggled method. Additionally, communicating with the server does not require knowing any of the Vite APIs anymore, as a new server object is passed to the init function that contains easy to use methods for communicating with the server.
import { defineToolbarApp } from "astro/toolbar";
export default defineToolbarApp({
init(canvas, app, server) {
- app.addEventListener("app-toggled", (e) => {
- console.log(`App is now ${state ? "enabled" : "disabled"}`);.
- });
+ app.onToggled(({ state }) => {
+ console.log(`App is now ${state ? "enabled" : "disabled"}`);
+ });
- if (import.meta.hot) {
- import.meta.hot.send("my-app:my-client-event", { message: "world" });
- }
+ server.send("my-app:my-client-event", { message: "world" })
- if (import.meta.hot) {
- import.meta.hot.on("my-server-event", (data: {message: string}) => {
- console.log(data.message);
- });
- }
+ server.on<{ message: string }>("my-server-event", (data) => {
+ console.log(data.message); // data is typed using the type parameter
+ });
},
})
Server helpers are also available on the server side, for use in your integrations, through the new toolbar object:
"astro:server:setup": ({ toolbar }) => {
toolbar.on<{ message: string }>("my-app:my-client-event", (data) => {
console.log(data.message);
toolbar.send("my-server-event", { message: "hello" });
});
}
This is a backwards compatible change and 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 6fc4c0e Thanks @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 checkUpdates or setting the ASTRO_DISABLE_UPDATE_CHECK environment variable to false.
#10762 43ead8f Thanks @bholmesdev! - Enables type checking for JavaScript files when using the strictest TS config. This ensures consistency with Astro's other TS configs, and fixes type checking for integrations like Astro DB when using an astro.config.mjs.
If you are currently using the strictest preset and would like to still disable .js files, set allowJS: false in your tsconfig.json.
#10861 b673bc8 Thanks @mingjunlu! - Fixes an issue where astro build writes type declaration files to outDir when it's outside of root directory.
#10684 8b59d5d Thanks @PeterDraex! - Update sharp to 0.33 to fix issue with Alpine Linux
#10846 3294f7a Thanks @matthewp! - Prevent getCollection breaking in vitest
#10856 30cf82a Thanks @robertvanhoesel! - Prevents inputs with a name attribute of action or method to break ViewTransitions' form submission
#10833 8d5f3e8 Thanks @renovate! - Updates esbuild dependency to v0.20. This should not affect projects in most cases.
#10801 204b782 Thanks @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:
- 
+ 
<!-- This dog lives in the same folder as my article! -->
#10841 a2df344 Thanks @martrapp! - Due to regression on mobile WebKit browsers, reverts a change made for JavaScript animations during view transitions.
#10799 dc74afca9f5eebc2d61331298d6ef187d92051e0 Thanks @martrapp! - Fixes an issue with persisted non-text input fields that have the focus during view transition navigation.
#10773 35e43ecdaae7adc4b9a0b974192a033568cfb3f0 Thanks @lilnasy! - Improves performance for frequent use of small components.
#10763 63132771373ce1510be3e8814897accc0bf62ef8 Thanks @matthewp! - Invalidate CC cache manifest when lockfile or config changes
#10811 77822a822b04b5113726f713df104e8667333c59 Thanks @AvinashReddy3108! - Update list of available integrations in the astro add CLI help.
#10732 a92e263beb6e0166f1f13c97803d1861793e2a99 Thanks @rishi-raj-jain! - Correctly sets build.assets directory during vite config setup
#10776 1607face67051b16d4648555f1001b2a9308e377 Thanks @fshafiee! - Fixes cookies type inference
#10796 90669472df3a05b33f0de46fd2d039e3eba7f7dd Thanks @bluwy! - Disables streaming when rendering site with output: "static"
#10782 b0589d05538fcc77dd3c38198bf93f3548362cd8 Thanks @nektro! - Handles possible null value when calling which-pm during dynamic package installation
#10774 308b5d8c122f44e7724bb2f3ad3aa5c43a83e584 Thanks @Princesseuh! - Fixes astro add sometimes modifying baseUrl unintentionally
#10783 4dbd545304d1a8af903c8c97f237eb55c988c40b Thanks @jurajkapsz! - Fixes Picture component specialFormatsFallback fallback check
#10775 06843121450899ecf0390ca4efaff6c9a6fe0f75 Thanks @Princesseuh! - Fixes assets endpoint in serverless returning 404 in certain situations where the website might be under a protected route
#10787 699f4559a279b374bddb3e5e48c72afe2709e8e7 Thanks @martrapp! - Fixes a timing issue in the view transition simulation.
#10708 742866c5669a2be4f8b5a4c861cadb933c381415 Thanks @horo-fox! - Limits parallel imports within getCollection() to prevent EMFILE errors when accessing files
#10755 c6d59b6fb7db20af957a8706c8159c50619235ef Thanks @ematipico! - Fixes a case where the i18n fallback failed to correctly redirect to the index page with SSR enabled
#10591 39988ef8e2c4c4888543c973e06d9b9939e4ac95 Thanks @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 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.
This change is in line with Astro's Node.js support policy.
#10678 2e53b5fff6d292b7acdf8c30a6ecf5e5696846a1 Thanks @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:
import { defineConfig } from 'astro/config';
export default defineConfig({
experimental: {
security: {
csrfProtection: {
origin: true,
},
},
},
});
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 440681e7b74511a17b152af0fd6e0e4dc4014025 Thanks @ematipico! - Adds a new i18n routing option manual to allow you to write your own i18n middleware:
import { defineConfig } from 'astro/config';
// astro.config.mjs
export default defineConfig({
i18n: {
locales: ['en', 'fr'],
defaultLocale: 'fr',
routing: 'manual',
},
});
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, and redirectToFallback:
// middleware.js
import { redirectToDefaultLocale } from 'astro:i18n';
export const onRequest = defineMiddleware(async (context, next) => {
if (context.url.startsWith('/about')) {
return next();
} else {
return redirectToDefaultLocale(context, 302);
}
});
Also adds a middleware function that manually creates Astro's i18n middleware. This allows you to extend Astro's i18n routing instead of completely replacing it. Run middleware in combination with your own middleware, using the sequence utility to determine the order:
import { defineMiddleware, sequence } from 'astro:middleware';
import { middleware } from 'astro:i18n'; // Astro's own i18n routing config
export const userMiddleware = defineMiddleware();
export const onRequest = sequence(
userMiddleware,
middleware({
redirectToDefaultLocale: false,
prefixDefaultLocale: true,
}),
);
#10671 9e14a78cb05667af9821948c630786f74680090d Thanks @fshafiee! - Adds the httpOnly, sameSite, and secure options when deleting a cookie
#10747 994337c99f84304df1147a14504659439a9a7326 Thanks @lilnasy! - Fixes an issue where functions could not be used as named slots.
#10750 7e825604ddf90c989537e07939a39dc249343897 Thanks @OliverSpeir! - Fixes a false positive for "Invalid tabindex on non-interactive element" rule for roleless elements ( div and span ).
#10745 d51951ce6278d4b59deed938d65e1cb72b5102df Thanks @lilnasy! - Fixes an issue where CLI commands could not report the reason for failure before exiting.
#10661 e2cd7f4291912dadd4a654bc7917856c58a72a97 Thanks @liruifengv! - Fixed errorOverlay theme toggle bug.
Updated dependencies [ccafa8d230f65c9302421a0ce0a0adc5824bfd55, 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99]:
#10728 f508c4b7d54316e737f454a3777204b23636d4a0 Thanks @ematipico! - Fixes a regression where some very specific code rendered using expressive-code was not escaped properly.
#10737 8a30f257b1f3618b01212a591b82ad7a63c82fbb Thanks @lilnasy! - Fixes a regression where constructing and returning 404 responses from a middleware resulted in the dev server getting stuck in a loop.
#10719 b21b3ba307235510707ee9f5bd49f71473a07004 Thanks @ematipico! - Fixes a false positive for div and span elements 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 role attribute. This means that cases like the following are now deemed correct:
<div role="tablist"></div>
<span role="button" onclick="" onkeydown=""></span>
#10688 799f6f3f29a3ef4f76347870a209ffa89651adfa Thanks @bluwy! - Marks renderer jsxImportSource and jsxTransformOptions options as deprecated as they are no longer used since Astro 3.0
#10657 93d353528fa1a85b67e3f1e9514ed2a1b42dfd94 Thanks @natemoo-re! - Improves the color contrast for notification badges on dev toolbar apps
#10693 1d26e9c7f7d8f47e33bc68d3b30bbffce25c7b63 Thanks @apetta! - Adds the disableremoteplayback attribute to MediaHTMLAttributes interface
#10695 a15975e41cb5eaf6ed8eb3ebaee676a17e433052 Thanks @bluwy! - Skips prerender chunk if building with static output
#10707 5e044a5eafaa206d2ef8b62c37d1bcd37f0a4078 Thanks @horo-fox! - Logs an error when a page's getStaticPaths fails
#10686 fa0f593890502faf5709ab881fe0e45519d2f7af Thanks @bluwy! - Prevents inlining scripts if used by other chunks when using the experimental.directRenderScript option
#10679 ca6bb1f31ef041e6ccf8ef974856fa945ff5bb31 Thanks @martrapp! - Generates missing popstate events for Firefox when navigating to hash targets on the same page.
#10669 0464563e527f821e53d78028d9bbf3c4e1050f5b Thanks @Princesseuh! - Fixes Astro waiting infinitely in CI when a required package was not installed
#10666 55ddb2ba4889480f776a8d29b9dcd531b9f5ab3e Thanks @lilnasy! - Fixes an issue where forwarded requests did not include hostname on node-based adapters. This also makes error pages more reliable.
#10642 4f5dc14f315eba7ea6ec5cc8e5dacb0cb81288dd Thanks @OliverSpeir! - Fixes typing issues when using format and quality options with remote images
#10616 317d18ef8c9cf4fd13647518e3fd352774a86481 Thanks @NikolaRHristov! - This change disables the sharp libvips image cache as it errors when the
file is too small and operations are happening too fast (runs into a race
condition)
#10470 320c309ca9fbe51c40e6ba846d04a0cb49aced5f Thanks @liruifengv! - improves client:only error message
#10496 ce985631129e49f7ea90e6ea690ef9f9cf0e6987 Thanks @florian-lefebvre! - Makes the warning less scary when adding 3rd-party integrations using astro add
#10495 046d69d517118ab5c0e71604b321729d66ddffff Thanks @satyarohith! - This patch allows astro to run in node-compat mode in Deno. Deno doesn't support
construction of response from async iterables in node-compat mode so we need to
use ReadableStream.
#10605 a16a829f4e25ad5c9a1b4557ec089fc8ab53320f Thanks @martrapp! - Fixes an issue with outdated page titles in browser history when using text fragments in view transition navigation.
#10584 e648c5575a8774af739231cfa9fc27a32086aa5f Thanks @duanwilliam! - Fixes a bug where JSX runtime would error on components with nullish prop values in certain conditions.
#10608 e31bea0704890ff92ce4f9b0ce536c1c90715f2c Thanks @matthewp! - Fixes bug with head content being pushed into body
Updated dependencies [2cf116f80cb5e421ab5cc5eb4a654e7b78c1b8de, 374efcdff9625ca43309d89e3b9cfc9174351512]:
#10596 20463a6c1e1271d8dc3cb0ab3419ee5c72abd218 Thanks @Princesseuh! - Add removeBase function
Updated dependencies [20463a6c1e1271d8dc3cb0ab3419ee5c72abd218]:
#10567 fbdc10f90f7baa5c49f2f53e3e4ce8f453814c01 Thanks @Princesseuh! - Fixes astro:assets not working when using complex config with vite.build.rollupOptions.output.assetFileNames
#10593 61e283e5a0d95b6ef5d3c4c985d6ee78f74bbd8e Thanks @Princesseuh! - Fixes Polymorphic type helper causing TypeScript errors in certain cases after the previous update
#10543 0fd36bdb383297b32cc523b57d2442132da41595 Thanks @matthewp! - Fixes inline stylesheets with content collections cache
#10582 a05953538fcf524786385830b99c0c5a015173e8 Thanks @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.
#10549 54c2f9707f5d038630143f769e3075c698474654 Thanks @admirsaheta! - Updates the HTMLAttributes type exported from astro to allow data attributes
#10562 348c1ca1323d0516c2dcf8e963343cd12cb5407f Thanks @apetta! - Fixes minor type issues inside the built-in components of Astro
#10550 34fa8e131b85531e6629390307108ffc4adb7ed1 Thanks @Skn0tt! - Fixes bug where server builds would include unneeded assets in SSR Function, potentially leading to upload errors on Vercel, Netlify because of size limits
Updated dependencies [c585528f446ccca3d4c643f4af5d550b93c18902]:
#10532 8306ce1ff7b71a2a0d7908336c9be462a54d395a Thanks @martrapp! - Fixes a style issue of client:only components in DEV mode during view transitions.
#10473 627e47d67af4846cea2acf26a96b4124001b26fc Thanks @bluwy! - Fixes and improves performance when rendering Astro JSX
#10504 8e4e554cc211e59c329c0a5d110c839c886ff120 Thanks @Princesseuh! - Update Babel version to fix regression in Babel's 7.24.2.
Updated dependencies [19e42c368184013fc30d1e46753b9e9383bb2bdf]:
e4a6462751725878bfe47632eeafa6854cad5bf2 Thanks @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.#10455 c12666166db724915e42e37a048483c99f88e6d9 Thanks @lilnasy! - Adds a helpful error message that will be shown when an endpoint does not return a Response.
#10426 6a9a35ee15069541c3144012385366a3c689240a Thanks @markgaze! - Fixes an issue with generating JSON schemas when the schema is a function
#10448 fcece3658697248ab58f77b3d4a8b14d362f3c47 Thanks @lilnasy! - Fixes an issue where multiple rendering errors resulted in a crash of the SSR app server.
#10379 3776ecf0aa9e08a992d3ae76e90682fd04093721 Thanks @1574242600! - Fixes a routing issue with partially truncated dynamic segments.
#10442 f8e0ad3c52a37b8a2175fe2f5ff2bd0cd738f499 Thanks @Princesseuh! - Fixes small rendering issues with the dev toolbar in certain contexts
#10438 5b48cc0fc8383b0659a595afd3a6ee28b28779c3 Thanks @bholmesdev! - Generate Astro DB types when running astro sync.
#10456 1900a8f9bc337f3a882178d1770e10ab67fab0ce Thanks @martrapp! - Fixes an error when using astro:transitions/client without <ViewTransitions/>
128c7a36397d99608dea918885b68bd302d00e7f Thanks @lilnasy! - Fixes an issue where error pages did not have access to the Astro.locals fields provided by the adapter.#10410 055fe293c6702dd27bcd6c4f59297c6d4385abb1 Thanks @lilnasy! - Fixes an issue where configured redirects could not include certain characters in the target path.
#9820 8edc42aa7c209b12d98ecf20cdecccddf7314af0 Thanks @alexnguyennz! - Prevents fully formed URLs in attributes from being escaped
629c9d7c4d96ae5711d95601e738b3d31d268116 Thanks @mingjunlu! - Fixes an issue where dev toolbar x-ray didn't escape props content.#10392 02aeb01cb8b62b9cc4dfe6069857219404343b73 Thanks @martrapp! - Fixes broken types for some functions of astro:transitions/client.
#10390 236cdbb611587692d3c781850cb949604677ef82 Thanks @bholmesdev! - Adds --help reference for new db and studio CLI commands
#10206 dc87214141e7f8406c0fdf6a7f425dad6dea6d3e Thanks @lilnasy! - Allows middleware to run when a matching page or endpoint is not found. Previously, a pages/404.astro or pages/[...catch-all].astro route 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.astro or fallback route with spread params, or use a routing configuration option if your adapter provides one.
#9960 c081adf998d30419fed97d8fccc11340cdc512e0 Thanks @StandardGage! - Allows passing any props to the <Code /> component
#10102 e3f02f5fb1cf0dae3c54beb3a4af3dbf3b06abb7 Thanks @bluwy! - Adds a new experimental.directRenderScript configuration option which provides a more reliable strategy to prevent scripts from being executed in pages where they are not used.
This replaces the experimental.optimizeHoistedScript flag 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 enable directRenderScript:
// astro.config.mjs
import { defineConfig } from 'astro/config';
export default defineConfig({
experimental: {
- optimizeHoistedScript: true,
+ directRenderScript: true
}
});
With experimental.directRenderScript configured, scripts are now directly rendered as declared in Astro files (including existing features like TypeScript, importing node_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 5a9528741fa98d017b269c7e4f013058028bdc5d Thanks @bluwy! - Stabilizes markdown.shikiConfig.experimentalThemes as markdown.shikiConfig.themes. No behaviour changes are made to this option.
#10189 1ea0a25b94125e4f6f2ac82b42f638e22d7bdffd Thanks @peng! - Adds the option to pass an object to build.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 a fallback domain 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:
// astro.config.mjs
import { defineConfig } from 'astro/config';
export default defineConfig({
build: {
assetsPrefix: {
js: 'https://js.cdn.example.com',
mjs: 'https://js.cdn.example.com', // if you have .mjs files, you must add a new entry like this
png: 'https://images.cdn.example.com',
fallback: 'https://generic.cdn.example.com',
},
},
});
#10252 3307cb34f17159dfd3f03144697040fcaa10e903 Thanks @Princesseuh! - Adds support for emitting warning and info notifications from dev toolbar apps.
When using the toggle-notification event, the severity can be specified through detail.level:
eventTarget.dispatchEvent(
new CustomEvent('toggle-notification', {
detail: {
level: 'warning',
},
}),
);
#10186 959ca5f9f86ef2c0a5a23080cc01c25f53d613a9 Thanks @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 9cd84bd19b92fb43ae48809f575ee12ebd43ea8f Thanks @matthewp! - Changes the default behavior of transition:persist to update the props of persisted islands upon navigation. Also adds a new view transitions option transition:persist-props (default: false) to prevent props from updating as needed.
Islands which have the transition:persist property 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 products props and might have some internal state, such as which filters are applied:
<ProductListing transition:persist products={products} />
Upon navigation, this component persists, but the desired products might 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=true to persist both props and state during navigation:
<ProductListing transition:persist-props="true" products={products} />
#9977 0204b7de37bf626e1b97175b605adbf91d885386 Thanks @OliverSpeir! - Supports adding the data-astro-rerun attribute on script tags so that they will be re-executed after view transitions
<script is:inline data-astro-rerun>
...
</script>
#10145 65692fa7b5f4440c644c8cf3dd9bc50103d2c33b Thanks @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 $schema value for TypeScript-style autocompletion/hints in tools like VSCode.
To enable this feature, add the experimental flag:
import { defineConfig } from 'astro/config';
export default defineConfig({
experimental: {
+ contentCollectionJsonSchema: true
}
});
This experimental implementation requires you to manually reference the schema in each data entry file of the collection:
// src/content/test/entry.json
{
+ "$schema": "../../../.astro/collections/test.schema.json",
"test": "test"
}
Alternatively, you can set this in your VSCode json.schemas settings:
"json.schemas": [
{
"fileMatch": [
"/src/content/test/**"
],
"url": "../../../.astro/collections/test.schema.json"
}
]
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 5a9528741fa98d017b269c7e4f013058028bdc5d Thanks @bluwy! - Migrates shikiji to shiki 1.0
#10268 2013e70bce16366781cc12e52823bb257fe460c0 Thanks @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 5c7862a9fe69954f8630538ebb7212cd04b8a810 Thanks @Princesseuh! - Updates the UI for dev toolbar audits with new information
#10360 ac766647b0e6156b7c4a0bb9a11981fe168852d7 Thanks @nmattia! - Fixes an issue where some CLI commands attempted to directly read vite config files.
#10291 8107a2721b6abb07c3120ac90e03c39f2a44ab0c Thanks @bluwy! - Treeshakes unused Astro component scoped styles
#10368 78bafc5d661ff7dd071c241cb1303c4d8a774d21 Thanks @Princesseuh! - Updates the base tsconfig.json preset with jsx: 'preserve' in order to fix errors when importing Astro files inside .js and .ts files.
Updated dependencies [c081adf998d30419fed97d8fccc11340cdc512e0, 1ea0a25b94125e4f6f2ac82b42f638e22d7bdffd, 5a9528741fa98d017b269c7e4f013058028bdc5d, a31bbd7ff8f3ec62ee507f72d1d25140b82ffc18]:
33583e8b31ee8a33e26cf57f30bb422921f4745d Thanks @lilnasy! - Fixes an issue where elements slotted within interactive framework components disappeared after hydration.#10355 8ce9fffd44b0740621178d61fb1425bf4155c2d7 Thanks @ematipico! - Fixes a regression where full dynamic routes were prioritized over partial dynamic routes. Now a route like food-[name].astro is matched before [name].astro.
#10356 d121311a3f4b5345e344e31f75d4e7164d65f729 Thanks @mingjunlu! - Fixes an issue where getCollection might return undefined when content collection is empty
#10325 f33cce8f6c3a2e17847658cdedb015bd93cc1ee3 Thanks @lilnasy! - Fixes an issue where ctx.site included the configured base in API routes and middleware, unlike Astro.site in astro pages.
#10343 f973aa9110592fa9017bbe84387f22c24a6d7159 Thanks @ematipico! - Fixes some false positive in the dev toolbar a11y audits, by adding the a element to the list of interactive elements.
#10295 fdd5bf277e5c1cfa30c1bd2ca123f4e90e8d09d9 Thanks @rossrobino! - Adds a prefetch fallback when using the experimental.clientPrerender option. If prerendering fails, which can happen if Chrome extensions block prerendering, it will fall back to prefetching the URL. This works by adding a prefetch field to the speculationrules script, but does not create an extra request.
a2e9b2b936666b2a4779feb00dcb8ff0ab82c2ec Thanks @matthewp! - Fixes @astrojs/db loading TS in the fixturesf2e60a96754ed1d86001fe4d5d3a0c0ef657408d Thanks @FredKSchott! - Fixes an issue where slotting interactive components within a "client:only" component prevented all component code in the page from running.#10281 9deb919ff95b1d2ffe5a5f70ec683e32ebfafd05 Thanks @lilnasy! - Fixes an issue where 404.astro was ignored with i18n routing enabled.
#10279 9ba3e2605daee3861e3bf6c5768f1d8bced4709d Thanks @lilnasy! - Fixes an issue where returning redirect responses resulted in missing files with certain adapters.
#10319 19ecccedaab6d8fa0ff23711c88fa7d4fa34df38 Thanks @lilnasy! - Fixes an issue where streaming SSR responses sometimes failed with "iterator.result is not a function" on node-based adapters.
#10302 992537e79f1847b590a2e226aac88a47a6304f68 Thanks @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, .mdx etc) and such extension would be also within the path (like ./.astro/index.astro).
#10298 819d20a89c0d269333c2d397c1080884f516307a Thanks @Fryuni! - Fix an incorrect conflict resolution between pages generated from static routes and rest parameters
4bc360cd5f25496aca3232f6efb3710424a14a34 Thanks @sanman1k98! - Fixes jerky scrolling on IOS when using view transitions.#10278 a548a3a99c2835c19662fc38636f92b2bda26614 Thanks @Princesseuh! - Fixes original images sometimes being kept / deleted when they shouldn't in both MDX and Markdoc
#10280 3488be9b59d1cb65325b0e087c33bcd74aaa4926 Thanks @bholmesdev! - Finalize db API to a shared db/ directory.
5e3e74b61daa2ba44c761c9ab5745818661a656e Thanks @Princesseuh! - Fixes dev toolbar warning about using the proper loading attributes on images using data: URIs#10274 e556151603a2f0173059d0f98fdcbec0610b48ff Thanks @lilnasy! - Fixes a regression introduced in v4.4.5 where image optimization did not work in dev mode when a base was configured.
#10263 9bdbed723e0aa4243d7d6ee64d1c1df3b75b9aeb Thanks @martrapp! - Adds auto completion for astro: event names when adding or removing event listeners on document.
#10284 07f89429a1ef5173d3321e0b362a9dc71fc74fe5 Thanks @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.
#10247 fb773c9161bf8faa5ebd7e115f3564c3359e56ea Thanks @martrapp! - Fixes an issue where transition:animate="none" still allowed the browser-native morph animation.
#10248 8ae5d99534fc09d650e10e64a09b61a2807574f2 Thanks @ematipico! - Fixes an issue where multiple injected routes with the same entrypoint but different pattern were incorrectly cached, causing some of them not being rendered in the dev server.
#10250 57655a99db34e20e9661c039fab253b867013318 Thanks @log101! - Fixes the overwriting of localised index pages with redirects
#10239 9c21a9df6b03e36bd78dc553e13c55b9ef8c44cd Thanks @mingjunlu! - Improves the message of MiddlewareCantBeLoaded for clarity
#10222 ade9759cae74ca262b988260250bcb202235e811 Thanks @martrapp! - Adds a warning in DEV mode when using view transitions on a device with prefer-reduced-motion enabled.
#10251 9b00de0a76b4f4b5b808e8c78e4906a2497e8ecf Thanks @mingjunlu! - Fixes TypeScript type definitions for Code component theme and experimentalThemes props
#10221 4db82d9c7dce3b73fe43b86020fcfa326c1357ec Thanks @matthewp! - Prevents errors in templates from crashing the server
#10219 afcb9d331179287629b5ffce4020931258bebefa Thanks @matthewp! - Fix dynamic slots missing hydration scripts
#10220 1eadb1c5290f2f4baf538c34889a09d5fcfb9bd4 Thanks @Princesseuh! - Fixes some built-in apps of the dev toolbar not closing when clicking the page
#10154 e64bd0740b44aed5cfaf67e5c37a1c56ed4442f4 Thanks @Cherry! - Fixes an issue where config.vite.build.assetsInlineLimit could not be set as a function.
#10196 8fb32f390d40cfa12a82c0645928468d27218866 Thanks @lilnasy! - Fixes an issue where a warning about headers being accessed in static mode is unnecessarily shown when i18n is enabled.
#10199 6aa660ae7abc6841d7a3396b29f10b9fb7910ce5 Thanks @lilnasy! - Fixes an issue where prerendered pages had access to query params in dev mode.
#10195 903eace233033998811b72e27a54c80d8e59ff37 Thanks @1574242600! - Fix build failure caused by read-only files under /public (in the presence of client-side JS).
#10205 459f74bc71748279fe7dce0688f38bd74b51c5c1 Thanks @martrapp! - Adds an error message for non-string transition:name values
#10208 8cd38f02456640c063552aef00b2b8a216b3935d Thanks @log101! - Fixes custom headers are not added to the Node standalone server responses in preview mode
#10143 7c5fcd2fa817472f480bbfbbc11b9ed71a7210ab Thanks @bluwy! - Improves the default optimizeDeps.entries Vite config to avoid globbing server endpoints, and respect the srcDir option
#10197 c856c729404196900a7386c8426b81e79684a6a9 Thanks @Princesseuh! - Fixes errors being logged twice in some cases
#10166 598f30c7cd6c88558e3806d9bc5a15d426d83992 Thanks @bluwy! - Improves Astro style tag HMR when updating imported styles
#10194 3cc20109277813ccb9578ca87a8b0d680a73c35c Thanks @matthewp! - Fixes an issue related to content collections usage in browser context caused by csssec
a46249173edde66b03c19441144272baa8394fb4 Thanks @ematipico! - Fixes an issue with the i18n.routing types, where an internal transformation was causing the generation of incorrect types for integrations.#9795 5acc3135ba5309a566def466fbcbabd23f70cd68 Thanks @lilnasy! - Refactors internals relating to middleware, endpoints, and page rendering.
#10105 1f598b372410066c6fcd41cba9915f6aaf7befa8 Thanks @negativems! - Fixes an issue where some astro commands failed if the astro config file or an integration used the global crypto object.
#10165 d50dddb71d87ce5b7928920f10eb4946a5339f86 Thanks @ematipico! - Fixes an issue where the i18n.routing object had all its fields defined as mandatory. Now they all are optionals and shouldn't break when using astro.config.mts.
#10132 1da9c5f2f3fe70b0206d1b3e0c01744fa40d511c Thanks @bluwy! - Simplifies internal Vite preview server teardown
#10163 b92d35f1026f3e99abb888d1a845bdda4efdc327 Thanks @mingjunlu! - Fixes an issue where audit fails to initialize when encountered <a> inside <svg>
#10079 80f8996514e6d0546e94bd927650cd4ab2f1fa2f Thanks @ktym4a! - Fix integrationData fetch to always be called even if View Transition is enabled.
#10139 3c73441eb2eaba767d6dad1b30c0353195d28791 Thanks @bluwy! - Fixes style-only change detection for Astro files if both the markup and styles are updated
#9614 d469bebd7b45b060dc41d82ab1cf18ee6de7e051 Thanks @matthewp! - Improves Node.js streaming performance.
This uses an AsyncIterable instead of a ReadableStream to do streaming in Node.js. This is a non-standard enhancement by Node, which is done only in that environment.
#10001 748b2e87cd44d8bcc1ab9d7e504703057e2000cd Thanks @bholmesdev! - Removes content collection warning when a configured collection does not have a matching directory name. This should resolve i18n collection warnings for Starlight users.
This also ensures configured collection names are always included in getCollection() and getEntry() types even when a matching directory is absent. We hope this allows users to discover typos during development by surfacing type information.
#10074 7443929381b47db0639c49a4d32aec4177bd9102 Thanks @Princesseuh! - Add a UI showing the list of found problems when using the audit app in the dev toolbar
#10099 b340f8fe3aaa81e38c4f1aa41498b159dc733d86 Thanks @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: name is unaffected.
However, this fix may result in breaking changes if your project relies on the particular character encoding strategy Astro uses to translate transition:name directives into values of the underlying CSS view-transition-name property. For example, Welcome to Astro is now encoded as Welcome_20to_20Astro_2e.
This mainly affects spaces and punctuation marks but no Unicode characters with codes >= 128.
#9976 91f75afbc642b6e73dd4ec18a1fe2c3128c68132 Thanks @OliverSpeir! - Adds a new optional astro:assets image attribute inferSize for use with remote images.
Remote images can now have their dimensions inferred just like local images. Setting inferSize to true allows you to use getImage() and the <Image /> and <Picture /> components without setting the width and height properties.
---
import { Image, Picture, getImage } from 'astro:assets';
const myPic = await getImage({ src: 'https://example.com/example.png', inferSize: true });
---
<Image src="https://example.com/example.png" inferSize alt="" />
<Picture src="https://example.com/example.png" inferSize alt="" />
Read more about using inferSize with remote images in our documentation.
#10015 6884b103c8314a43e926c6acdf947cbf812a21f4 Thanks @Princesseuh! - Adds initial support for performance audits to the dev toolbar
#10116 4bcc249a9f34aaac59658ca626c828bd6dbb8046 Thanks @lilnasy! - Fixes an issue where the dev server froze when typescript aliases were used.
#10096 227cd83a51bbd451dc223fd16f4cf1b87b8e44f8 Thanks @Fryuni! - Fixes regression on routing priority for multi-layer index pages
The 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 /blog is 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)/blog is 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 solely for rest parameter segments and their immediate parents, which is consistent with the transitivity property.
#10120 787e6f52470cf07fb50c865948b2bc8fe45a6d31 Thanks @bluwy! - Updates and supports Vite 5.1
#10096 227cd83a51bbd451dc223fd16f4cf1b87b8e44f8 Thanks @Fryuni! - Fixes edge case on i18n fallback routes
Previously index routes deeply nested in the default locale, like /some/nested/index.astro could be mistaken as the root index for the default locale, resulting in an incorrect redirect on /.
#10112 476b79a61165d0aac5e98459a4ec90762050a14b Thanks @Princesseuh! - Renames the home Astro Devtoolbar App to astro:home
#10117 51b6ff7403c1223b1c399e88373075972c82c24c Thanks @hippotastic! - Fixes an issue where create astro, astro add and @astrojs/upgrade would fail due to unexpected package manager CLI output.
#9857 73bd900754365b006ee730df9f379ba924e5b3fa Thanks @iamyunsin! - Fixes false positives in the dev overlay audit when multiple role values exist.
#10075 71273edbb429b5afdba6f8ee14681b66e4c09ecc Thanks @lilnasy! - Improves error messages for island hydration.
#10072 8106178043050d142bf385bed2990730518f28e2 Thanks @lilnasy! - Clarifies error messages in endpoint routing.
#9971 d9266c4467ca0faa1213c1a5995164e5655ab375 Thanks @mingjunlu! - Fixes an issue where ReadableStream wasn't canceled in dev mode
#10063 dac759798c111494e76affd2c2504d63944871fe Thanks @marwan-mohamed12! - Moves shikiji-core from devDependencies to dependencies to prevent type errors
#10067 989ea63bb2a5a670021541198aa70b8dc7c4bd2f Thanks @ematipico! - Fixes a regression in the astro:i18n module, where the functions getAbsoluteLocaleUrl and getAbsoluteLocaleUrlList returned a URL with double slash with a certain combination of options.
#10060 1810309e65c596266355c3b7bb36cdac70f3305e Thanks @lilnasy! - Fixes an issue where custom client directives added by integrations broke builds with a custom root.
#9991 8fb67c81bb84530b39df4a1449c0862def0854af Thanks @ktym4a! - Increases compatibility with standard browser behavior by changing where view transitions occur on browser back navigation.
#10022 3fc76efb2a8faa47edf67562a1f0c84a19be1b33 Thanks @lilnasy! - Fixes a regression where types for the astro:content module did not include required exports, leading to typescript errors.
#10016 037e4f12dd2f460d66f72c9f2d992b95e74d2da9 Thanks @ematipico! - Fixes a bug where routes with a name that start with the name of the i18n.defaultLocale were incorrectly returning a 404 response.
#10013 e6b5306a7de779ce495d0ff076d302de0aa57eaf Thanks @delucis! - Fixes a regression in content collection types
#10003 ce4283331f18c6178654dd705e3cf02efeef004a Thanks @bholmesdev! - Adds support for .strict() on content collection schemas when a custom slug is present.
#9998 18ac0940ea1b49b6b0ddd9be1f96aef416e2d7ee Thanks @ematipico! - Fixes a bug in Astro.currentLocale that wasn't returning the correct locale when a locale is configured via path
#9998 18ac0940ea1b49b6b0ddd9be1f96aef416e2d7ee Thanks @ematipico! - Fixes a regression in Astro.currentLocale where it stopped working properly with dynamic routes
#9956 81acac24a3cac5a9143155c1d9f838ea84a70421 Thanks @matthewp! - Fixes HMR for MDX dependencies in Content Collections
#9999 c53a31321a935e4be04809046d7e0ba3cc41b272 Thanks @MoustaphaDev! - Rollbacks the feature which allowed to dynamically generate slots with variable slot names due to unexpected regressions.
#9906 3c0876cbed5033e6b5b42cc2b9d8b393d7e5a55e Thanks @florian-lefebvre! - Improves the types for the astro:content module by making low fidelity types available before running astro sync
#9932 9f0d89fa7e9e7c08c8600b0c49c2cce7489a7582 Thanks @ematipico! - Fixes a case where a warning was logged even when the feature i18nDomains wasn't enabled
#9907 6c894af5ab79f290f4ff7feb68617a66e91febc1 Thanks @ktym4a! - Load 404.html on all nonexistent paths on astro preview.
#9841 27ea080e24e2c5cdc59b63b1dfe0a83a0c696597 Thanks @kristianbinau! - Makes the warning clearer when having a custom base and requesting a public URL without it
#9888 9d2fdb293d6a7323e10126cebad18ef9a2ea2800 Thanks @natemoo-re! - Improves error handling logic for the astro sync command.
#9918 d52529e09450c84933dd15d6481edb32269f537b Thanks @LarryIVC! - Adds the name attribute to the <details> tag type
#9938 1568afb78a163db63a4cde146dec87785a83db1d Thanks @lilnasy! - Fixes a regression where middleware did not run for prerendered pages and endpoints.
#9931 44674418965d658733d3602668a9354e18f8ef89 Thanks @lilnasy! - Fixes a regression where a response created with Response.redirect or containing null as the body never completed in node-based adapters.
#9839 58f9e393a188702eef5329e41deff3dcb65a3230 Thanks @Princesseuh! - Adds a new ComponentProps type export from astro/types to get the props type of an Astro component.
---
import type { ComponentProps } from 'astro/types';
import Button from './Button.astro';
type myButtonProps = ComponentProps<typeof Button>;
---
#9159 7d937c158959e76443a02f740b10e251d14dbd8c Thanks @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 fad4f64aa149086feda2d1f3a0b655767034f1a8 Thanks @matthewp! - Adds a new build.format configuration option: 'preserve'. This option will preserve your source structure in the final build.
The existing configuration options, file and directory, either build all of your HTML pages as files matching the route name (e.g. /about.html) or build all your files as index.html within 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 create index.html files 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.astro builds /about.html) when using the file configuration option.
Rather than make a breaking change to allow build.format: 'file' to be more flexible, we decided to create a new build.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.astro becomes about.htmlabout/index.astro becomes about/index.htmlSee the build.format configuration options reference for more details.
#9143 041fdd5c89920f7ccf944b095f29e451f78b0e28 Thanks @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 the experimental.i18nDomains flag to true and add i18n.domains to map any of your supported locales to custom URLs:
//astro.config.mjs"
import { defineConfig } from 'astro/config';
export default defineConfig({
site: 'https://example.com',
output: 'server', // required, with no prerendered pages
adapter: node({
mode: 'standalone',
}),
i18n: {
defaultLocale: 'en',
locales: ['es', 'en', 'fr', 'ja'],
routing: {
prefixDefaultLocale: false,
},
domains: {
fr: 'https://fr.example.com',
es: 'https://example.es',
},
},
experimental: {
i18nDomains: true,
},
});
With "domains" configured, the URLs emitted by getAbsoluteLocaleUrl() and getAbsoluteLocaleUrlList() will use the options set in i18n.domains.
import { getAbsoluteLocaleUrl } from 'astro:i18n';
getAbsoluteLocaleUrl('en', 'about'); // will return "https://example.com/about"
getAbsoluteLocaleUrl('fr', 'about'); // will return "https://fr.example.com/about"
getAbsoluteLocaleUrl('es', 'about'); // will return "https://example.es/about"
getAbsoluteLocaleUrl('ja', 'about'); // will return "https://example.com/ja/about"
Similarly, your localized files will create routes at corresponding URLs:
/en/about.astro will be reachable at the URL https://example.com/about./fr/about.astro will be reachable at the URL https://fr.example.com/about./es/about.astro will be reachable at the URL https://example.es/about./ja/about.astro will be reachable at the URL https://example.com/ja/about.See our Internationalization Guide for more details and limitations on this experimental routing feature.
#9755 d4b886141bb342ac71b1c060e67d66ca2ffbb8bd Thanks @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:
- 
+ 
<!-- This dog lives in the same folder as my article! -->
#9908 2f6d1faa6f2d6de2d4ccd2a48adf5adadc82e593 Thanks @lilnasy! - Improves http behavior relating to errors encountered while streaming a response.
#9877 7be5f94dcfc73a78d0fb301eeff51614d987a165 Thanks @fabiankachlock! - Fixes the content config type path on windows
#9143 041fdd5c89920f7ccf944b095f29e451f78b0e28 Thanks @ematipico! - Fixes an issue where the function getLocaleRelativeUrlList wasn't normalising the paths by default
#9911 aaedb848b1d6f683840035865528506a346ea659 Thanks @natemoo-re! - Fixes an issue where some adapters that do not include a start() export would error rather than silently proceed
#9884 37369550ab57ca529fd6c796e5b0e96e897ca6e5 Thanks @lilnasy! - Fixes an issue where multiple cookies were sent in a single Set-Cookie header in the dev mode.
#9876 e9027f194b939ac5a4d795ee1a2c24e4a6fbefc0 Thanks @friedemannsommer! - Fixes an issue where using Response.redirect in an endpoint led to an error.
#9882 13c3b712c7ba45d0081f459fc06f142216a4ec59 Thanks @natemoo-re! - Improves handling of YAML parsing errors
#9878 a40a0ff5883c7915dd55881dcebd052b9f94a0eb Thanks @lilnasy! - Fixes an issue where setting trailingSlash to "never" had no effect on Astro.url.
#9840 70fdf1a5c660057152c1ca111dcc89ceda5c8840 Thanks @delucis! - Expose ContentConfig type from astro:content
#9865 00ba9f1947ca9016cd0ee4d8f6048027fab2ab9a Thanks @ematipico! - Fixes a bug in Astro.currentLocale where the value was incorrectly computed during the build.
#9838 0a06d87a1e2b94be00a954f350c184222fa0594d Thanks @lilnasy! - Fixes an issue where astro:i18n could not be used in framework components.
Updated dependencies [44c957f893c6bf5f5b7c78301de7b21c5975584d]:
#9825 e4370e9e9dd862425eced25823c82e77d9516927 Thanks @tugrulates! - Fixes false positive aria role errors on interactive elements
#9828 a3df9d83ca92abb5f08f576631019c1604204bd9 Thanks @ematipico! - Fixes a case where shared modules among pages and middleware were transformed to a no-op after the build.
#9834 1885cea308a62b173a50967cf5a0b174b3c3f3f1 Thanks @Princesseuh! - Fixes third-party dev toolbar apps not loading correctly when using absolute paths on Windows
#9818 d688954c5adba75b0d676694fbf5fb0da1c0af13 Thanks @Princesseuh! - Improves the wording of a few confusing error messages
#9680 5d7db1dbb0ff06db98e08b0ca241ff09d0b8b44d Thanks @loucyx! - Fixes types generation from Content Collections config file
#9822 bd880e8437ea2df16f322f604865c1148a9fd4cf Thanks @liruifengv! - Applies the correct escaping to identifiers used with transition:name.
#9830 f3d22136e53fd902310024519fc4de83f0a58039 Thanks @lilnasy! - Fixes an issue where 404 responses from endpoints were replaced with contents of 404.astro in dev mode.
#9816 2a44c8f93201958fba2d1e83046eabcaef186b7c Thanks @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 b3f313138bb314e2b416c29cda507383c2a9f816 Thanks @bluwy! - Fixes environment variables replacement for export const prerender
#9790 267c5aa2c7706f0ea3447f20a09d85aa560866ad Thanks @lilnasy! - Refactors internals of the astro:i18n module to be more maintainable.
#9776 dc75180aa698b298264362bab7f00391af427798 Thanks @lilnasy! - Simplifies internals that handle middleware.
#9792 e22cb8b10c0ca9f6d88cab53cd2713f57875ab4b Thanks @tugrulates! - Accept aria role switch on toolbar audit.
#9606 e6945bcf23b6ad29388bbadaf5bb3cc31dd4a114 Thanks @eryue0220! - Fixes escaping behavior for .html files and components
#9786 5b29550996a7f5459a0d611feea6e51d44e1d8ed Thanks @Fryuni! - Fixes a regression in routing priority for index pages in rest parameter folders and dynamic sibling trees.
Considering the following tree:
src/pages/
├── index.astro
├── static.astro
├── [dynamic_file].astro
├── [...rest_file].astro
├── blog/
│ └── index.astro
├── [dynamic_folder]/
│ ├── index.astro
│ ├── static.astro
│ └── [...rest].astro
└── [...rest_folder]/
├── index.astro
└── static.astro
The routes are sorted in this order:
/src/pages/index.astro
/src/pages/blog/index.astro
/src/pages/static.astro
/src/pages/[dynamic_folder]/index.astro
/src/pages/[dynamic_file].astro
/src/pages/[dynamic_folder]/static.astro
/src/pages/[dynamic_folder]/[...rest].astro
/src/pages/[...rest_folder]/static.astro
/src/pages/[...rest_folder]/index.astro
/src/pages/[...rest_file]/index.astro
This allows for index files to be used as overrides to rest parameter routes on SSR when the rest parameter matching undefined is not desired.
#9775 075706f26d2e11e66ef8b52288d07e3c0fa97eb1 Thanks @lilnasy! - Simplifies internals that handle endpoints.
#9773 9aa7a5368c502ae488d3a173e732d81f3d000e98 Thanks @LunaticMuch! - Raises the required vite version to address a vulnerability in vite.server.fs.deny that affected the dev mode.
#9781 ccc05d54014e24c492ca5fddd4862f318aac8172 Thanks @stevenbenner! - Fix build failure when image file name includes special characters
eed0e8757c35dde549707e71c45862438a043fb0 Thanks @Princesseuh! - Fix apps being able to crash the dev toolbar in certain cases#9712 ea6cbd06a2580527786707ec735079ff9abd0ec0 Thanks @bluwy! - Improves HMR behavior for style-only changes in .astro files
#9739 3ecb3ef64326a8f77aa170df1e3c89cb5c12cc93 Thanks @ematipico! - Makes i18n redirects take the build.format configuration into account
#9762 1fba85681e86aa83d24336d4209cafbc76b37607 Thanks @ematipico! - Adds popovertarget" to the attribute that can be passed to the button` element
#9605 8ce40a417c854d9e6a4fa7d5a85d50a6436b4a3c Thanks @MoustaphaDev! - Adds support for dynamic slot names
#9381 9e01f9cc1efcfb938355829676d51b24818ab2bb Thanks @martrapp! - Improves the CLI output of astro preferences list to include additional relevant information
#9741 73d74402007896204ee965f6553dc83b3dec8d2f Thanks @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 8d2e5db096f1e7b098511b4fe9357434a6ff0703 Thanks @Blede2000! - Allow i18n routing utilities like getRelativeLocaleUrl to also get the default local path when redirectToDefaultLocale is false
Updated dependencies [53c69dcc82cdf4000aff13a6c11fffe19096cf45, 2f81cffa9da9db0e2802d303f94feaee8d2f54ec, a505190933365268d48139a5f197a3cfb5570870]:
a4b696def3a7eb18c1ae48b10fd3758a1874b6fe Thanks @Fryuni! - Fixes a regression in routing priority between index.astro and dynamic routes with rest parameters#9566 165cfc154be477337037185c32b308616d1ed6fa Thanks @OliverSpeir! - Allows remark plugins to pass options specifying how images in .md files will be optimized
#9661 d6edc7540864cf5d294d7b881eb886a3804f6d05 Thanks @ematipico! - Adds new helper functions for adapter developers.
Astro.clientAddress can now be passed directly to the app.render() method.const response = await app.render(request, { clientAddress: '012.123.23.3' });
Request and Response objects are now provided as static methods on the NodeApp class.http.createServer((nodeReq, nodeRes) => {
const request: Request = NodeApp.createRequest(nodeReq);
const response = await app.render(request);
await NodeApp.writeResponse(response, nodeRes);
});
Astro.cookies.set() can now be automatically added to the Response object by passing the addCookieHeader option to app.render().-const response = await app.render(request)
-const setCookieHeaders: Array<string> = Array.from(app.setCookieHeaders(webResponse));
-if (setCookieHeaders.length) {
- for (const setCookieHeader of setCookieHeaders) {
- headers.append('set-cookie', setCookieHeader);
- }
-}
+const response = await app.render(request, { addCookieHeader: true })
#9638 f1a61268061b8834f39a9b38bca043ae41caed04 Thanks @ematipico! - Adds a new i18n.routing config option redirectToDefaultLocale to disable automatic redirects of the root URL (/) to the default locale when prefixDefaultLocale: true is set.
In projects where every route, including the default locale, is prefixed with /[locale]/ path, this property allows you to control whether or not src/pages/index.astro should automatically redirect your site visitors from / to /[defaultLocale].
You can now opt out of this automatic redirection by setting redirectToDefaultLocale: false:
// astro.config.mjs
export default defineConfig({
i18n: {
defaultLocale: 'en',
locales: ['en', 'fr'],
routing: {
prefixDefaultLocale: true,
redirectToDefaultLocale: false,
},
},
});
#9671 8521ff77fbf7e867701cc30d18253856914dbd1b Thanks @bholmesdev! - Removes the requirement for non-content files and assets inside content collections to be prefixed with an underscore. For files with extensions like .astro or .css, you can now remove underscores without seeing a warning in the terminal.
src/content/blog/
post.mdx
- _styles.css
- _Component.astro
+ styles.css
+ Component.astro
Continue to use underscores in your content collections to exclude individual content files, such as drafts, from the build output.
#9567 3a4d5ec8001ebf95c917fdc0d186d29650533d93 Thanks @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 e9a72d9a91a3741566866bcaab11172cb0dc7d31 Thanks @blackmann! - Adds a new markdown.shikiConfig.transformers config 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 a5f1682347e602330246129d4666a9227374c832 Thanks @rossrobino! - Adds an experimental flag clientPrerender to prerender your prefetched pages on the client with the Speculation Rules API.
// astro.config.mjs
{
prefetch: {
prefetchAll: true,
defaultStrategy: 'viewport',
},
experimental: {
clientPrerender: true,
},
}
Enabling this feature overrides the default prefetch behavior globally to prerender links on the client according to your prefetch configuration. 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, prefetch will fall back to the supported strategy.
See the Prefetch Guide for more prefetch options and usage.
#9439 fd17f4a40b83d14350dce691aeb79d87e8fcaf40 Thanks @Fryuni! - Adds an experimental flag globalRoutePriority to prioritize redirects and injected routes equally alongside file-based project routes, following the same route priority order rules for all routes.
// astro.config.mjs
export default defineConfig({
experimental: {
globalRoutePriority: true,
},
});
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:
| Page | Current Behavior | Global Routing Priority Behavior |
|---|---|---|
/blog/tags/astro | Injected route /blog/[...slug] | Redirect to /tags/[tag] |
/blog/post/0 | Injected route /blog/[...slug] | File-based route /blog/post/[pid] |
/posts | File-based route /[page] | Redirect to /blog |
In 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.
#9719 7e1db8b4ce2da9e044ea0393e533c6db2561ac90 Thanks @bluwy! - Refactors Vite config to avoid Vite 5.1 warnings
#9439 fd17f4a40b83d14350dce691aeb79d87e8fcaf40 Thanks @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].astro will build routes of the form /blog/posts/1 and /blog/posts/a/pages/blog/[...slug].astro will build routes of a variety of forms, including blog/1 and /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 1539e04a8e5865027b3a8718c6f142885e7c8d88 Thanks @bluwy! - Simplifies HMR handling, improves circular dependency invalidation, and fixes Astro styles invalidation
Updated dependencies [165cfc154be477337037185c32b308616d1ed6fa, e9a72d9a91a3741566866bcaab11172cb0dc7d31]:
#9665 d02a3c48a3ce204649d22e17b1e26fb5a6a60bcf Thanks @bluwy! - Disables internal file watcher for one-off Vite servers to improve start-up performance
#9664 1bf0ddd2777ae5f9fde3fd854a9e75aa56c080f2 Thanks @bluwy! - Improves HMR for Astro style and script modules
#9668 74008cc23853ed507b144efab02300202c5386ed Thanks @Princesseuh! - Fix the passthrough image service not generating srcset values properly
#9693 d38b2a4fe827e956662fcf457d1f1f84832c2f15 Thanks @kidylee! - Disables View Transition form handling when the action property points to an external URL
#9678 091097e60ef38dadb87d7c8c1fc9cb939a248921 Thanks @ematipico! - Adds an error during the build phase in case i18n.routing.prefixDefaultLocale is set to true and the index page is missing.
#9659 39050c6e1f77dc21e87716d95e627a654828ee74 Thanks @Princesseuh! - Fix Astro wrongfully deleting certain images imported with ?url when used in tandem with astro:assets
#9685 35d54b3ddb3310ab4c505d49bd4937b2d25e4078 Thanks @lilnasy! - Fixes an issue where anchor elements within a custom component could not trigger a view transition.
#9642 cdb7bfa66260afc79b829b617492a01a709a86ef Thanks @martrapp! - Fixes an issue where View Transitions did not work when navigating to the 404 page
#9637 5cba637c4ec39c06794146b0c7fd3225d26dcabb Thanks @bluwy! - Improves environment variables replacement in SSR
#9658 a3b5695176cd0280438938c1d6caef478a571415 Thanks @martrapp! - Fixes an issue caused by trying to load text/partytown scripts during view transitions
#9657 a4f90d95ff97abe59f2a1ef0956cab257ae36838 Thanks @ematipico! - Fixes a bug where the custom status code wasn't correctly computed in the dev server
#9627 a700a20291e19cde23705e8e661e833aec7d3095 Thanks @lilnasy! - Adds a warning when setting cookies will have no effect
#9652 e72efd6a9a1e2a70488fd225529617ffd8418534 Thanks @bluwy! - Improves environment variables handling by using esbuild to perform replacements
#9560 8b9c4844f7b302380835154fab1c3489979fc07d Thanks @bluwy! - Fixes tsconfig alias with import.meta.glob
#9653 50f39183cfec4a4522c1f935d710e5d9b724993b Thanks @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.
#9618 401fd3e8c8957a3bed6469a622cd67b157ca303f Thanks @ldh3907! - Adds a second generic parameter to APIRoute to type the params
#9600 47b951b3888a5a8a708d2f9b974f12fba7ec9ed3 Thanks @jacobdalamb! - Improves tailwind config file detection when adding the tailwind integration using astro add tailwind
Tailwind config file ending in .ts, .mts or .cts will now be used instead of creating a new tailwind.config.mjs when the tailwind integration is added using astro add tailwind.
#9622 5156c740506cbf6ec85c95e1663c14cbd438d75b Thanks @bluwy! - Fixes the Sharp image service limitInputPixels option type
#9513 e44f6acf99195a3f29b8390fd9b2c06410551b74 Thanks @wtto00! - Adds a 'load' prefetch strategy to prefetch links on page load
#9377 fe719e27a84c09e46b515252690678c174a25759 Thanks @bluwy! - Adds "Missing ARIA roles check" and "Unsupported ARIA roles check" audit rules for the dev toolbar
#9573 2a8b9c56b9c6918531c57ec38b89474571331aee Thanks @bluwy! - Allows passing a string to --open and server.open to open a specific URL on startup in development
#9544 b8a6fa8917ff7babd35dafb3d3dcd9a58cee836d Thanks @bluwy! - Adds a helpful error for static sites when you use the astro preview command if you have not previously run astro build.
#9546 08402ad5846c73b6887e74ed4575fd71a3e3c73d Thanks @bluwy! - Adds an option for the Sharp image service to allow large images to be processed. Set limitInputPixels: false to bypass the default image size limit:
// astro.config.mjs
import { defineConfig } from 'astro/config';
export default defineConfig({
image: {
service: {
entrypoint: 'astro/assets/services/sharp',
config: {
limitInputPixels: false,
},
},
},
});
#9596 fbc26976533bbcf2de9d6dba1aa3ea3dc6ce0853 Thanks @Princesseuh! - Adds the ability to set a rootMargin setting when using the client:visible directive. This allows a component to be hydrated when it is near the viewport, rather than hydrated when it has entered the viewport.
<!-- Load component when it's within 200px away from entering the viewport -->
<Component client:visible={{ rootMargin: '200px' }} />
#9063 f33fe3190b482a42ebc68cc5275fd7f2c49102e6 Thanks @alex-sherwin! - Cookie encoding / decoding can now be customized
Adds new encode and decode functions to allow customizing how cookies are encoded and decoded. For example, you can bypass the default encoding via encodeURIComponent when adding a URL as part of a cookie:
---
import { encodeCookieValue } from './cookies';
Astro.cookies.set('url', Astro.url.toString(), {
// Override the default encoding so that URI components are not encoded
encode: (value) => encodeCookieValue(value),
});
---
Later, you can decode the URL in the same way:
---
import { decodeCookieValue } from './cookies';
const url = Astro.cookies.get('url', {
decode: (value) => decodeCookieValue(value),
});
---
#9593 3b4e629ac8c2fdb4b491bf01abc7794e2e100173 Thanks @bluwy! - Improves astro add error reporting when the dependencies fail to install
#9563 d48ab90fb41fbc0589cd2df711682a41382c03aa Thanks @martrapp! - Fixes back navigation to fragment links (e.g. #about) in Firefox when using view transitions
Co-authored-by: Florian Lefebvre [email protected] Co-authored-by: Sarah Rainsberger [email protected]
#9597 9fd24a546c45d48451da46637c14e7ed54dac76a Thanks @lilnasy! - Fixes an issue where configuring trailingSlash had no effect on API routes.
#9586 82bad5d6205672ed3f6a49d4de53d3a68367433e Thanks @martrapp! - Fixes page titles in the browser's drop-down for back / forward navigation when using view transitions
#9575 ab6049bd58e4d02f47d500f9db08a865bc7f09b8 Thanks @bluwy! - Sets correct process.env.NODE_ENV default when using the JS API
#9587 da307e4a080483f8763f1919a05fa2194bb14e22 Thanks @jjenzz! - Adds a CSSProperties interface that allows extending the style attribute
#9513 e44f6acf99195a3f29b8390fd9b2c06410551b74 Thanks @wtto00! - Ignores 3g in slow connection detection. Only 2g and slow-2g are considered slow connections.
#9571 ec71f03cfd9b8195fb21c92dfda0eff63b6ebeed Thanks @bluwy! - Removes telemetry for unhandled errors in the dev server
#9548 8049f0cd91b239c52e37d571e3ba3e703cf0e4cf Thanks @bluwy! - Fixes error overlay display on URI malformed error
#9504 8cc3d6aa46f438d668516539c34b48ad748ade39 Thanks @matiboux! - Implement i18n's getLocaleByPath function
#9547 22f42d11a4fd2e154a0c5873c4f516584e383b70 Thanks @bluwy! - Prevents ANSI codes from rendering in the error overlay
#9446 ede3f7fef6b43a08c9371f7a2531e2eef858b94d Thanks @alexnguyennz! - Toggle dev toolbar hitbox height when toolbar is visible
#9572 9f6453cf4972ac28eec4f07a1373feaa295c8864 Thanks @bluwy! - Documents supported --host and --port flags in astro preview --help
#9540 7f212f0831d8cd899a86fb94899a7cad8ec280db Thanks @matthewp! - Fixes remote images with encoded characters
#9559 8b873bf1f343efc1f486d8ef53c38380e2373c08 Thanks @sygint! - Adds 'starlight' to the displayed options for astro add
#9537 16e61fcacb98e6bd948ac240bc082659d70193a4 Thanks @walter9388! - <Image /> srcset now parses encoded paths correctly
#9522 bb1438d20d325acd15f3755c6e306e45a7c64bcd Thanks @Zegnat! - Add support for autocomplete attribute to the HTML button type.
#9531 662f06fd9fae377bed1aaa49adbba3542cced087 Thanks @bluwy! - Fixes duplicated CSS modules content when it's imported by both Astro files and framework components
#9501 eb36e95596fcdb3db4a31744e910495e22e3af84 Thanks @Princesseuh! - Export JSX namespace from astro/jsx-runtime for language tooling to consume
#9492 89a2a07c2e411cda32244b7b05d3c79e93f7dd84 Thanks @lilnasy! - Improves error message for the case where two similarly named files result in the same content entry.
#9532 7224809b73d2c3ec8e8aee2fa07463dc3b57a7a2 Thanks @bluwy! - Prevents unnecessary URI decoding when rendering a route
#9478 dfef925e1fd07f3efb9fde6f4f23548f2af7dc75 Thanks @lilnasy! - Improves errors in certain places to also report their causes.
#9463 3b0eaed3b544ef8c4ec1f7b0d5a8f475bcfeb25e Thanks @Princesseuh! - Update Sharp version to ^0.33.1
#9512 1469e0e5a915e6b42b9953dbb48fe57a74518056 Thanks @mingjunlu! - Prevents dev toolbar tooltip from overflowing outside of the screen
#9497 7f7a7f1aeaec6b327ae0e5e7470a4f46174bf8ae Thanks @lilnasy! - Adds a helpful warning message for when an exported API Route is not uppercase.
#9452 e83b5095f Thanks @florian-lefebvre! - Upgrades vite to latest
#9352 f515b1421 Thanks @tmcw! - Add a more descriptive error message when image conversion fails
#9486 f6714f677 Thanks @martrapp! - Fixes View Transition's form submission prevention, allowing preventDefault to be used.
#9461 429be8cc3 Thanks @Skn0tt! - update import created for astro create netlify
#9464 faf6c7e11 Thanks @Fryuni! - Fixes an edge case with view transitions where some spec-compliant Content-Type headers would cause a valid HTML response to be ignored.
#9400 1e984389b Thanks @bluwy! - Fixes importing dev toolbar apps from integrations on Windows
#9487 19169db1f Thanks @ematipico! - Improves logging of the generated pages during the build
#9460 047d285be Thanks @Princesseuh! - Fix Astro failing to build on certain exotic platform that reports their CPU count incorrectly
#9466 5062d27a1 Thanks @knpwrs! - Updates view transitions form handling with logic for the enctype attribute
#9458 fa3078ce9 Thanks @ematipico! - Correctly handle the error in case the middleware throws a runtime error
#9089 5ae657882 Thanks @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 c384f6924 Thanks @Princesseuh! - Fix some false positive in the audit logic of the dev toolbar
#9437 354a62c86 Thanks @dkobierski! - Fixes incorrect hoisted script paths when custom rollup output file names are configured
#9475 7ae4928f3 Thanks @ematipico! - Remove the manifest from the generated files in the dist/ folder.
#9419 151bd429b Thanks @matthewp! - Prevent Partytown from hijacking history APIs
#9426 c01cc4e34 Thanks @alexnguyennz! - Fixes warning for external URL redirects
#9445 f963d07f2 Thanks @natemoo-re! - Upgrades Astro's compiler to a crash when sourcemaps try to map multibyte characters
#9126 6d2d0e279 Thanks @lilnasy! - Fixes an issue where error pages were not shown when trailingSlash was set to "always".
#9434 c01580a2c Thanks @ematipico! - Improves the error message when a middleware doesn't return a Response
#9433 fcc2fd5b0 Thanks @ematipico! - Correctly merge headers from the original response when an error page is rendered
#9423 bda1d294f Thanks @matthewp! - Error when getImage is passed an undefined src
#9424 e1a5a2d36 Thanks @matthewp! - Prevents dev server from crashing on unhandled rejections, and adds a helpful error message
#9404 8aa17a64b Thanks @Princesseuh! - Fixed some newer HTML attributes not being included in our type definitions
#9414 bebf38c0c Thanks @Skn0tt! - Adds the feature name to logs about feature deprecation / experimental status.
#9418 2c168af67 Thanks @alexnguyennz! - Fix broken link in CI instructions
#9407 546d92c86 Thanks @matthewp! - Allows file URLs as import specifiers
#9380 ea0918259 Thanks @ematipico! - Correctly handle the rendering of i18n routes when output: "hybrid" is set
#9374 65ddb0271 Thanks @bluwy! - Fixes an issue where prerendered route paths that end with .mjs were removed from the final build
#9375 26f7023d6 Thanks @bluwy! - Prettifies generated route names injected by integrations
#9387 a7c75b333 Thanks @natemoo-re! - Fixes an edge case with astro add that could install a prerelease instead of a stable release version.
Prior to this change
astro add svelte installs [email protected]
After this change
astro add svelte installs [email protected]
Updated dependencies [270c6cc27]:
#9342 eb942942d Thanks @Princesseuh! - Fix missing is:inline type for the <slot /> element
#9343 ab0281aee Thanks @martrapp! - Adds source file properties to HTML elements only if devToolbar is enabled
#9336 c76901065 Thanks @FredKSchott! - dev: fix issue where 404 and 500 responses were logged as 200
#9339 0bb3d5322 Thanks @morinokami! - Fixed the log message to correctly display 'enabled' and 'disabled' when toggling 'Disable notifications' in the Toolbar.
#9331 cfb20550d Thanks @natemoo-re! - Updates an internal dependency (vitefu) to avoid a common peerDependency warning
#9327 3878a91be Thanks @doseofted! - Fixes an edge case for <form method="dialog"> when using View Transitions. Forms with method="dialog" no longer require an additional data-astro-reload attribute.
631e5d01b Thanks @ematipico! - Fixes an issue where logs that weren't grouped together by route when building the app.#9138 abf601233 Thanks @bluwy! - Updates the unified, remark, and rehype dependencies to latest. Make sure to update your custom remark and rehype plugins as well to be compatible with the latest versions.
Potentially breaking change: The default value of markdown.remarkRehype.footnoteBackLabel is changed from "Back to content" to "Back to reference 1". See the mdast-util-to-hast commit for more information.
#9181 cdabf6ef0 Thanks @bluwy! - Removes support for returning simple objects from endpoints (deprecated since Astro 3.0). You should return a Response instead.
ResponseWithEncoding is also removed. You can refactor the code to return a response with an array buffer instead, which is encoding agnostic.
The types for middlewares have also been revised. To type a middleware function, you should now use MiddlewareHandler instead of MiddlewareResponseHandler. If you used defineMiddleware() to type the function, no changes are needed.
#9263 3cbd8ea75 Thanks @bluwy! - Removes additional deprecated APIs:
astro/client-image type. You should use the astro/client type instead.rss support in getStaticPaths. You should use @astrojs/rss instead.Astro.request.params support. You should use Astro.params instead.#9271 47604bd5b Thanks @matthewp! - Renames Dev Overlay to Dev Toolbar
The previously named experimental Dev Overlay is now known as the Astro Dev Toolbar. Overlay plugins have been renamed as Toolbar Apps. All APIs have been updated to reflect this name change.
To not break existing APIs, aliases for the Toolbar-based names have been created. The previous API names will continue to function but will be deprecated in the future. All documentation has been updated to reflect Toolbar-based names.
#9122 1c48ed286 Thanks @bluwy! - Adds Vite 5 support. There are no breaking changes from Astro. Check the Vite migration guide for details of the breaking changes from Vite instead.
#9225 c421a3d17 Thanks @natemoo-re! - Removes the opt-in handleForms property for <ViewTransitions />. Form submissions are now handled by default and this property is no longer necessary. This default behavior can be disabled by setting data-astro-reload on relevant <form /> elements.
#9196 37697a2c5 Thanks @bluwy! - Removes support for Shiki custom language's path property. The language JSON file should be imported and passed to the option instead.
// astro.config.js
+ import customLang from './custom.tmLanguage.json'
export default defineConfig({
markdown: {
shikiConfig: {
langs: [
- { path: './custom.tmLanguage.json' },
+ customLang,
],
},
},
})
#9199 49aa215a0 Thanks @lilnasy! - This change only affects maintainers of third-party adapters. In the Integration API, the app.render() method of the App class has been simplified.
Instead of two optional arguments, it now takes a single optional argument that is an object with two optional properties: routeData and locals.
app.render(request)
- app.render(request, routeData)
+ app.render(request, { routeData })
- app.render(request, routeData, locals)
+ app.render(request, { routeData, locals })
- app.render(request, undefined, locals)
+ app.render(request, { locals })
The current signature is deprecated but will continue to function until next major version.
#9212 c0383ea0c Thanks @alexanderniebuhr! - Removes deprecated app.match() option, matchNotFound
#9168 153a5abb9 Thanks @bluwy! - Removes deprecated features from Astro 3.0
supportedAstroFeatures to specify a list of features they support.build.split and build.excludeMiddleware options are removed. Use functionPerRoute and edgeMiddleware from adapters instead.markdown.drafts option and draft feature is removed. Use content collections instead.getHeaders() exported from markdown files is removed. Use getHeadings() instead.#9105 6201bbe96 Thanks @FredKSchott! - Update CLI logging experience
#9200 b4b851f5a Thanks @ematipico! - Adds a new way to configure the i18n.locales array.
Developers can now assign a custom URL path prefix that can span multiple language codes:
// astro.config.mjs
export default defineConfig({
experimental: {
i18n: {
defaultLocale: 'english',
locales: ['de', { path: 'english', codes: ['en', 'en-US'] }, 'fr'],
},
},
});
With the above configuration, the URL prefix of the default locale will be /english/. When computing Astro.preferredLocale, Astro will use the codes.
#9115 3b77889b4 Thanks @natemoo-re! - Adds the astro preferences command to manage user preferences. User preferences are specific to individual Astro users, unlike the astro.config.mjs file which changes behavior for everyone working on a project.
User preferences are scoped to the current project by default, stored in a local .astro/settings.json file. Using the --global flag, user preferences can also be applied to every Astro project on the current machine. Global user preferences are stored in an operating system-specific location.
# Disable the dev overlay for the current user in the current project
npm run astro preferences disable devOverlay
# Disable the dev overlay for the current user in all Astro projects on this machine
npm run astro preferences --global disable devOverlay
# Check if the dev overlay is enabled for the current user
npm run astro preferences list devOverlay
#9139 459b26436 Thanks @bluwy! - Reworks Vite's logger to use Astro's logger to correctly log HMR messages
#9279 6a9669b81 Thanks @martrapp! - Improves consistency between navigations with and without <ViewTransitions>. See #9279 for more details.
#9161 bd0c2e9ae Thanks @bluwy! - Renames the entryPoint property of the injectRoute integrations API to entrypoint for consistency. A warning will be shown prompting you to update your code when using the old name.
#9129 8bfc20511 Thanks @FredKSchott! - Update error log formatting
#9118 000e8f465 Thanks @Princesseuh! - Redesign Dev Overlay main screen to show more information, such as the coolest integrations, your current Astro version and more.
#9118 000e8f465 Thanks @Princesseuh! - Fixes an issue where links with the same pathname as the current page, but different search params, were not prefetched.
#9275 0968cb1a3 Thanks @lilnasy! - Fixes an issue where html annotations relevant only to the dev server were included in the production build.
#9252 7b74ec4ba Thanks @ematipico! - Consistently emit fallback routes in the correct folders, and emit routes that consider trailingSlash
#9222 279e3c1b3 Thanks @matthewp! - Ensure the dev-overlay-window is anchored to the bottom
#9292 5428b3da0 Thanks @natemoo-re! - Improves display for astro preferences list command
#9235 9c2342c32 Thanks @Princesseuh! - Fix SVG icons not showing properly in the extended dropdown menu of the dev overlay
#9218 f4401c8c1 Thanks @matthewp! - Improve high contrast mode with the Dev Overlay
#9254 b750a161e Thanks @matthewp! - Improve highlight/tooltip positioning when in fixed positions
#9230 60cfa49e4 Thanks @FredKSchott! - Update the look and feel of the dev overlay
#9248 43ddb5217 Thanks @martrapp! - Adds properties of the submit button (name, value) to the form data of a view transition
#9170 8a228fce0 Thanks @natemoo-re! - Adds new accessibility audits to the Dev Toolbar's built-in Audits app.
The audits Astro performs are non-exhaustive and only capable of detecting a handful of common accessibility issues. Please take care to perform a thorough, manual audit of your site to ensure compliance with the Web Content Accessibility Guidelines (WCAG) international standard before publishing your site.
🧡 Huge thanks to the Svelte team for providing the basis of these accessibility audits!
#9149 0fe3a7ed5 Thanks @bluwy! - Removes vendored Vite's importMeta.d.ts file in favour of Vite 5's new vite/types/import-meta.d.ts export
#9295 3d2dbb0e5 Thanks @matthewp! - Remove aria-query package
This is another CJS-only package that breaks usage.
#9274 feaba2c7f Thanks @TheOtterlord! - Fix routing prefixes when prefixDefaultLocale is true
#9273 9887f2412 Thanks @alexanderniebuhr! - Exports type for Dev Toolbar App under correct name
#9150 710be505c Thanks @bluwy! - Refactors virtual modules exports. This should not break your project unless you import Astro's internal modules, including:
astro/middleware/namespaceastro/transitionsastro/transitions/routerastro/transitions/eventsastro/transitions/typesastro/prefetchastro/i18n#9227 4b8a42406 Thanks @matthewp! - Ensure overlay x-ray z-index is higher than the island
#9255 9ea3e0b94 Thanks @matthewp! - Adds instructions on how to hide the dev overlay
#9293 cf5fa4376 Thanks @matthewp! - Removes the 'a11y-role-has-required-aria-props' audit rule
This audit rule depends on a CommonJS module. To prevent blocking the 4.0 release the rule is being removed temporarily.
#9214 4fe523b00 Thanks @Princesseuh! - Fixes a number of small user experience bugs with the dev overlay
#9013 ff8eadb95 Thanks @bayssmekanique! - Returns the updated config in the integration astro:config:setup hook's updateConfig() API
Updated dependencies [abf601233, addb57c8e, c7953645e]:
#9295 3d2dbb0e5 Thanks @matthewp! - Remove aria-query package
This is another CJS-only package that breaks usage.
#9275 0968cb1a3 Thanks @lilnasy! - Fixes an issue where html annotations relevant only to the dev server were included in the production build.
#9292 5428b3da0 Thanks @natemoo-re! - Improves display for astro preferences list command
#9293 cf5fa4376 Thanks @matthewp! - Removes the 'a11y-role-has-required-aria-props' audit rule
This audit rule depends on a CommonJS module. To prevent blocking the 4.0 release the rule is being removed temporarily.
6a9669b81 Thanks @martrapp! - Improves consistency between navigations with and without <ViewTransitions>. See #9279 for more details.#9170 8a228fce0 Thanks @natemoo-re! - Adds new accessibility audits to the Dev Toolbar's built-in Audits app.
The audits Astro performs are non-exhaustive and only capable of detecting a handful of common accessibility issues. Please take care to perform a thorough, manual audit of your site to ensure compliance with the Web Content Accessibility Guidelines (WCAG) international standard before publishing your site.
🧡 Huge thanks to the Svelte team for providing the basis of these accessibility audits!
#9274 feaba2c7f Thanks @TheOtterlord! - Fix routing prefixes when prefixDefaultLocale is true
#9273 9887f2412 Thanks @alexanderniebuhr! - Exports type for Dev Toolbar App under correct name
#9271 47604bd5b Thanks @matthewp! - Renames Dev Overlay to Dev Toolbar
The previously named experimental Dev Overlay is now known as the Astro Dev Toolbar. Plugins have been renamed as Toolbar Apps. This updates our references to reflect.
To not break existing APIs, aliases for the Toolbar-based names have been created. The previous API names will continue to function but will be deprecated in the future. All documentation has been updated to reflect Toolbar-based names.
3cbd8ea75 Thanks @bluwy! - Removes additional deprecated APIs:
astro/client-image type. You should use the astro/client type instead.rss support in getStaticPaths. You should use @astrojs/rss instead.Astro.request.params support. You should use Astro.params instead.#9200 b4b851f5a Thanks @ematipico! - Adds a new way to configure the i18n.locales array.
Developers can now assign a custom URL path prefix that can span multiple language codes:
// astro.config.mjs
export default defineConfig({
experimental: {
i18n: {
defaultLocale: 'english',
locales: ['de', { path: 'english', codes: ['en', 'en-US'] }, 'fr'],
routingStrategy: 'prefix-always',
},
},
});
With the above configuration, the URL prefix of the default locale will be /english/. When computing Astro.preferredLocale, Astro will use the codes.
#9139 459b26436 Thanks @bluwy! - Reworks Vite's logger to use Astro's logger to correctly log HMR messages
#9252 7b74ec4ba Thanks @ematipico! - Consistently emit fallback routes in the correct folders, and emit routes that
consider trailingSlash
#9235 9c2342c32 Thanks @Princesseuh! - Fix SVG icons not showing properly in the extended dropdown menu of the dev overlay
#9254 b750a161e Thanks @matthewp! - Improve highlight/tooltip positioning when in fixed positions
#9230 60cfa49e4 Thanks @FredKSchott! - Update the look and feel of the dev overlay
#9248 43ddb5217 Thanks @martrapp! - Adds properties of the submit button (name, value) to the form data of a view transition
#9255 9ea3e0b94 Thanks @matthewp! - Adds instructions on how to hide the dev overlay
#9013 ff8eadb95 Thanks @bayssmekanique! - Returns the updated config in the integration astro:config:setup hook's updateConfig() API
#9225 c421a3d17 Thanks @natemoo-re! - Removes the opt-in handleForms property for <ViewTransitions />. Form submissions are now handled by default and can be disabled by setting data-astro-reload on relevant <form /> elements.
#9199 49aa215a0 Thanks @lilnasy! - This change only affects maintainers of third-party adapters. In the Integration API, the app.render() method of the App class has been simplified.
Instead of two optional arguments, it now takes a single optional argument that is an object with two optional properties: routeData and locals.
app.render(request)
- app.render(request, routeData)
+ app.render(request, { routeData })
- app.render(request, routeData, locals)
+ app.render(request, { routeData, locals })
- app.render(request, undefined, locals)
+ app.render(request, { locals })
The current signature is deprecated but will continue to function until next major version.
#9212 c0383ea0c Thanks @alexanderniebuhr! - Removes deprecated app.match() option, matchNotFound
#9115 3b77889b4 Thanks @natemoo-re! - Adds the astro preferences command to manage user preferences. User preferences are specific to individual Astro users, unlike the astro.config.mjs file which changes behavior for everyone working on a project.
User preferences are scoped to the current project by default, stored in a local .astro/settings.json file. Using the --global flag, user preferences can also be applied to every Astro project on the current machine. Global user preferences are stored in an operating system-specific location.
# Disable the dev overlay for the current user in the current project
npm run astro preferences disable devOverlay
# Disable the dev overlay for the current user in all Astro projects on this machine
npm run astro preferences --global disable devOverlay
# Check if the dev overlay is enabled for the current user
npm run astro preferences list devOverlay
#9129 8bfc20511 Thanks @FredKSchott! - Update error log formatting
#9222 279e3c1b3 Thanks @matthewp! - Ensure the dev-overlay-window is anchored to the bottom
#9218 f4401c8c1 Thanks @matthewp! - Improve high contrast mode with the Dev Overlay
#9227 4b8a42406 Thanks @matthewp! - Ensure overlay x-ray z-index is higher than the island
#9214 4fe523b00 Thanks @Princesseuh! - Fixes a number of small user experience bugs with the dev overlay
#9118 000e8f465 Thanks @Princesseuh! - Redesign Dev Overlay main screen to show more information, such as the coolest integrations, your current Astro version and more.
#9118 000e8f465 Thanks @Princesseuh! - Fixes an issue where links with the same pathname as the current page, but different search params, were not prefetched.
#9138 abf601233 Thanks @bluwy! - Updates the unified, remark, and rehype dependencies to latest. Make sure to update your custom remark and rehype plugins as well to be compatible with the latest versions.
Potentially breaking change: The default value of markdown.remarkRehype.footnoteBackLabel is changed from "Back to content" to "Back to reference 1". See the mdast-util-to-hast commit for more information.
#9181 cdabf6ef0 Thanks @bluwy! - Removes support for returning simple objects from endpoints (deprecated since Astro 3.0). You should return a Response instead.
ResponseWithEncoding is also removed. You can refactor the code to return a response with an array buffer instead, which is encoding agnostic.
The types for middlewares have also been revised. To type a middleware function, you should now use MiddlewareHandler instead of MiddlewareResponseHandler. If you used defineMiddleware() to type the function, no changes are needed.
#9122 1c48ed286 Thanks @bluwy! - Adds Vite 5 support. There are no breaking changes from Astro. Check the Vite migration guide for details of the breaking changes from Vite instead.
#9196 37697a2c5 Thanks @bluwy! - Removes support for Shiki custom language's path property. The language JSON file should be imported and passed to the option instead.
// astro.config.js
+ import customLang from './custom.tmLanguage.json'
export default defineConfig({
markdown: {
shikiConfig: {
langs: [
- { path: './custom.tmLanguage.json' },
+ customLang,
],
},
},
})
#9168 153a5abb9 Thanks @bluwy! - Removes deprecated features from Astro 3.0
supportedAstroFeatures to specify a list of features they support.build.split and build.excludeMiddleware options are removed. Use functionPerRoute and edgeMiddleware from adapters instead.markdown.drafts option and draft feature is removed. Use content collections instead.getHeaders() exported from markdown files is removed. Use getHeadings() instead.#9105 6201bbe96 Thanks @FredKSchott! - Update CLI logging experience
#9161 bd0c2e9ae Thanks @bluwy! - Renames the entryPoint property of the injectRoute integrations API to entrypoint for consistency. A warning will be shown prompting you to update your code when using the old name.
#9149 0fe3a7ed5 Thanks @bluwy! - Removes vendored Vite's importMeta.d.ts file in favour of Vite 5's new vite/types/import-meta.d.ts export
#9150 710be505c Thanks @bluwy! - Refactors virtual modules exports. This should not break your project unless you import Astro's internal modules, including:
astro/middleware/namespaceastro/transitionsastro/transitions/routerastro/transitions/eventsastro/transitions/typesastro/prefetchastro/i18nUpdated dependencies [abf601233, addb57c8e, c7953645e]: