AstroEco is Releasing…
Display your GitHub releases using astro-loader-github-releases

🚀 Features
- Integrate Giscus comments - by @lin-stephanie in #28 (fb951)
- Add
UI.postMetaStyle
to set post metadata style ('minimal'
for plain text,'icon'
for icon-prefixed); hide modified date on mobile - by @lin-stephanie (29e8a)
🐞 Bug Fixes
- Missing shadow on mobile toc panel & docs error - by @lin-stephanie (1368d)
- Icon jitter when toggling code collapse - by @lin-stephanie (0ffec)
💅 Refactors
- Load medium-zoom only on post pages & format code - by @lin-stephanie (ae6d6)
🏡 Chore
- Update docs for Giscus and
UI.postMetaStyle
- by @lin-stephanie (96cd0) - Update deps - by @lin-stephanie (14c02)
View changes on GitHub

Patch Changes
-
#13761
a2e8463
Thanks @jp-knj! - Adds new content collections errors -
#13788
7d0b7ac
Thanks @florian-lefebvre! - Fixes a case where an error would not be thrown when using the<Font />
component from the experimental fonts API without adding fonts in the Astro config -
#13784
d7a1889
Thanks @florian-lefebvre! - Fixes the experimental fonts API to correctly takeconfig.base
,config.build.assets
andconfig.build.assetsPrefix
into account -
#13777
a56b8ea
Thanks @L4Ph! - Fixed an issue where looping GIF animation would stop when converted to WebP -
#13566
0489d8f
Thanks @TheOtterlord! - Fix build errors being ignored when build.concurrency > 1

Patch Changes
-
#13792
7910fea
Thanks @alexeyzimarev! - Unify imported images detection across adapters -
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

Patch Changes
-
#13792
7910fea
Thanks @alexeyzimarev! - Unify imported images detection across adapters -
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

Patch Changes
-
#13772
83193d4
Thanks @Adammatthiesen! - Fix options parsing for the libsql client connection to ensure that proper values are being set when adding URLSearchParams to theASTRO_DB_REMOTE_URL
-
#13783
1609044
Thanks @Adammatthiesen! - Modify Database type to allow transactions to be properly typed now that Astro Studio has sunset.

Minor Changes
-
#13753
90293de
Thanks @mattyoho! - Customize the filenames of sitemap XML files generated by the@astro/sitemap
integration by settingfilenameBase
in the integration configuration settings. This may be useful when deploying an Astro site at a path on a domain with preexisting sitemap files.Generated sitemap files will appear at
/sitemap-0.xml
and/sitemap-index.xml
by default, which may conflict with preexisting files. SetfilenameBase
to a custom value to avoid that if so:import { defineConfig } from 'astro/config'; import sitemap from '@astrojs/sitemap'; export default defineConfig({ site: 'https://example.com', integrations: [ sitemap({ filenameBase: 'astronomy-sitemap', }), ], });
This will yield sitemap and index files as
https://example.com/astronomy-sitemap-0.xml
andhttps://example.com/astronomy-sitemap-index.xml
.

Patch Changes
-
#13752
a079c21
Thanks @florian-lefebvre! - Improves handling of font URLs not ending with a file extension when using the experimental fonts API -
#13750
7d3127d
Thanks @martrapp! - Allows the ClientRouter to open new tabs or windows when submitting forms by clicking while holding the Cmd, Ctrl, or Shift key. -
#13765
d874fe0
Thanks @florian-lefebvre! - Fixes a case where font sources with relative protocol URLs would fail when using the experimental fonts API -
#13640
5e582e7
Thanks @florian-lefebvre! - Allows inferringweight
andstyle
when using the local provider of the experimental fonts APIIf you want Astro to infer those properties directly from your local font files, leave them undefined:
{ // No weight specified: infer style: 'normal'; // Do not infer }
Patch Changes
-
#3058
274cc06
Thanks @techfg! - Fixes display of focus indicator around site title -
#3181
449c822
Thanks @HiDeoo! - Fixes an issue where all headings in Markdown and MDX content were rendered with a clickable anchor link, even in non-Starlight pages. -
#3168
ca693fe
Thanks @jsparkdev! - Updates Korean langage support with improvements and missing translations

Patch Changes
-
#13734
30aec73
Thanks @ascorbic! - Loosen content layer schema types -
#13751
5816b8a
Thanks @florian-lefebvre! - Updatesunifont
to support subsets when using thegoogle
provider with the experimental fonts API -
#13756
d4547ba
Thanks @florian-lefebvre! - Adds a terminal warning when a remote provider returns no data for a family when using the experimental fonts API -
#13742
f599463
Thanks @florian-lefebvre! - Fixes optimized fallback css generation to properly add asrc
when using the experimental fonts API -
#13740
6935540
Thanks @vixalien! - Fix cookies set after middleware did a rewrite withnext(url)
not being applied -
#13759
4a56d0a
Thanks @jp-knj! - Improved the error handling of certain error cases.
Patch Changes
-
#3153
ea31f46
Thanks @SuperKXT! - Fixes hover styles for highlighted directory in FileTree component. -
#2905
b5232bc
Thanks @HiDeoo! - Fixes a potential issue for projects with dynamic routes added by an user, an Astro integration, or a Starlight plugin where some styles could end up being missing. -
#3165
80a7871
Thanks @KianNH! - IncreasesmaxBuffer
for an internalspawnSync()
call to support larger Git commit histories when using Starlight'slastUpdated
feature. -
#3158
d1f3c8b
Thanks @heisenberg0924! - Adds Hungarian language support

🚨 Breaking Changes
- Upgrade from Astro 4.16 to Astro 5.7 and more - by @lin-stephanie in #25 (089b9)
🏡 Chore
- Update docs for Astro 5.7 upgrade - by @lin-stephanie (ef781)
View changes on GitHub

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
-
#13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE -
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
-
#13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE -
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.1

Patch Changes
-
#13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE -
Updated dependencies [
c3e80c2
]:- @astrojs/studio@0.1.9

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE

Patch Changes
- #13731
c3e80c2
Thanks @jsparkdev! - update vite to latest version for fixing CVE


Patch Changes
- #13720
e1cd1ae
Thanks @florian-lefebvre! - Fixes SSR renderer type

Patch Changes
- #13720
e1cd1ae
Thanks @florian-lefebvre! - Fixes SSR renderer type

Patch Changes
- #13720
e1cd1ae
Thanks @florian-lefebvre! - Fixes SSR renderer type


Patch Changes (aec3423
)
- Update the entry Zod schema
- Resolve
<Content />
becomes non-functional whenfetchThread: true
is set

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13663
a19a185
Thanks @florian-lefebvre! - Improves type-safety of renderers

Patch Changes
- #13663
a19a185
Thanks @florian-lefebvre! - Improves type-safety of renderers

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13663
a19a185
Thanks @florian-lefebvre! - Improves type-safety of renderers

Patch Changes
-
#13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code -
Updated dependencies [
5dd2d3f
]:- @astrojs/underscore-redirects@0.6.1

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
-
#13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code -
Updated dependencies [
5dd2d3f
]:- @astrojs/underscore-redirects@0.6.1

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
- #13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code

Patch Changes
-
#13591
5dd2d3f
Thanks @florian-lefebvre! - Removes unused code -
Updated dependencies [
5dd2d3f
]:- @astrojs/studio@0.1.8
Patch Changes
- #3132
5959919
Thanks @HiDeoo! - Fixes an issue where all border styles were not reset by the Starlight’s Tailwind compatibility package like in Tailwind base styles.

Patch Changes
- #13636
a9fd03f
Thanks @sarah11918! - Updates the wording for choosing the "minimal" starter template options
Major Changes
-
#2322
f14eb0c
Thanks @HiDeoo! -⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.34.0Please use the
@astrojs/upgrade
command to upgrade your project:npx @astrojs/upgrade
-
#2322
f14eb0c
Thanks @HiDeoo! - Adds support for Tailwind v4, drops support for Tailwind v3.⚠️ BREAKING CHANGE: Tailwind v3 is no longer supported. Tailwind v4 support in Astro is now provided using a Vite plugin and the Astro Tailwind integration is no longer required.-
Remove the Astro Tailwind integration. The Astro Tailwind integration is no longer required with Tailwind v4.
// astro.config.mjs import { defineConfig } from "astro/config"; import starlight from "@astrojs/starlight"; -import tailwind from "@astrojs/tailwind"; export default defineConfig({ integrations: [ starlight({ title: "Docs with Tailwind", customCss: ["./src/tailwind.css"], }), - tailwind({ applyBaseStyles: false }), ], });
-
Install Tailwind v4. Install the latest version of the
tailwindcss
and@tailwindcss/vite
packages.Use the
astro add tailwind
command to install and configure both packages:npx astro add tailwind
-
Update Tailwind base styles. Tailwind CSS base styles needs to be updated for Tailwind v4 and also to use Starlight Tailwind CSS.
/* src/tailwind.css */ -@tailwind base; -@tailwind components; -@tailwind utilities; +@layer base, starlight, theme, components, utilities; + +@import '@astrojs/starlight-tailwind'; +@import 'tailwindcss/theme.css' layer(theme); +@import 'tailwindcss/utilities.css' layer(utilities); + +@theme { + /* + Configure your Tailwind theme that will be used by Starlight. + https://starlight.astro.build/guides/css-and-tailwind/#styling-starlight-with-tailwind + */ +} + +/* +Add additional Tailwind styles to this file: +https://tailwindcss.com/docs/adding-custom-styles#using-custom-css +*/
-
Update Tailwind customizations. If you previously customized your Tailwind theme configuration in the
tailwind.config.mjs
file, such customizations are now defined through CSS using the@theme
block in your Tailwind base styles.-
Locate existing customizations in your
tailwind.config.mjs
file. The following example defines customizations for the accent colors, gray scale, and font families used by Starlight:// tailwind.config.mjs import starlightPlugin from '@astrojs/starlight-tailwind'; import colors from 'tailwindcss/colors'; /** @type {import('tailwindcss').Config} */ export default { content: ['./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}'], theme: { extend: { colors: { // Custom accent colors. accent: colors.fuchsia, // Custom gray scale. gray: colors.slate, }, fontFamily: { // Custom text font. sans: ['"Atkinson Hyperlegible"'], // Custom code font. mono: ['"IBM Plex Mono"'], }, }, }, plugins: [starlightPlugin()], };
-
The above customizations can be migrated to the new
@theme
block in the file containing your Tailwind base styles as follows:/* src/tailwind.css */ @layer base, starlight, theme, components, utilities; @import '@astrojs/starlight-tailwind'; @import 'tailwindcss/theme.css' layer(theme); @import 'tailwindcss/utilities.css' layer(utilities); @theme { /* Custom accent colors. */ --color-accent-50: var(--color-fuchsia-50); --color-accent-100: var(--color-fuchsia-100); --color-accent-200: var(--color-fuchsia-200); --color-accent-300: var(--color-fuchsia-300); --color-accent-400: var(--color-fuchsia-400); --color-accent-500: var(--color-fuchsia-500); --color-accent-600: var(--color-fuchsia-600); --color-accent-700: var(--color-fuchsia-700); --color-accent-800: var(--color-fuchsia-800); --color-accent-900: var(--color-fuchsia-900); --color-accent-950: var(--color-fuchsia-950); /* Custom gray scale. */ --color-gray-50: var(--color-slate-50); --color-gray-100: var(--color-slate-100); --color-gray-200: var(--color-slate-200); --color-gray-300: var(--color-slate-300); --color-gray-400: var(--color-slate-400); --color-gray-500: var(--color-slate-500); --color-gray-600: var(--color-slate-600); --color-gray-700: var(--color-slate-700); --color-gray-800: var(--color-slate-800); --color-gray-900: var(--color-slate-900); --color-gray-950: var(--color-slate-950); /* Custom text font. */ --font-sans: 'Atkinson Hyperlegible'; /* Custom code font. */ --font-mono: 'IBM Plex Mono'; }
-
We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.
For full details about upgrading from Tailwind v3 to v4, see the official upgrade guide.
-
Minor Changes
-
#2322
f14eb0c
Thanks @HiDeoo! - Groups all of Starlight's CSS declarations into a singlestarlight
cascade layer.This change allows for easier customization of Starlight's CSS as any custom unlayered CSS will override the default styles. If you are using cascade layers in your custom CSS, you can use the
@layer
CSS at-rule to define the order of precedence for different layers including the ones used by Starlight.We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.
-
#3122
3a087d8
Thanks @delucis! - Removes defaultattrs
andcontent
values from head entries parsed using Starlight’s schema.Previously when adding
head
metadata via frontmatter or user config, Starlight would automatically add values forattrs
andcontent
if not provided. Now, these properties are leftundefined
.This makes it simpler to add tags in route middleware for example as you no longer need to provide empty values for
attrs
andcontent
:head.push({ tag: 'style', content: 'div { color: red }' - attrs: {}, }); head.push({ tag: 'link', - content: '' attrs: { rel: 'me', href: 'https://example.com' }, });
This is mostly an internal API but if you are overriding Starlight’s
Head
component or processing head entries in some way, you may wish to double check your handling ofAstro.locals.starlightRoute.head
is compatible withattrs
andcontent
potentially beingundefined
. -
#3033
8c19678
Thanks @delucis! - Adds support for generating clickable anchor links for headings.By default, Starlight now renders an anchor link beside headings in Markdown and MDX content. A new
<AnchorHeading>
component is available to achieve the same thing in custom pages built using<StarlightPage>
.If you want to disable this new Markdown processing set the
markdown.headingLinks
option in your Starlight config tofalse
:starlight({ title: 'My docs', markdown: { headingLinks: false, }, }),
⚠️ BREAKING CHANGE: The minimum supported version of Astro is now v5.5.0.Please update Starlight and Astro together:
npx @astrojs/upgrade
-
#2322
f14eb0c
Thanks @HiDeoo! - Removes Shikicss-variables
theme fallback.⚠️ BREAKING CHANGE:Previously, Starlight used to automatically provide a fallback theme for Shiki, the default syntax highlighter built into Astro if the configured Shiki theme was not
github-dark
.This fallback was only relevant when the default Starlight code block renderer, Expressive Code, was disabled and Shiki was used. Starlight no longer provides this fallback.
If you were relying on this behavior, you now manually need to update your Astro configuration to use the Shiki
css-variables
theme to match the previous behavior.import { defineConfig } from 'astro/config'; export default defineConfig({ + markdown: { + shikiConfig: { + theme: 'css-variables', + }, + }, });
Additionally, you can use custom CSS to control the appearance of the code blocks. Here are the previously used CSS variables for the fallback theme:
:root { --astro-code-foreground: var(--sl-color-white); --astro-code-background: var(--sl-color-gray-6); --astro-code-token-constant: var(--sl-color-blue-high); --astro-code-token-string: var(--sl-color-green-high); --astro-code-token-comment: var(--sl-color-gray-2); --astro-code-token-keyword: var(--sl-color-purple-high); --astro-code-token-parameter: var(--sl-color-red-high); --astro-code-token-function: var(--sl-color-red-high); --astro-code-token-string-expression: var(--sl-color-green-high); --astro-code-token-punctuation: var(--sl-color-gray-2); --astro-code-token-link: var(--sl-color-blue-high); }
Patch Changes
Minor Changes
-
#3033
8c19678
Thanks @delucis! - Adds support for generating clickable anchor links for headings.By default, the Starlight Markdoc preset now includes a default
heading
node, which renders an anchor link beside headings in your Markdoc content.If you want to disable this new feature, pass
headingLinks: false
in your Markdoc config:export default defineMarkdocConfig({ // Disable the default heading anchor link support extends: [starlightMarkdoc({ headingLinks: false })], });
⚠️ BREAKING CHANGE: The minimum supported peer version of Starlight is now v0.34.0.Please update Starlight and the Starlight Markdoc preset together:
npx @astrojs/upgrade

Minor Changes
-
#13527
2fd6a6b
Thanks @ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:
--- export const prerender = false; // Not needed with 'server' output const cart = await Astro.session.get('cart'); --- <a href="/checkout">🛒 {cart?.length ?? 0} items</a>
Configuring session storage
Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.
If you are using an adapter that doesn't have a default driver, or if you want to choose a different driver, you can configure it using the
session
configuration option:import { defineConfig } from 'astro/config'; import vercel from '@astrojs/vercel'; export default defineConfig({ adapter: vercel(), session: { driver: 'upstash', }, });
Using sessions
Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.
In pages and components, you can access the session using
Astro.session
:--- const cart = await Astro.session.get('cart'); --- <a href="/checkout">🛒 {cart?.length ?? 0} items</a>
In endpoints, actions, and middleware, you can access the session using
context.session
:export async function GET(context) { const cart = await context.session.get('cart'); return Response.json({ cart }); }
If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be
undefined
and an error will be logged in the console:--- export const prerender = true; const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined ---
Upgrading from Experimental to Stable
If you were previously using the experimental API, please remove the
experimental.session
flag from your configuration:import { defineConfig } from 'astro/config'; import node from '@astrojs/node'; export default defineConfig({ adapter: node({ mode: "standalone", }), - experimental: { - session: true, - }, });
See the sessions guide for more information.

Minor Changes
-
#13527
2fd6a6b
Thanks @ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:
--- export const prerender = false; // Not needed with 'server' output const cart = await Astro.session.get('cart'); --- <a href="/checkout">🛒 {cart?.length ?? 0} items</a>
Configuring session storage
Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.
If you are using an adapter that doesn't have a default driver, or if you want to choose a different driver, you can configure it using the
session
configuration option:import { defineConfig } from 'astro/config'; import vercel from '@astrojs/vercel'; export default defineConfig({ adapter: vercel(), session: { driver: 'upstash', }, });
Using sessions
Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.
In pages and components, you can access the session using
Astro.session
:--- const cart = await Astro.session.get('cart'); --- <a href="/checkout">🛒 {cart?.length ?? 0} items</a>
In endpoints, actions, and middleware, you can access the session using
context.session
:export async function GET(context) { const cart = await context.session.get('cart'); return Response.json({ cart }); }
If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be
undefined
and an error will be logged in the console:--- export const prerender = true; const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined ---
Upgrading from Experimental to Stable
If you were previously using the experimental API, please remove the
experimental.session
flag from your configuration:import { defineConfig } from 'astro/config'; import node from '@astrojs/node'; export default defineConfig({ adapter: node({ mode: "standalone", }), - experimental: { - session: true, - }, });
See the sessions guide for more information.
Patch Changes
- Updated dependencies []:
- @astrojs/underscore-redirects@0.6.0

Minor Changes
-
#13527
2fd6a6b
Thanks @ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:
--- export const prerender = false; // Not needed with 'server' output const cart = await Astro.session.get('cart'); --- <a href="/checkout">🛒 {cart?.length ?? 0} items</a>
Configuring session storage
Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.
If you are using an adapter that doesn't have a default driver, or if you want to choose a different driver, you can configure it using the
session
configuration option:import { defineConfig } from 'astro/config'; import vercel from '@astrojs/vercel'; export default defineConfig({ adapter: vercel(), session: { driver: 'upstash', }, });
Using sessions
Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.
In pages and components, you can access the session using
Astro.session
:--- const cart = await Astro.session.get('cart'); --- <a href="/checkout">🛒 {cart?.length ?? 0} items</a>
In endpoints, actions, and middleware, you can access the session using
context.session
:export async function GET(context) { const cart = await context.session.get('cart'); return Response.json({ cart }); }
If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be
undefined
and an error will be logged in the console:--- export const prerender = true; const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined ---
Upgrading from Experimental to Stable
If you were previously using the experimental API, please remove the
experimental.session
flag from your configuration:import { defineConfig } from 'astro/config'; import node from '@astrojs/node'; export default defineConfig({ adapter: node({ mode: "standalone", }), - experimental: { - session: true, - }, });
See the sessions guide for more information.
Patch Changes
- Updated dependencies []:
- @astrojs/underscore-redirects@0.6.0

Minor Changes
-
#13578
406501a
Thanks @stramel! - The SVG import feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.This feature allows you to import SVG files directly into your Astro project as components and inline them into your HTML.
To use this feature, import an SVG file in your Astro project, passing any common SVG attributes to the imported component.
--- import Logo from './path/to/svg/file.svg'; --- <Logo <Logo width={64} height={64} fill="currentColor" />
If you have been waiting for stabilization before using the SVG Components feature, you can now do so.
If you were previously using this feature, please remove the experimental flag from your Astro config:
import { defineConfig } from 'astro' export default defineConfig({ - experimental: { - svg: true, - } })
Additionally, a few features that were available during the experimental stage were removed in a previous release. Please see the v5.6.0 changelog for details if you have not yet already updated your project code for the experimental feature accordingly.
Please see the SVG Components guide in docs for more about this feature.

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version -
Updated dependencies [
3752519
,360cb91
]:- @astrojs/studio@0.1.7

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version -
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.0

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version

Patch Changes
-
#13596
3752519
Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91
Thanks @jsparkdev! - Updates vite to the latest version -
Updated dependencies []:
- @astrojs/underscore-redirects@0.6.0

Patch Changes (981ee1a
)
- Refactor first parameter type of exported
renderPostAsHtml
from PostView to RichTextProps - Update docs
Last fetched: | Scheduled refresh: Every Saturday
See Customizing GitHub Activity Pages to configure your own
Inspired by releases.antfu.me