Skip to content

AstroEco is Contributing…

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

withastro/astro

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

Releases

@astrojs/solid-js@8.0.0

Major Changes

  • #17891 6fb274e Thanks @ryansolid! - Adds support for Solid 2.0 (requires solid-js@^2.0.0 and @solidjs/web@^2.0.0)

    This major version supports Solid 2.0 only; use @astrojs/solid-js@7 (and @astrojs/solid-js-renderer@0.1) for Solid 1.x projects. The Solid 2.0 renderer lives in @astrojs/solid-js-renderer, which the integration re-exports.

    Highlights:

    • Compiles through @solidjs/vite-plugin (replacing vite-plugin-solid), with an optional compiler option to select the native or Babel backend.
    • Islands render through Solid 2.0's first-class async model (renderToStream), with no Suspense wrapper: async islands settle fully on the server, and error boundaries (Errored) contain both sync and async errors.
    • Threads an asset manifest into server renders so lazy() boundary modules inside islands resolve their module URLs, hydrate through serialized asset maps, and have their CSS inlined into the island markup (deduped per page) — in dev via the plugin's live resolver, in production via the client build manifest.
    • Component detection (check()) now probe-renders through the stream renderer with per-component caching, rejects foreign framework vnodes explicitly, and no longer breaks on Proxy-based components.
    • Removes the solid-devtools integration option (the Solid 2.0 devtools story is not settled yet).

Minor Changes

  • #17891 6fb274e Thanks @ryansolid! - Adds support for Solid server components (experimental)

    Enable with serverFunctions: { components: true } — "use server" functions that return a component, riding the server-function endpoint:

    // src/frames/panel.jsx
    'use server';
    
    export async function getPanel(name) {
      return (props) => (
        <section>
          <h2>panel:{name}</h2>
          {props.children}
        </section>
      );
    }
    // inside an island
    const Panel = dynamic(() => getPanel(name()));

    Server components render inline during island SSR and are adopted at boot with zero endpoint requests; re-evaluations stream over the endpoint and morph the boundary in place, preserving client slot state and DOM identity. The integration wires all the pieces: the frames render plugin and direct-call transform on the server, the endpoint response transform through the handler, and installServerComponents() via Astro's before-hydration stage on the client.

  • #17891 6fb274e Thanks @ryansolid! - Adds support for Solid server functions (experimental)

    Enable with the serverFunctions option (requires an adapter — server functions need a server at runtime):

    import { defineConfig } from 'astro/config';
    import solid from '@astrojs/solid-js';
    
    export default defineConfig({
      integrations: [solid({ serverFunctions: true })],
    });

    "use server" functions imported by Solid islands are compiled to typed RPC calls. The integration injects the transport endpoint (default /_server) as an Astro route, so server-function requests flow through Astro's middleware pipeline — the same auth guards and locals decoration pages get — in dev and production alike. Inside a server function, Solid's getRequestEvent() exposes the request, Astro's locals, and the full Astro API context as nativeEvent.

    Island SSR now also runs inside a Solid request-event scope, so getRequestEvent() and direct in-process server function calls work during server rendering.

    Pass an options object instead of true to customize (endpoint path, argument codec, etc.) — it is forwarded to @solidjs/vite-plugin.

Patch Changes

  • Updated dependencies [6fb274e]:
    • @astrojs/solid-js-renderer@0.2.0

@astrojs/solid-js-renderer@0.2.0

Minor Changes

  • #17891 6fb274e Thanks @ryansolid! - Adds support for Solid 2.0 (requires solid-js@^2.0.0 and @solidjs/web@^2.0.0)

    This major version supports Solid 2.0 only; use @astrojs/solid-js@7 (and @astrojs/solid-js-renderer@0.1) for Solid 1.x projects. The Solid 2.0 renderer lives in @astrojs/solid-js-renderer, which the integration re-exports.

    Highlights:

    • Compiles through @solidjs/vite-plugin (replacing vite-plugin-solid), with an optional compiler option to select the native or Babel backend.
    • Islands render through Solid 2.0's first-class async model (renderToStream), with no Suspense wrapper: async islands settle fully on the server, and error boundaries (Errored) contain both sync and async errors.
    • Threads an asset manifest into server renders so lazy() boundary modules inside islands resolve their module URLs, hydrate through serialized asset maps, and have their CSS inlined into the island markup (deduped per page) — in dev via the plugin's live resolver, in production via the client build manifest.
    • Component detection (check()) now probe-renders through the stream renderer with per-component caching, rejects foreign framework vnodes explicitly, and no longer breaks on Proxy-based components.
    • Removes the solid-devtools integration option (the Solid 2.0 devtools story is not settled yet).

astro@7.4.14

Patch Changes

  • #17891 6fb274e Thanks @ryansolid! - Updates the Solid tsconfig preset for Solid 2.0: astro add solid-js now writes jsxImportSource: "@solidjs/web" (renderer packages own their JSX namespaces and jsx-runtime type entries in 2.0; solid-js no longer exports one)
withastro/astro

Fixes #18781.

Changes

  • A sitemap chunk that rewrites a URL now keeps the original entry out of the default sitemap.
  • The integration records which input entries matched and uses the callback's returned item for the named chunk. Returning the URL of a different page does not remove that other page from the default sitemap.
  • A custom pages chunk keeps its matched entries alongside unmatched entries in sitemap-pages-0.xml.

The Factory preview addresses the original URL leak for named chunks. This patch also preserves the returned items when the chunk is named pages, where the default sitemap would otherwise overwrite them. Factory preview

Testing

  • The chunked sitemap test covers an async callback that returns a copy with a rewritten URL. It checks both the named chunk and the default sitemap. A second case covers a custom pages chunk.

Verification

The same fixture was built first with Astro 7.4.13 and @astrojs/sitemap 3.7.6, then with the patched integration. Minimal reproduction

Before, sitemap-pages-0.xml
https://example.com/
https://example.com/article/

After, sitemap-pages-0.xml
https://example.com/

The named chunk contains https://example.com/articles/current/ in both builds.

Docs

No docs change is needed. The existing docs already describe the default sitemap as containing URLs that did not match a chunk.

withastro/astro

Changes

  • tsconfig paths aliases (e.g. ~/markdoc/...) used inside markdoc.config.* now resolve correctly instead of failing with Cannot find package '~'. This regressed in 2.0.11 when bundleConfigFile() switched from esbuild to Rolldown.
  • Replaced the bare external predicate in load-config.ts with a Rolldown externalize-deps plugin. The plugin resolves each bare import specifier before deciding whether to externalize it. Imports that resolve to a file inside the project root and outside node_modules (i.e. what a tsconfig paths alias points to) are bundled; everything else stays external with its original specifier, matching the previous esbuild behavior.

Testing

  • Added packages/integrations/markdoc/test/units/load-config.test.ts covering the alias-resolution path: a config file that imports via a tsconfig paths alias is bundled successfully, while true third-party package imports remain external.

Docs

  • No docs update needed — this restores previously documented behavior with no API changes.

Closes #18779

withastro/astro

Changes

  • When vite.build.cssMinify or vite.build.minify is set to "esbuild", Astro now detects at build start whether esbuild can be resolved from Vite and fails with a descriptive MissingEsbuild error — instead of surfacing Node's raw ERR_MODULE_NOT_FOUND. This was broken by #18263, which removed esbuild as a direct Astro dependency; Vite 8 treats it as an optional peer, so projects that relied on hoisting now fail silently.
  • Implemented as a small Vite buildStart plugin that checks resolvability before Vite attempts the import. No runtime overhead for projects that don't use esbuild minification.

Testing

  • Added packages/astro/test/units/build/plugin-esbuild-check.test.ts, which covers the cases where cssMinify: "esbuild" or minify: "esbuild" is configured without esbuild installed (expects the new error) and where esbuild is resolvable (expects no error).

Docs

  • No docs update needed; this is a developer-facing error message improvement with no new API surface.

Closes #18774

withastro/astro

Changes

  • Removes the scrollend event listener and the 50 ms polling fallback from ClientRouter. Both called history.replaceState() on every frame of a requestAnimationFrame-driven scroll, which in Safari 26.2+ hits the browser's 100-writes-per-10-seconds limit and causes internal links to silently do nothing for 10 seconds.
  • Scroll positions are now kept in an in-memory map keyed by the router's history index and recorded only when an entry is left: in transition(), in the Navigation API navigate event (covering location.hash changes and third-party pushState calls), and via a passive scroll listener as a fallback for browsers without the Navigation API. The whole map is serialized to sessionStorage in pagehide and read back at init, so positions survive reloads and cross-document navigations. history.state is kept as a fallback for entries created by older router versions.

Testing

  • Added e2e tests in packages/astro/e2e/view-transitions.test.ts covering: a rAF-driven scroll makes zero history.replaceState() calls; Back/Forward after a scripted scroll restores the correct position; reload after a traversal then Back restores correctly; location.hash change then Back restores the pre-hash position; third-party pushState then Back.

Docs

  • No docs update needed. This is an internal scroll-position bookkeeping change with no public API surface.

Closes #18761

withastro/astro

Changes

  • Removes the fetch() fallback from getImageSize() in the dev toolbar audit. In Safari/WebKit, re-fetching an SVG that is currently animating freezes the animation; this was triggered for loading="lazy" images because WebKit reports all three resource timing size fields (decodedBodySize, encodedBodySize, transferSize) as 0 for lazy images.
  • getImageSize() now reads size from decodedBodySize ?? encodedBodySize ?? transferSize and skips the size check entirely when no size is available, rather than fetching. Eager images that are still loading are awaited; unloaded lazy images are skipped to avoid blocking the whole audit on below-the-fold content.

Testing

  • Added an e2e test in packages/astro/e2e/dev-toolbar-audits.test.ts asserting that opening the Audit app makes no extra network request for a loading="lazy" image, covering the WebKit-specific regression path in Chromium.

Docs

  • No docs update needed; this is an internal dev-only audit behavior fix with no user-facing API changes.

Closes #18700

withastro/astro

Changes

  • a11y-missing-content no longer reports false positives for anchors inside visibility: hidden containers or inside an aria-hidden="true" subtree. These elements are invisible to both sighted users and assistive technologies, so warning about their content is misleading and can produce thousands of spurious reports on sites that hide menus with visibility: hidden.
  • Adds two early returns to the rule's match(): one checking computed visibility !== 'visible' (inherited, so covers hidden ancestors), and one checking element.closest('[aria-hidden="true"]'). Computed style is used instead of checkVisibility({ visibilityProperty: true }) for broader browser compatibility.

Testing

  • Extended the existing e2e dev-toolbar audit test (packages/astro/e2e/dev-toolbar-audits.test.ts) with a new fixture a11y-hidden-anchor.astro covering the two previously false-positive cases (visibility-hidden container and aria-hidden anchor) alongside the control cases. The visible-anchor-with-hidden-text warning introduced in #16016 is still reported.

Docs

  • No docs update needed; this is a dev-only audit tool behavior fix with no public API impact.

Closes #18623

withastro/astro

Changes

  • Fixes island CSS that was missing or loaded twice when the same component is imported statically by one island and with import() by another. This covers #18767 and the double load on pages that render both islands, without bringing back #18677.
  • The client build no longer decides globally whether to keep or delete a client CSS file. For each chunk, it walks up from the chunk's CSS modules to the hydrated components, client:only components and scripts that load them, statically or through import(). It then adds the chunk's CSS to each of those pages, unless the page's server build already has all of it (cssScopeTo-aware, propagated content included).
  • Page-attributed CSS is removed from importedCss, so Vite's preload never loads it again under another URL. Files no page links are deleted. CSS reachable only from entries not attributed to any page (e.g. injectScript('page')) keeps the old preload behavior.
  • Behavior change: CSS of modules that an island loads with import(), where the server build can't see the import, now ships in the page HTML instead of loading when the import runs. This matches how client:only components, scripts and server-visible dynamic imports already work. The preload list is shared by every page, so it can't skip a file only on the pages that already have its styles.
  • Replaces shouldDeleteCSSChunk, getChunksSharedByIslands, the cssScopeTo restore path and the client:only force-inline workaround from #17292.

Testing

  • Rewrote css-deduplication.test.ts as a matrix over inlineStylesheets never, auto and always. For every page it collects the head CSS plus whatever Vite's preload would add once all dynamic imports run, and asserts each style loads exactly once where expected and nowhere else. It also checks for missing files, CSS that only arrives through preload, and unused CSS files.
  • Added fixture pages for each historical case: #12303, #18677, #18678, #18767 (React, and the reporter's Svelte repro), both islands on one page, a lazy module sharing CSS with islands on other pages, client:only sharing a lazily loaded file, a server-visible import(), #16119, #18123 and #16251 (Svelte conditional rendering). Main fails 11 of the 60 checks, and the previous version of this PR failed 16.
  • The 'always' assertion goes back to "no CSS files are emitted", since every style is now inlined.

Docs

  • No docs update needed: this is a build-output fix with no API or config changes.

Closes #18767

withastro/astro

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

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@astrojs/cloudflare@15.0.0-beta.6

Patch Changes

  • #18754 d342812 Thanks @edmundhung! - Updates @cloudflare/vite-plugin to 2.0.0-rc.0. Build output is now written to .cloudflare/output/v1/. Rebuild existing projects before running astro preview or deploying with cf.
withastro/astro

Changes

  • createAsyncManifestMemo previously cached the pending promise indefinitely (evicting only on rejection). On Cloudflare Workers, a promise can only settle in the request that created it; if that request is cancelled while a shared load (middleware, session driver, cache provider, actions, or logger) is still in flight, the cached promise never settles and never rejects. Every subsequent request that awaits it throws "This promise was created by a request that has since ended", causing a burst of 500s until the isolate is recycled.
  • When a waiting caller's shared promise fails, the fix now removes the stale entry and retries the load once inside that caller's own request. Concurrent requests still share one in-flight load when nothing goes wrong, and a load that genuinely fails for all callers still rejects.

Testing

  • packages/astro/test/units/manifest/memo.test.ts covers the new retry path: a shared promise that rejects causes the waiting caller to evict the cache entry and start a fresh load, while a load that fails on every attempt still propagates the rejection.

Docs

  • No docs update needed; this is an internal runtime fix with no public API change.

Closes #18764

withastro/astro

Changes

  • getHeadings() and render().headings no longer turn { into ${ for .md headings when using the unified() processor. The .replace(/\{/g, '${') call in rehypeHeadingIds was left over from 2021 when heading text was serialized into a JS template literal; headings are now serialized with JSON.stringify, so the escaping is both unnecessary and harmful.
  • One line removed from packages/markdown/remark/src/rehype-collect-headings.ts. No change to rendered HTML or generated slugs.

Testing

  • Added a regression test in packages/markdown/remark/test/headings.test.ts covering a .md heading that contains { to assert the returned text matches the literal heading string.

Docs

  • No docs update needed; this is a bug fix restoring already-documented behavior.

Closes #18716

withastro/astro

Changes

  • ASTRO_DEV_BACKGROUND=0 (and ASTRO_PREVIEW_BACKGROUND=0) now correctly records "background": false in the lock file. Previously, !!process.env.ASTRO_DEV_BACKGROUND evaluated !!'0' as true, making a foreground server appear as a background server and causing astro dev status to report background and astro dev logs to exit with "No log file found."
  • Introduces a small isBackgroundServerProcess(envVar) helper in cli/server.ts that checks env[envVar] === '1', matching the value the background spawner sets. Both astro dev and astro preview now use this helper when writing the lock file.

Testing

  • Adds packages/astro/test/units/dev/background-env.test.ts covering the isBackgroundServerProcess helper: verifies that =0, unset, and =1 all produce the correct boolean so the lock file reflects the true server mode.

Docs

  • No docs update needed; the existing Background mode documentation already describes the =0 opt-out correctly — only the implementation was wrong.

Closes #18719

withastro/astro

Changes

  • Fixes #18728. Since #18187, every platform-specific VSIX shipped only the runner's linux-x64-gnu @astrojs/compiler-binding, so formatting failed with Cannot find native binding everywhere else.
  • The extension is now published as one universal VSIX using the compiler's WASI build, like astro2tsx. The new packaging step installs with --cpu=wasm32, runs vsce package, then reinstalls for the host because ovsx needs the native @node-rs/crc32. Both marketplaces publish that file with --packagePath.

Testing

  • No test code added; this is a release workflow change.

Docs

  • No docs update needed; this only affects how the extension is packaged.
withastro/starlight

Description

  • Closes #1748
  • Moves <Banner /> out of <main> in Page.astro so it sits above <TwoColumnContent /> inside .main-frame. On wide viewports (>= 72rem) with a table of contents, the banner now spans the full width of the content area (both .main-pane and .right-sidebar-container) and appears centered instead of being constrained to .main-pane.
  • Updates .right-sidebar sticky positioning in TwoColumnContent.astro (top: var(--sl-nav-height), height: calc(100vh - var(--sl-nav-height)), border moved onto .right-sidebar) so the right sidebar starts below the banner at scroll top and pins beneath the navbar when scrolling.
  • Adds role="region" and a localized aria-label (banner.accessibleLabel, seeded in built-in translation files since builtinI18nSchema() requires all keys) to Banner.astro so the banner remains a unique accessible landmark outside <main>.
  • Updates starlight-toc.ts to continue observing .sl-banner now that it is no longer a descendant of <main>.
  • Adds Playwright E2E assertions covering banner alignment, landmark attributes, and sticky right-sidebar scroll behavior in packages/starlight/__e2e__/basics.test.ts, plus an @astrojs/starlight patch changeset.

Local verification after final edits:

  • Build and publint check (pnpm --filter '@astrojs/*' build)
  • Example build and size-limit check (pnpm --filter @example/starlight-basics build and pnpm size)
  • prettier --check on all modified files
  • Playwright E2E suite __e2e__/basics.test.ts: 52 passed
  • Targeted source and built dist Vitest suites (i18n, translations, translations-fs, translations-ec, config-errors, starlight-page-route-data): 84 passed in both source and dist modes
  • axe-playwright audit (wcag2a, wcag21a, wcag2aa, wcag21aa, wcag22aa, best-practice) on built /headings-banner/, /custom-page/, and /headings/ pages: 0 violations
withastro/astro

Changes

  • Uses ephemeral ports for the custom entry file fixture so parallel test files cannot redirect requests to an unrelated port.

Testing

  • Updates the preview and dev tests for the custom entry file to use an ephemeral port.

Docs

  • No docs update is needed because this change only affects test setup.

AI was used to diagnose and implement this change.

withastro/astro

Changes

@cloudflare/vite-plugin v2 and cf 1.0 are moving from beta to release candidates. This moves @astrojs/cloudflare on next from the plugin beta to its RC.

  • Moves @cloudflare/vite-plugin from an exact beta pin to ^2.0.0-rc.0, which brings in the 1.0 RCs of @cloudflare/config and @cloudflare/build-output-utils. The exact pin protected against breaking changes between betas. RCs should not have breaking changes, so the range accepts later RCs and 2.x without another bump, but not betas.
  • Replaces ParsedInputConfigWithWorker, which the RC removes, with WorkerConfig and CloudflareConfig.
  • Reads Build Output from .cloudflare/output/v1/ instead of v0/ in astro preview and the tests. A build clears the whole .cloudflare/output/ directory, so rebuilding removes any old v0 output.
  • Updates cf in the adapter test fixtures and packages/astro/e2e/fixtures/cloudflare to ^1.0.0-rc.0, and exempts cf@1.0.0-rc.0 from minimumReleaseAge.

astro add @astrojs/cloudflare@beta needs no change. It installs cf@latest, and cf publishes its RC under latest.

This overlaps with #18742, which moves the same pin to 2.0.0-beta.v.17.

Testing

The existing adapter tests cover these code paths. They are updated for the v1 output paths and the renamed types. No new tests, because behavior is otherwise unchanged.

Docs

No docs change. Users don't configure or reference the Build Output path directly.

withastro/astro

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

Releases

astro@7.4.13

Patch Changes

  • #18770 c850735 Thanks @astro-factory! - Fixes the dev toolbar's a11y-missing-content audit reporting anchors and headings that are hidden with visibility: hidden or are inside an aria-hidden="true" subtree

  • #18536 d044365 Thanks @KoenRijpstra! - Fixes server bundles including every renderable content collection entry when no server-rendered route calls render() from astro:content

  • #18740 c7a2f1d Thanks @astro-factory! - Fixes i18n.fallback failing with i18nNoLocaleFoundInPath when the fallback target is a locale defined with a custom path

  • #18660 75ac226 Thanks @NetBr3ak! - Fixes <Font preload> emitting no preload links when a requested weight range such as "400 700" sits inside a variable font file's range such as "400 900"

  • #18758 273d7da Thanks @astro-factory! - Fixes astro dev status, astro dev logs, and the astro preview equivalents treating a server started with ASTRO_DEV_BACKGROUND=0 or ASTRO_PREVIEW_BACKGROUND=0 as a background server

  • #18658 33c931e Thanks @hood! - Improves startup time of every astro command for projects that don't configure fonts, by loading the font resolution dependencies only when fonts are used

  • #18771 01c942d Thanks @astro-factory! - Fixes the dev toolbar's audit fetching loading="lazy" images again to measure them, which froze animated SVGs in Safari and downloaded images the page meant to load later

  • #18711 bf5a170 Thanks @astro-factory! - Fixes the dev server blocking cross-origin requests from an origin allowed by a security.allowedDomains entry with a default port, such as { hostname: 'staging.myapp.com', protocol: 'https', port: '443' }. BaseApp.validateForwardedHost() now applies the same allowedDomains rules as the rest of Astro.

  • #18733 c6ab3c5 Thanks @Marve10s! - Fixes hydration of framework components receiving sparse array props by serializing holes as undefined

  • Updated dependencies [c6ab3c5]:

    • @astrojs/runtime@0.1.2

@astrojs/cloudflare@14.4.9

Patch Changes

  • #18720 d116e3d Thanks @astro-factory! - Fixes a spurious No environment found in configuration warning for the prerender worker when building with CLOUDFLARE_ENV set

@astrojs/node@11.1.14

Patch Changes

  • #18636 b4de3b5 Thanks @umeraamir69! - Shares one process unhandledRejection listener across app handlers so standalone mode no longer treats in-request rejections as outside request context

  • #18743 7c8dad5 Thanks @EnesKartal! - Adds Content-Type: text/plain; charset=utf-8 header to 400 responses for undecodable URLs in standalone mode.

@astrojs/sitemap@3.7.6

Patch Changes

  • #18622 1dab71a Thanks @Toyenzo! - Fixes i18n locale matching for pages whose first path segment is named like an Object.prototype property, such as /constructor/ or /toString/. These were treated as locales, producing invalid alternate links. Also rejects an i18n defaultLocale that is only an inherited object property rather than a configured locale.

astro-vscode@2.17.5

Patch Changes

  • #18757 3ac5ad3 Thanks @matthewp! - Fixes formatting .astro files failing with Cannot find native binding on Windows, macOS, and ARM or Alpine Linux

@astrojs/markdown-remark@7.3.10

Patch Changes

  • #18759 387105b Thanks @astro-factory! - Fixes getHeadings() and render().headings reporting { as ${ in Markdown heading text when using the unified() processor

@astrojs/runtime@0.1.2

Patch Changes

  • #18733 c6ab3c5 Thanks @Marve10s! - Fixes hydration of framework components receiving sparse array props by serializing holes as undefined
withastro/astro

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@astrojs/astro2tsx (source) ^0.1.3 → ^0.1.4 age confidence dependencies patch
@astrojs/compiler-rs (source) ^0.5.1 → ^0.5.3 age confidence dependencies patch
@astrojs/compiler-rs (source) ^0.5.1 → ^0.5.3 age confidence devDependencies patch
@astrojs/compiler-rs (source) ^0.5.2 → ^0.5.3 age confidence dependencies patch
@babel/core (source) ^8.1.0 → ^8.1.2 age confidence devDependencies patch
@clack/prompts (source) ^1.8.1 → ^1.9.0 age confidence dependencies minor
@cloudflare/vite-plugin (source) ^1.67.0 → ^1.69.1 age confidence dependencies minor
@cloudflare/vitest-plugin (source) 1.6.0 → 1.8.1 age confidence devDependencies minor 1.8.2
@cloudflare/workers-types ^5.20261106.1 → ^5.20261113.1 age confidence devDependencies minor 5.20261116.1 (+2)
@codspeed/vitest-plugin (source) ^6.1.0 → ^6.1.1 age confidence devDependencies patch
@hono/node-server ^2.1.6 → ^2.1.8 age confidence dependencies patch
@markdoc/markdoc (source) ^0.5.11 → ^0.5.12 age confidence dependencies patch 0.5.13
@netlify/blobs (source) ^11.1.7 → ^11.1.9 age confidence dependencies patch
@netlify/functions (source) ^6.1.0 → ^6.1.1 age confidence dependencies patch
@qwik.dev/partytown ^1.0.4 → ^1.0.5 age confidence dependencies patch
@rolldown/plugin-babel (source) ^0.3.0 → ^0.3.1 age confidence devDependencies patch
@solidjs/router ^1.0.1 → ^1.0.3 age confidence dependencies patch
@tailwindcss/vite (source) ^4.3.4 → ^4.3.5 age confidence dependencies patch
@vercel/functions (source) ^3.11.0 → ^3.11.2 age confidence dependencies patch 3.11.3
@vitejs/plugin-react (source) ^6.1.2 → ^6.3.0 age confidence dependencies minor
@vitejs/plugin-react (source) ^6.2.1 → ^6.3.0 age confidence dependencies minor
@vitejs/plugin-vue (source) ^6.0.10 → ^6.0.11 age confidence dependencies patch
@vitejs/plugin-vue (source) ^6.0.10 → ^6.0.11 age confidence devDependencies patch
@volar/kit (source) ~2.4.30 → ~2.4.31 age confidence dependencies patch
@volar/language-core (source) ~2.4.30 → ~2.4.31 age confidence devDependencies patch
@volar/language-core (source) ~2.4.30 → ~2.4.31 age confidence dependencies patch
@volar/language-server (source) ~2.4.30 → ~2.4.31 age confidence devDependencies patch
@volar/language-server (source) ~2.4.30 → ~2.4.31 age confidence dependencies patch
@volar/language-service (source) ~2.4.30 → ~2.4.31 age confidence dependencies patch
@volar/test-utils (source) ~2.4.30 → ~2.4.31 age confidence devDependencies patch
@volar/typescript (source) ~2.4.30 → ~2.4.31 age confidence dependencies patch
@volar/typescript (source) ~2.4.30 → ~2.4.31 age confidence devDependencies patch
@volar/vscode (source) ~2.4.30 → ~2.4.31 age confidence devDependencies patch
@vscode/vsce (source) ^4.1.0 → ^4.1.1 age confidence devDependencies patch
ci-info ^4.4.0 → ^4.5.0 age confidence dependencies minor
devalue ^6.0.2 → ^6.0.3 age confidence dependencies patch
hast-util-from-html ^2.0.3 → ^2.1.0 age confidence dependencies minor
hono (source) ^4.13.16 → ^4.13.18 age confidence dependencies patch
hono (source) ^4.13.16 → ^4.13.18 age confidence devDependencies patch
hono (source) ^4.13.13 → ^4.13.18 age confidence dependencies patch
magic-string ^1.4.2 → ^1.4.5 age confidence dependencies patch
muggle-string ^1.0.3 → ^1.0.4 age confidence dependencies patch
neotraverse (source) ^1.0.1 → ^1.0.2 age confidence dependencies patch
node (source) 26.13.0 → 26.13.1 age confidence patch
node 26.13.0 → 26.13.1 age confidence uses-with patch
ovsx (source) ^1.3.0 → ^1.4.0 age confidence devDependencies minor
oxc-transform-react (source) ^0.157.0 → ^0.158.0 age confidence dependencies minor
oxc-transform-react (source) ^0.157.0 → ^0.158.0 age confidence devDependencies minor
preact (source) ^11.0.1 → ^11.2.0 age confidence dependencies minor
preact (source) ^11.1.1 → ^11.2.0 age confidence devDependencies minor
preact (source) ^11.1.1 → ^11.2.0 age confidence dependencies minor
preact-render-to-string ^6.8.2 → ^6.8.3 age confidence dependencies patch
prettier (source) ^3.9.10 → ^3.10.1 age confidence dependencies minor
prettier (source) ^3.9.10 → ^3.10.1 age confidence devDependencies minor
react (source) ^19.3.0 → ^19.3.1 age confidence dependencies patch
react-dom (source) ^19.3.0 → ^19.3.1 age confidence dependencies patch
rolldown (source) ~1.2.16 → ~1.3.2 age confidence dependencies minor
rolldown (source) ~1.2.16 → ~1.3.2 age confidence devDependencies minor
sass ^1.108.0 → ^1.108.2 age confidence devDependencies patch
sass ^1.108.0 → ^1.108.2 age confidence dependencies patch
satteri ^0.11.6 → ^0.11.7 age confidence dependencies patch
satteri ^0.11.6 → ^0.11.7 age confidence devDependencies patch
smol-toml ^1.9.0 → ^1.9.1 age confidence dependencies patch
solid-js (source) ^1.9.17 → ^1.9.19 age confidence dependencies patch
solid-js (source) ^1.9.18 → ^1.9.19 age confidence devDependencies patch
solid-js (source) ^1.9.18 → ^1.9.19 age confidence dependencies patch
svelte (source) ^5.57.2 → ^5.57.3 age confidence dependencies patch
tailwindcss (source) ^4.3.4 → ^4.3.5 age confidence dependencies patch
tinyps ^0.5.1 → ^0.5.2 age confidence dependencies patch
turbo (source) ^2.11.10 → ^2.11.11 age confidence devDependencies patch
typescript-eslint (source) ^8.72.1 → ^8.72.2 age confidence devDependencies patch
vite (source) ^8.3.3 → ^8.3.8 age confidence dependencies patch
vite (source) ^8.3.4 → ^8.3.8 age confidence dependencies patch
vite (source) ^8.3.3 → ^8.3.8 age confidence devDependencies patch
vite (source) ^8.3.5 → ^8.3.8 age confidence devDependencies patch
vite (source) ^8.3.6 → ^8.3.8 age confidence dependencies patch
vite (source) ^8.3.6 → ^8.3.8 age confidence devDependencies patch
vite-plugin-solid ^2.11.14 → ^2.11.16 age confidence dependencies patch
vite-plugin-solid ^2.11.15 → ^2.11.16 age confidence devDependencies patch
vite-plugin-solid ^2.11.15 → ^2.11.16 age confidence dependencies patch
vue (source) ^3.5.43 → ^3.5.45 age confidence dependencies patch
vue (source) ^3.5.44 → ^3.5.45 age confidence devDependencies patch
wrangler (source) ^4.158.0 → ^4.161.0 age confidence devDependencies minor 4.162.0
wrangler (source) ^4.158.0 → ^4.161.0 age confidence dependencies minor 4.162.0
zod (source) ^4.6.5 → ^4.6.7 age confidence dependencies patch

Release Notes

withastro/compiler-rs (@​astrojs/astro2tsx)

v0.1.4

Compare Source

Patch Changes
  • 81881cb: Moves @emnapi/runtime from devDependencies to dependencies so package managers that do not auto-install peer dependencies (e.g. Yarn 1) can load @astrojs/astro2tsx without a manual install.
withastro/compiler-rs (@​astrojs/compiler-rs)

v0.5.3

Compare Source

Patch Changes
babel/babel (@​babel/core)

v8.1.2

Compare Source

👓 Spec Compliance
  • babel-parser
  • babel-plugin-transform-regenerator, babel-plugin-transform-runtime
🐛 Bug Fix
  • babel-helper-module-transforms, babel-plugin-transform-dynamic-import, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-umd
  • babel-parser
  • babel-helper-member-expression-to-functions, babel-plugin-transform-classes, babel-plugin-transform-object-super, babel-plugin-transform-private-methods
  • babel-helper-string-parser, babel-parser
  • babel-generator
  • babel-plugin-transform-class-static-block
  • babel-template
  • babel-helper-module-transforms, babel-parser, babel-plugin-transform-modules-commonjs, babel-plugin-transform-react-pure-annotations, babel-plugin-transform-typescript, babel-traverse, babel-types
  • babel-plugin-transform-exponentiation-operator, babel-plugin-transform-logical-assignment-operators
  • babel-plugin-transform-flow-comments
  • babel-plugin-transform-block-scoping, babel-traverse
  • babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator, babel-runtime-corejs3
  • babel-traverse
  • babel-plugin-transform-regenerator
  • babel-helper-module-transforms, babel-plugin-transform-modules-commonjs
🏠 Internal
  • Other
  • babel-core, babel-helper-fixtures, babel-helper-transform-fixture-test-runner, babel-helpers, babel-node, babel-plugin-transform-runtime, babel-register, babel-template, babel-traverse, babel-types
🏃‍♀️ Performance
bombshell-dev/clack (@​clack/prompts)

v1.9.0

Compare Source

Minor Changes
  • #​596 cbeefcb Thanks @​dreyfus92! - Add accessible mode to spinner: when enabled via the accessible option, the global setting, or the ACCESSIBLE env var, the spinner emits static, append-only, screen-reader friendly output, a plain start line, a "still working" heartbeat every 30 seconds, and a plain final line. Instead of animated in-place repaints.

  • #​614 5ac9e73 Thanks @​btea! - Allow multiselect to accept readonly option arrays, e.g. options declared with as const. The Value type parameter is now inferred as a literal union ('a' | 'b') from such arrays, and initialValues also accepts readonly arrays.

  • #​622 1835f41 Thanks @​btea! - Add support for disabled selectKey options: they are rendered dimmed, cannot be selected by keypress, and are ignored when set as the initial value.

Patch Changes

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

withastro/astro

Summary

Fixes #18748.

When unifont's npm provider resolves installed fonts with remote: false, it returns local file: URLs (pathToFileURL(filePath).href).

Previously, CachedFontFetcher.fetch() only checked isAbsolute(url). Since file: URLs fail isAbsolute(url), they were routed to fetch(url). In Node.js, fetch() fails when attempting to fetch file: scheme URLs with TypeError: fetch failed / CannotFetchFontFile.

Changes

  • In packages/astro/src/assets/fonts/infra/cached-font-fetcher.ts, check url.startsWith('file:') and convert to a local filesystem path using fileURLToPath(url).
  • Forward the converted path to the configured #readFile() handler.
  • Added unit test in packages/astro/test/units/assets/fonts/infra.test.ts.
  • Included changeset.
withastro/astro

Changes

Fixes #18744

In astro dev, using a custom Cloudflare Worker entrypoint with FetchState and the documented companion handler:

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext) {
    const state = new FetchState(request);
    const asset = await cf(state, env, ctx);
    if (asset) return asset;
    return finalize(state, await astro(state));
  },
};

caused every page with export const prerender = true to return 404.

Root Cause

  1. In production, prerendered pages are emitted as static assets, and fallbackToAssets serves them.
  2. In astro dev, static assets have not been built to disk. FetchState constructed from a bare request in a custom entrypoint lacks pre-populated render options, so it resolves routes with the production matcher which skips prerendered routes when manifest.serverLike is true, falling back to the 404 route.
  3. The adapter's default entrypoint calls app.devMatch() in dev mode, which allows prerendered routes.

Solution

In packages/integrations/cloudflare/src/fetch.ts, when app!.isDev(), match the request pathname using await app!.devMatch(app!.getPathnameFromRequest(state.request)) and assign state.routeData = result.routeData.
Added changeset .changeset/cloudflare-fetch-dev-prerender.md (@astrojs/cloudflare patch).

Testing

Verified with the reproduction from #18744:

  • In astro dev, visiting / (prerender = true) returns 200 with rendered page content instead of 404.
  • On-demand SSR routes (/ssr) and fallback asset handling continue to function as expected.

Docs

No documentation changes needed.

withastro/astro

Fixes #18739

Changes

  • Added an optional beforeSwap hook to doSwap() in packages/runtime/src/internal/transitions/events.ts, invoked after astro:before-swap and afterDispatch (fallback old-page animation) and immediately before event.swap().
  • Split moveToLocation() in packages/astro/src/transitions/router.ts into writeHistoryEntry() (run in beforeSwap so location.href and history.state are updated before event.swap() inserts the new DOM and triggers custom element connectedCallback()) and scrollToLocation() (run after doSwap() once the new DOM is in place).
  • Removed the now-unnecessary pageTitleForBrowserHistory temporary title juggling since writeHistoryEntry() runs before event.swap() overwrites document.title (and intra-page hash navigation keeps the same title).
  • Added a Playwright e2e regression test in packages/astro/e2e/view-transitions.test.ts verifying that custom elements upgraded during swap see the new URL and history.state, astro:before-swap still sees the previous URL, and history.replaceState() inside connectedCallback() updates the new entry without overwriting the previous page's entry.

Verification

  • pnpm run build:ci (34/34 packages built)
  • pnpm exec playwright test e2e/view-transitions.test.ts -g "custom elements upgraded during swap|history" --reporter=list (5 passed)
  • pnpm --filter @astrojs/runtime test (8 passed)
  • pnpm --filter astro test:types (passed)
  • pnpm exec biome ci --formatter-enabled=false packages/runtime/src/internal/transitions/events.ts packages/astro/src/transitions/router.ts packages/astro/e2e/view-transitions.test.ts (0 errors)
withastro/astro

Changes

Fixes #18739

During a <ClientRouter /> navigation, updateDOM previously executed doSwap() (and event.swap(), inserting the new DOM into document) before calling moveToLocation(), which writes the history entry.

Because inserting the new page synchronously upgrades and connects custom elements on it whose definitions are registered, their connectedCallback runs immediately and reads location and history.state of the previous page.
Furthermore, if a component writes to the URL during initialization (e.g. history.replaceState(...)), it overwrote the previous page's history entry, causing moveToLocation to find to.href === location.href and push nothing, corrupting browser history.

Solution

  • Add an optional beforeInsert?: (event: TransitionBeforeSwapEvent) => void hook to doSwap in packages/runtime/src/internal/transitions/events.ts.
  • In packages/astro/src/transitions/router.ts:
    • Split history entry writing into writeHistoryEntry(to, options, historyState).
    • Pass a beforeInsert callback to doSwap that sets document.title = pageTitleForBrowserHistory, calls writeHistoryEntry, and restores title right before event.swap().
    • Pass historyWritten = true to moveToLocation after swap so that only scroll restoration / hash positioning runs post-swap.
  • Added changeset .changeset/swap-history-before-insert.md (astro and @astrojs/runtime patch).

Testing

Verified with the reproduction from #18739:

  • Direct load on /b/?x=1 shows /b/?x=1.
  • Navigation from /a/ to /b/?x=1 now properly provides /b/?x=1 to the <url-reader> custom element during its connectedCallback.
  • Navigation from /a/ to /c/ with custom element calling replaceState retains /a/ in history, allowing Back navigation to return to /a/.

Docs

No documentation changes needed; this fixes internal ordering so that custom elements during client-side navigation observe standard page-load URL state.

withastro/astro

Fixes #18689

Changes

  • Added Content-Type: text/plain; charset=utf-8 header to the 400 Bad request. response in createStandaloneHandler (packages/integrations/node/src/standalone.ts) when decodeURI(req.url) throws.
  • Added unit test packages/integrations/node/test/units/standalone-handler.test.ts covering undecodable paths (/%C0%AF) and query strings (/?q=100%).
  • Added a patch changeset for @astrojs/node.

Testing

  • pnpm --filter @astrojs/node build (passed)
  • pnpm --filter @astrojs/node exec astro-scripts test test/units/*.test.ts (11/11 passed)
  • pnpm --filter @astrojs/node exec astro-scripts test test/bad-urls.test.ts (2/2 passed)
withastro/astro

Changes

Renaming a glob() content file with the same slug and contents leaves its old path cached and can break builds. Include the relative file path in the digest to refresh the entry and deferred import.

Testing

Content-layer tests (126) and Markdoc tests (2) passed. Regression tests cover eager and deferred rendering. Build, type and changed-file lint checks passed.

Docs

Existing file-renaming behavior is restored.

withastro/astro

Changes

  • optimizeFallbacks() now selects the most representative file for metric measurement before calling CapsizeFontMetricsResolver.getMetrics(). It prefers Latin subset, then normal style, then the weight closest to 400. Previously the resolver cached by family name and used whichever file the provider returned first—for Montserrat on Google that was Cyrillic and/or italic—so size-adjust varied with subset order and was wrong for Latin text.
  • With the fix, size-adjust for Montserrat is 112.83% regardless of which subsets or styles are configured, matching the value measured on rendered text in Chromium.

Testing

  • Extended packages/astro/test/units/assets/fonts/core.test.ts with cases covering Latin-only, Latin+Cyrillic, and Cyrillic+Latin configurations to assert that size-adjust is identical across all three and corresponds to the Latin upright 400 file.

Docs

  • No docs update needed; this is a correctness fix to an internal metric-selection step with no API or configuration surface change.

Closes #18736

withastro/astro

Changes

  • Cached routes returning 204, 205, or 304 no longer cause a 500 on cache hits. createResponseFromCacheEntry() now passes null as the body for null-body statuses ([101, 204, 205, 304]), matching the same list already used in core/app/prerender.ts. Previously, the empty ArrayBuffer stored on a cache miss was passed to the Response constructor, which the runtime rejects for these status codes, causing every hit (including SWR/stale reads) to throw and return a 500 until the entry expired.
  • The failing entry was not evicted after the error, so 500s repeated on every request until TTL elapsed.

Testing

  • Added unit tests in packages/astro/test/units/cache/memory-provider.test.ts covering cache hits for 204, 205, and 304 responses, verifying the correct status is returned and no error is thrown.

Docs

  • No docs update needed; this is a bug fix for existing documented behavior.

Closes #18721

withastro/starlight

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

Releases

@astrojs/starlight@0.43.1

Patch Changes

  • #4396 46a5020 Thanks @trueberryless! - Fixes a regression where the icon of the <Aside> component was rendered smaller than the icon of Markdown asides.
withastro/starlight

Description

This PR fixes a small regression introduced in #4190 I believe, where the icon of an <Aside> component is rendered smaller than the icon of a Markdown aside (:::note). It does so by specifically setting size="1.333em" on the Aside icon and also adding a regression test with fixture for the future.

withastro/starlight

This PR contains the following updates:

Package Type Update Change
peter-evans/create-pull-request action patch v8.1.2 → v8.1.3

Release Notes

peter-evans/create-pull-request

v8.1.3: Create Pull Request v8.1.3

Compare Source

What's Changed

Full Changelog: peter-evans/create-pull-request@v8.1.2...v8.1.3


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/starlight

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

Releases

@astrojs/starlight@0.43.0

Minor Changes

  • #4190 3f2336b Thanks @delucis! - ⚠️ BREAKING CHANGE: Adds support for any Astro scopedStyleStrategy configuration.

    Previously, Starlight forced the "where" strategy, resulting in CSS selectors like :where(.astro-HASH). Starlight now respects the strategy set in astro.config.mjs and will default to Astro’s default "attribute" strategy, resulting in attribute selectors like [data-astro-cid-HASH].

    The new default can change some styling behaviour, so we recommend checking for visual changes in your site when updating. In particular, note the following:

    • Attribute selectors have a higher specificity than :where() selectors. Check to ensure styles still apply and no CSS changes are needed to ensure the relative specificity of declarations remains the same.

    • Astro’s "attribute" strategy does not automatically pass along a parent component’s scope when passing a class down to a child component. If you have components that depended on this, you will need to update the child component to spread the parent’s data attribute where you are reusing the class name, for example:

      ---
      // Parent.astro
      ---
      
      <Child class="special-case" />
      
      <style>
        .special-case {
          --accent-color: red;
        }
      </style>
      ---
      // Child.astro
      -const { class: className } = Astro.props;
      +const { class: className, ...attributes } = Astro.props;
      ---
      
      -<div class={className}>
      +<div class={className} {...attributes}>
        <!-- ... -->
      </div>

      See “Passing a class to a child component” in the Astro docs for more details.

    Alternatively, if you wish to continue using the previous scoping strategy in your site, set it explicitly in your Astro configuration file:

    // astro.config.mjs
    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
    + scopedStyleStrategy: "where",
      // ...
    });
  • #3674 993ac27 Thanks @controversial! - Adds support for Pagefind’s excludeSelectors and includeCharacters configuration to customize how search indexes are built

  • #4219 35abe4f Thanks @delucis! - Refactors Starlight’s theme select menu to reduce its JavaScript use

    ⚠️ Potentially breaking change: If your project or theme plugin overrides the ThemeSelect component, check that it still works after updating. The global API previously used by theme select components has been removed and calling StarlightThemeProvider.updatePickers() will no longer work.

    See ThemeProvider.astro, ThemeSelect.astro, and LanguageSelect.astro on GitHub for the full source code of the updated components.

  • #4385 c130349 Thanks @delucis! - Updates dependency i18next to v27

    ⚠️ Potentially breaking change: If you use Starlight’s translation APIs directly, see i18next’s migration guide for details. We don’t expect any changes to impact Starlight users, but let us know if they do.

Patch Changes

  • #4390 f8b072a Thanks @Toyenzo! - Errors if an aside is passed an icon name that matches Object.prototype properties, such as constructor or toString
withastro/starlight

Description

  • Closes #4389
  • getAsideIconName() checked a custom aside icon with !Icons[iconName], which also matches properties inherited from Object.prototype. Icon names such as constructor, toString or __proto__ were accepted. With the default Markdown processor, the aside's <svg> then contained text like function Object() { [native code] }. With unified(), the build failed with a generic parse error instead of "Invalid aside icon".
  • The check now uses Object.hasOwn(Icons, iconName), the same approach as #4309 for autogenerated sidebars. This covers Markdown asides (both processors) and the <Aside> component, which share getAsideIconName().
  • Nothing visual changes for valid icons.

Tests:

  • New __tests__/basics/aside-utils.test.ts: covers default, valid and unknown icons, and checks that constructor, toString, hasOwnProperty and __proto__ throw "Invalid aside icon". The 4 prototype cases fail on main.
  • __tests__/markdown-processor/asides.test.ts: rendering :::note{icon="constructor" | "toString" | "__proto__"} now throws on both processors. On main, the satteri cases render instead of throwing.
  • The full @astrojs/starlight unit suite passes (693 tests), and Prettier and ESLint are clean on the changed files.
  • Changeset: @astrojs/starlight patch.
withastro/astro

Fixes #18732. This replaces #18431, which was closed for lack of an issue; the issue now has a minimal reproduction: https://github.com/Marve10s/astro-sparse-array-props-repro

Changes

  • Sparse array props stop framework components from hydrating. Array(2) passed as { items: Array(2) } serializes as {"items":[1,[null,null]]}, and the island decoder throws TypeError: t is not iterable on the bare null entries.
  • Array.prototype.map skips holes. serializeArray in @astrojs/runtime now uses Array.from, which visits every index, so each hole goes through the existing serializer as undefined and comes out as [0]: {"items":[1,[[0],[0]]]}.
  • The wire format and the client island script are unchanged. A hole and an explicit undefined entry now serialize the same way.

Testing

  • Two regressions in packages/astro/test/serialize.test.ts cover a sparse array and a nested sparse array. Both fail on main and pass with the fix; all 27 serializer tests pass.
  • I rebuilt the reproduction against Astro 7.4.11 with the patched serializer and loaded it in headless Chromium. Before the fix the island stays unhydrated and logs [hydrate] Error parsing props; after it, the component hydrates and the console has no errors.
  • Biome and Prettier pass on the changed files. I did not run the full test, typecheck, or e2e suites locally.

Docs

No docs change. Arrays are already supported as hydrated props, and this fixes their serialization without adding an API. A patch changeset covers astro and @astrojs/runtime.

withastro/astro

Changes

  • When CLOUDFLARE_ENV is set during astro build, the prerender worker's Vite preview() server would pass that env name to wrangler while reading the already-resolved dist/server/.prerender/wrangler.json. Because that generated config has no env sections (they were already merged during the main build), wrangler emitted a misleading "No environment found" warning for every build. The fix clears process.env.CLOUDFLARE_ENV to '' only for the duration of the prerender preview server startup, then restores the original value. The prerendered pages still receive the correct environment variables because the config was already resolved before this step.
  • Using '' instead of delete ensures that a CLOUDFLARE_ENV value coming from a .env file is also suppressed during this window.

Testing

  • Adds packages/integrations/cloudflare/test/prerender-cloudflare-env.test.ts, which builds a fixture with CLOUDFLARE_ENV set and asserts that the warning does not appear in the build output.

Docs

  • No docs update needed; this is a build-time warning fix with no user-facing API or configuration change.

Closes #18712

withastro/astro

Changes

errors-data.ts moved to packages/runtime/src/internal/core/errors/ in #18610, but the follow-up edits in that PR point at packages/runtime/src/core/errors/errors-data.ts, which does not exist.

Update the remaining references to the real path: the ESLint config for the docs-generation file, the docs path filter and docs pr labeler, plus the two Markdown links and the AGENTS.md path.

Testing

packages/runtime/src/core/errors/errors-data.ts returns 404 and packages/runtime/src/internal/core/errors/errors-data.ts exists on main. No code or behavior changes, only path strings.

Docs

No user-facing docs change and no changeset, this only corrects internal paths and links.

withastro/starlight

Description

  • Updates i18next to v27, the recently released new major version — might as well before v1 to not be too far behind
  • The breaking changes in this release seem to be minimal: https://www.i18next.com/misc/migration-guide (it’s a bit hard to read — not the most helpful guide I’ve ever encountered)
  • I chose to reverse the returnEmptyString change, which would be hard for users to work around if they were depending on it, whereas the v26 behaviour gives users more options.
  • Otherwise, I think the changes should be not noticeable (and certainly not to most users who do not use our translation APIs directly).
  • There is one change in a test due to i18next no longer escaping / in strings. The migration guide shows how to restore the old behaviour, but I don’t see why we would have to escape / so I decided to accept this change.
withastro/astro

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

Releases

astro@7.4.12

Patch Changes

  • #18409 2917650 Thanks @matthewp! - Fixes a typo in the error message shown when a font cssVariable is invalid

  • #18709 6f1a2a8 Thanks @ematipico! - Reduces memory usage during astro build by releasing content collection entries from memory once the content layer sync is complete.

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

  • Updated dependencies [59052e7]:

    • @astrojs/markdown-satteri@0.4.10
    • @astrojs/vite-plugin-astro@0.1.3

create-astro@5.3.2

Patch Changes

@astrojs/cloudflare@14.4.8

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/markdoc@2.1.5

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/mdx@8.1.6

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed
  • Updated dependencies [59052e7]:
    • @astrojs/markdown-satteri@0.4.10

@astrojs/netlify@8.2.14

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/node@11.1.13

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/preact@6.1.6

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed
  • Updated dependencies [59052e7]:
    • @astrojs/preact-renderer@0.1.3

@astrojs/react@7.1.9

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed
  • Updated dependencies [59052e7]:
    • @astrojs/react-renderer@0.1.3

@astrojs/sitemap@3.7.5

Patch Changes

  • #18149 71f4d06 Thanks @irontaek! - Speeds up sitemap chunk generation for large sites by tracking assigned URLs with a Set.

@astrojs/solid-js@7.1.6

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed
  • Updated dependencies [59052e7]:
    • @astrojs/solid-js-renderer@0.1.2

@astrojs/svelte@9.1.6

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed
  • Updated dependencies [59052e7]:
    • @astrojs/svelte-renderer@0.1.2

@astrojs/vercel@11.0.22

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/vue@7.1.6

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed
  • Updated dependencies [59052e7]:
    • @astrojs/vue-renderer@0.1.2

@astrojs/markdown-remark@7.3.9

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/markdown-satteri@0.4.10

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/preact-renderer@0.1.3

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/react-renderer@0.1.3

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/solid-js-renderer@0.1.2

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/svelte-renderer@0.1.2

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/vue-renderer@0.1.2

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed

@astrojs/vite-plugin-astro@0.1.3

Patch Changes

  • #18713 59052e7 Thanks @delucis! - Unpins @astrojs/* dependencies to allow versions matching the ^ range to be installed
withastro/starlight

This PR contains the following updates:

Package Type Update Change Pending
peter-evans/create-pull-request action patch v8.1.1 → v8.1.2 v8.1.3

Release Notes

peter-evans/create-pull-request

v8.1.2: Create Pull Request v8.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: peter-evans/create-pull-request@v8.1.1...v8.1.2


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

Changes

  • Switches from workspace:* to workspace:^ in package dependencies
  • This means that instead of publishing e.g. "@astrojs/internal-helpers": "0.13.2", we ship "@astrojs/internal-helpers": "^0.13.2" allowing users to update within the ^ version range if newer versions of the package are available.
  • This can matter, because sometimes we’ll update package A, but another package B that depends on A is not published. In this case, package B will never be able to use the updates from package A, and users can end up with duplicates or stuff can even break.
  • Recent example: @astrojs/markdown-satteri updated the satteri version it uses to v0.11, but @astrojs/mdx was never published. This meant @astrojs/mdx was pinned to using an older version of @astrojs/markdown-satteri, preventing MDX users from updating.

Testing

  • Existing tests should pass
  • Bit hard to test if there is a real downstream impact that could break due to a newer version of a dep now being used, but given we test with latest in the monorepo, I don’t foresee that.

Docs

n/a

withastro/starlight

Description

This PR updates Lunaria and its GitHub Action to their latest versions to handle pull_request_target being blocked by default.

The new setup uses the new documented 2 workflow approach relying on the workflow_run event to run Lunaria after the Lunaria Trigger workflow completes.

From my understanding, here are the changes we should observe (not issues, just listing them):

  • Lunaria comments on PRs from first-time contributors will only appear after we approve the workflow runs for the PR whereas before they appeared immediately.
  • The list of checks won't include Lunaria (only the trigger, so if Lunaria fails, the Actions tab will be the only place to see the failure).
  • We cannot test without merging this PR first.

Afaik, the changes to @lunariajs/core should not affect us.

withastro/astro

Changes

  • astro dev no longer blocks cross-origin requests whose allowedDomains entry specifies a default port (e.g. port: '443' with protocol: 'https' or port: '80' with protocol: 'http'). The URL parser normalises default ports to '', so the previous matchPattern-based check in BaseApp.validateForwardedHost could never match them.
  • BaseApp.validateForwardedHost now delegates to validateHost (the same helper used everywhere else since #18641), making the dev-server Sec-Fetch check and the public helper consistent with the documented allowedDomains rules. The unused matchPattern import is removed.

Testing

  • New unit test cases in packages/astro/test/units/dev/sec-fetch.test.ts cover origins matched by entries with port: '443' / port: '80', confirming they pass the Sec-Fetch check; evil origins remain blocked.

Docs

  • No docs update needed — the fix aligns the implementation with the already-documented behaviour of allowedDomains.

Closes #18710

withastro/astro

Fixes #18708

Changes

  • astro build releases the content layer once its sync is done. Before, the globalContentLayer singleton kept a reference to it, so the data store, holding every loaded entry, stayed in memory for the rest of the build, including while pages prerender.
  • The build sync calls globalContentLayer.dispose() instead of contentLayer.dispose(). It still disposes the content layer, and also clears the singleton. Dev keeps its content layer, because it passes skip.cleanup.
  • With 5,000 entries of ~20 KB, the heap at astro:build:done drops from 143 MB to 47 MB. The reproduction is in #18708.

Testing

  • Adds test/units/content-layer/sync-cleanup.test.ts: after a build sync, globalContentLayer.get() is null. With skip.cleanup: true, the content layer is kept.

Docs

  • No docs update needed: this changes memory usage only, not behavior.
withastro/starlight

Description

Adds an AWS logo to the grid on the landing page.

IIRC, I’d seen AWS usage of Starlight before, but couldn’t track it down when adding the logo grid, but I spotted https://aws.github.io/graph-explorer/ today.

withastro/starlight

Description

  • Adds Zeku to the community tools and integrations list on the Plugins and Integrations page.
  • Zeku is a desktop app for writing in a Starlight or Astro project. It opens the project's content folder, reads the collection schema for its frontmatter forms, and knows Starlight's own frontmatter, asides, components, sidebar labels, and badges. Plain files, published with your own git.
  • It's a paid app with a 14-day free trial, which the card says, so readers know before clicking.
withastro/astro

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

Releases

astro@7.4.11

Patch Changes

  • #18641 08e2cee Thanks @astro-factory! - Validates the protocol, host and port from X-Forwarded-Proto, X-Forwarded-Host and X-Forwarded-Port together against each security.allowedDomains entry, instead of one at a time:

    • A forwarded protocol is only applied when an entry allows it for the host in use.
    • A forwarded port is only applied when the entry for that host lists it.
    • A forwarded host without a forwarded protocol is validated with the protocol of the server.
    • An entry with port: '443' (or '80' for http) now matches a host that doesn't include a port.
  • #18651 93a9057 Thanks @umeraamir69! - Returns 400 Bad Request for malformed percent-encoded paths in the dev server and static preview instead of bubbling into a 500

  • #18672 e901468 Thanks @astro-factory! - Fixes astro check reporting @astrojs/check as missing when the package is installed but throws while loading. The original error is now shown instead of an install prompt.

  • #18641 08e2cee Thanks @astro-factory! - Fixes security.allowedDomains accepting non-HTTP(S) X-Forwarded-Proto values (such as ftp or ws) when the list mixes patterns with and without a protocol

  • #18686 62bb716 Thanks @astro-factory! - Fixes astro build deleting the license file generated by Vite's build.license option. Astro now removes only its own Vite manifest from the .vite/ output folder.

  • #18629 e9916e1 Thanks @decrek! - Fixes spreading an object onto an element with scoped styles changing that object. When the same object was spread on every render, for example a constant imported from another module, its class grew with every request.

  • #18641 08e2cee Thanks @astro-factory! - Tightens how security.allowedDomains validates the Host and X-Forwarded-Host headers. Only a plain hostname with an optional port is accepted, and the validated host is applied to Astro.url exactly as it was matched.

  • Updated dependencies [d13beeb, e9916e1]:

    • @astrojs/markdown-satteri@0.4.9
    • @astrojs/runtime@0.1.1
    • @astrojs/vite-plugin-astro@0.1.2

@astrojs/mdx@8.1.5

Patch Changes

  • Updated dependencies [d13beeb]:
    • @astrojs/markdown-satteri@0.4.9

@astrojs/preact@6.1.5

Patch Changes

  • Updated dependencies []:
    • @astrojs/preact-renderer@0.1.2

@astrojs/react@7.1.8

Patch Changes

  • Updated dependencies []:
    • @astrojs/react-renderer@0.1.2

@astrojs/solid-js@7.1.5

Patch Changes

  • Updated dependencies []:
    • @astrojs/solid-js-renderer@0.1.1

@astrojs/svelte@9.1.5

Patch Changes

  • Updated dependencies []:
    • @astrojs/svelte-renderer@0.1.1

@astrojs/vue@7.1.5

Patch Changes

  • Updated dependencies []:
    • @astrojs/vue-renderer@0.1.1

@astrojs/markdown-remark@7.3.8

Patch Changes

  • #18698 d13beeb Thanks @astro-factory! - Fixes MDX optimize emptying <style> and <script> elements nested in static HTML from plugins, and turning SVG attributes like marker-end into markerEnd when ignoreElementNames is set

@astrojs/markdown-satteri@0.4.9

Patch Changes

  • #18698 d13beeb Thanks @astro-factory! - Fixes MDX optimize emptying <style> and <script> elements nested in static HTML from plugins, and turning SVG attributes like marker-end into markerEnd when ignoreElementNames is set

@astrojs/preact-renderer@0.1.2

Patch Changes

  • Updated dependencies [e9916e1]:
    • @astrojs/runtime@0.1.1

@astrojs/react-renderer@0.1.2

Patch Changes

  • Updated dependencies [e9916e1]:
    • @astrojs/runtime@0.1.1

@astrojs/solid-js-renderer@0.1.1

Patch Changes

  • Updated dependencies [e9916e1]:
    • @astrojs/runtime@0.1.1

@astrojs/svelte-renderer@0.1.1

Patch Changes

  • Updated dependencies [e9916e1]:
    • @astrojs/runtime@0.1.1

@astrojs/vue-renderer@0.1.1

Patch Changes

  • Updated dependencies [e9916e1]:
    • @astrojs/runtime@0.1.1

@astrojs/runtime@0.1.1

Patch Changes

  • #18629 e9916e1 Thanks @decrek! - Fixes spreading an object onto an element with scoped styles changing that object. When the same object was spread on every render, for example a constant imported from another module, its class grew with every request.

@astrojs/vite-plugin-astro@0.1.2

Patch Changes

  • Updated dependencies [e9916e1]:
    • @astrojs/runtime@0.1.1
withastro/astro

Changes

  • Raw <style> and <script> elements whose text content was moved into a set:html property by rehypeCollapseScriptStyle are now excluded from the static optimizer, preventing their content from being written as a literal attribute (<style set:html="…"></style>). This affects both the unified and Sätteri processors.
  • In the unified optimizer (rehype-optimize-static.ts), elements that carry a set:html/set:text directive are treated as non-static, so they and their siblings fall through to the runtime path. The optimizer also now passes space: 'svg' when serializing static children that sit inside an <svg> context (stopping at <foreignObject>), fixing camelCased attribute names like markerEnd → marker-end.
  • In Sätteri (create-processor.ts), script and style are always added to optimizeStatic.ignoreElements alongside any user-supplied ignoreElementNames, matching the unified fix.

Testing

  • Added cases to packages/markdown/remark/test/mdx-rehype-optimize-static.test.ts covering raw <svg><style> with optimize: true and ignoreElementNames: ["style"], including a <div><style>…</style><p>…</p></div> case with < and & in CSS to verify content is not escaped.
  • Added cases to packages/markdown/satteri/test/mdx-renderer-options.test.ts covering the same scenarios for the Sätteri processor.

Docs

  • No docs update needed; this is a bug fix restoring already-documented behavior for optimize: true.

Closes #18652

withastro/astro

Changes

  • Adds a changeset for the @astrojs/internal-helpers/renderer export added in #18612. The framework integrations were published requiring @astrojs/internal-helpers@0.13.1, which lacks it.

Testing

  • changeset status bumps @astrojs/internal-helpers and the five integrations.

Docs

  • None.
withastro/starlight

Description

  • Removes the guidance to set nodejs_compat for Cloudflare users. Since August, Node compat has been enabled by default (see “Node.js compatibility” in the Cloudflare docs), so this guidance is only really needed for people with older projects trying to add Starlight. Given that’s likely a fairly small population and we don’t generally cover platform-specific stuff unless really necessary, I think it makes sense to clean that up. (As this is a standalone paragraph, I also went ahead and removed it from translations.)
  • While in there, I also removed the CF docs from the showcase sites since they no longer use Starlight.
withastro/starlight

Description

  • This PR updates the link cards used in our docs to link to external content such as themes, showcase sites, blog posts, plugins etc.
  • It adds a rel="nofollow ugc" attribute for this kind of content.
  • The main motivation here is to disincentivise people from creating or adding content/sites only for SEO back-linking.
withastro/astro

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

Releases

astro@7.4.10

Patch Changes

  • #18621 8a61493 Thanks @marcalexiei! - Fixes the dev toolbar's audit freezing an image's CSS animations in Safari, by reading the image's size from the request that loaded it instead of fetching it again

  • #18691 f787792 Thanks @ematipico! - Improves startup time of astro commands by loading SVGO only when svgoOptimizer() optimizes an SVG, instead of whenever astro/config is imported

  • #18678 ea63d76 Thanks @astro-factory! - Fixes duplicate CSS loading for hydrated islands that share modules or are imported through a path alias. The client build no longer emits and preloads stylesheets that are already linked on the page by the server build.

  • Updated dependencies [57137ed]:

    • @astrojs/internal-helpers@0.13.2
    • @astrojs/markdown-satteri@0.4.8
    • @astrojs/vite-plugin-astro@0.1.1

@astrojs/cloudflare@14.4.7

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
    • @astrojs/underscore-redirects@1.0.4

@astrojs/markdoc@2.1.4

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2

@astrojs/mdx@8.1.4

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
    • @astrojs/markdown-satteri@0.4.8

@astrojs/netlify@8.2.13

Patch Changes

  • #18680 4f8e19a Thanks @florian-lefebvre! - Prevents server function traces from including the entire project when a dependency uses paths the tracer cannot resolve.
  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
    • @astrojs/underscore-redirects@1.0.4

@astrojs/node@11.1.12

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2

@astrojs/preact@6.1.4

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
    • @astrojs/preact-renderer@0.1.1

@astrojs/react@7.1.7

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
    • @astrojs/react-renderer@0.1.1

@astrojs/solid-js@7.1.4

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
    • @astrojs/solid-js-renderer@0.1.0

@astrojs/svelte@9.1.4

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
    • @astrojs/svelte-renderer@0.1.0

@astrojs/vercel@11.0.21

Patch Changes

  • #18680 4f8e19a Thanks @florian-lefebvre! - Prevents server function traces from including the entire project when a dependency uses paths the tracer cannot resolve.
  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2

@astrojs/vue@7.1.4

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
    • @astrojs/vue-renderer@0.1.0

@astrojs/internal-helpers@0.13.2

Patch Changes

  • #18695 57137ed Thanks @matthewp! - Adds the @astrojs/internal-helpers/renderer export used by @astrojs/react, @astrojs/preact, @astrojs/solid-js, @astrojs/svelte and @astrojs/vue, which fail to load without it

@astrojs/markdown-remark@7.3.7

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2

@astrojs/markdown-satteri@0.4.8

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2

@astrojs/preact-renderer@0.1.1

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2

@astrojs/react-renderer@0.1.1

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2

@astrojs/vite-plugin-astro@0.1.1

Patch Changes

  • Updated dependencies [57137ed]:
    • @astrojs/internal-helpers@0.13.2
withastro/astro
withastro/astro

Changes

Closes #18655
Closes #18657
Closes #18690

Import svgo lazily

Testing

Added

Docs

withastro/astro

Changes

  • Errors thrown after a page has started streaming are now logged exactly once through the configured pipeline logger (e.g. logHandlers.json()), as a single structured record with level: "error" — the same as errors thrown before the first byte. Previously they were printed by writeResponse via console.error as multi-line plain text, bypassing any custom logger entirely; adapters that hand the body to their runtime untouched (Bun, Deno) logged nothing at all.
  • SSRResult now carries an optional logger set from FetchState in createResult(). Both streaming renderers (renderStreamToAsyncIterable and renderStreamToStream) log the error once and stamp it with Symbol.for('astro.streamErrorLogged'). writeResponse skips only stamped errors so that errors from an endpoint's own ReadableStream are still printed as before. recordServerError() in the dev server respects the same marker and skips its logger.error call for already-logged errors, preventing a duplicate record in astro dev.

Testing

  • packages/astro/test/units/render/streaming.test.ts — new unit tests covering the mid-stream error path for both AsyncIterable and ReadableStream bodies, asserting a single logger call with the correct level and no console.error output.
  • packages/astro/test/units/app/node.test.ts — updated to assert that writeResponse still prints errors from endpoint streams that were never touched by the renderer.
  • packages/astro/test/streaming-error-logger.test.ts — new dev-server integration test asserting that a mid-stream page error produces exactly one error record in astro dev.

Docs

No docs update needed — this is a bug fix that restores expected logger behaviour with no API changes.

Closes #18625

withastro/astro

Changes

  • dist/.vite/license.md (and its equivalents in server/client output dirs) is now preserved after astro build when vite.build.license is set. Previously, removeViteManifestDirectories() removed the entire .vite/ folder recursively, silently deleting the licence file Vite writes there.
  • The cleanup now deletes only .vite/manifest.json directly, then removes the .vite/ directory only if it is empty afterwards. Files Vite writes alongside the manifest (such as build.license output) are left untouched.

Testing

  • Added packages/astro/test/units/build/remove-vite-manifest-directories.test.ts, covering: manifest-only directories are removed, non-empty directories with extra files are kept after manifest deletion, and builds without a manifest leave nothing behind.

Docs

  • No docs update needed; this restores behaviour that already matches Vite's own output and requires no new user-facing config.

Closes #18685

withastro/astro

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

Releases

@astrojs/preact-renderer@0.1.0

Minor Changes

Patch Changes

@astrojs/react-renderer@0.1.0

Minor Changes

Patch Changes

@astrojs/solid-js-renderer@0.1.0

Minor Changes

Patch Changes

@astrojs/svelte-renderer@0.1.0

Minor Changes

Patch Changes

@astrojs/vue-renderer@0.1.0

Minor Changes

Patch Changes

@astrojs/runtime@0.1.0

Minor Changes

  • #18610 5083c65 Thanks @matthewp! - Initial release

  • #18611 f98e8a8 Thanks @matthewp! - Adds standalone rendering: astro() compiles .astro files in a plain Vite project, and renderToString() / renderToResponse() from @astrojs/runtime render a component tree with its stylesheets, scripts and framework islands in dev and in builds

  • #18611 f98e8a8 Thanks @matthewp! - Adds declarative renderer fields: an AstroRenderer can carry options (passed to its server entrypoint as this.options), optimizeDeps, dedupe, noExternal (a list, or a function of the project root for lists found by crawling dependencies), a dev-only devHeadScript and an appEntrypoint that its entrypoints import, which astro() applies, so a renderer is plain data next to the framework's own Vite plugin

Patch Changes

  • #18630 c904827 Thanks @astro-factory! - Fixes bundled scripts and hydrated islands being blocked when security.csp.scriptDirective.strictDynamic is enabled. Astro now adds the hash of every bundled script to script-src and renders an import map with their integrity in the <head>.

  • #18688 1999c84 Thanks @astro-factory! - Fixes errors thrown after a page has started streaming bypassing the configured logger. They are now reported once through it, as one error record, in both production and astro dev

@astrojs/vite-plugin-astro@0.1.0

Minor Changes

  • #18610 5083c65 Thanks @matthewp! - Initial release

  • #18611 f98e8a8 Thanks @matthewp! - Adds standalone rendering: astro() compiles .astro files in a plain Vite project, and renderToString() / renderToResponse() from @astrojs/runtime render a component tree with its stylesheets, scripts and framework islands in dev and in builds

  • #18611 f98e8a8 Thanks @matthewp! - Adds declarative renderer fields: an AstroRenderer can carry options (passed to its server entrypoint as this.options), optimizeDeps, dedupe, noExternal (a list, or a function of the project root for lists found by crawling dependencies), a dev-only devHeadScript and an appEntrypoint that its entrypoints import, which astro() applies, so a renderer is plain data next to the framework's own Vite plugin

Patch Changes

astro@7.4.9

Patch Changes

  • #18681 bf1828b Thanks @astro-factory! - Fixes static builds skipping or failing on pages whose getStaticPaths() params contain characters like % or \, and warns when a prerendered page is skipped because it returned an empty error response

  • #18630 c904827 Thanks @astro-factory! - Fixes bundled scripts and hydrated islands being blocked when security.csp.scriptDirective.strictDynamic is enabled. Astro now adds the hash of every bundled script to script-src and renders an import map with their integrity in the <head>.

  • #18611 f98e8a8 Thanks @matthewp! - Fixes bundling of a <script src> that uses a root-relative path to a project file outside src/, such as /lib/analytics.ts. The error asking for is:inline is now shown only when the path points to a file in public/.

  • #18688 1999c84 Thanks @astro-factory! - Fixes errors thrown after a page has started streaming bypassing the configured logger. They are now reported once through it, as one error record, in both production and astro dev

  • Updated dependencies [c904827, 5083c65, 1999c84, 5083c65, f98e8a8, f98e8a8]:

    • @astrojs/runtime@0.1.0
    • @astrojs/vite-plugin-astro@0.1.0

@astrojs/preact@6.1.3

Patch Changes

  • Updated dependencies [ff1cf65]:
    • @astrojs/preact-renderer@0.1.0

@astrojs/react@7.1.6

Patch Changes

  • Updated dependencies [ff1cf65]:
    • @astrojs/react-renderer@0.1.0

@astrojs/solid-js@7.1.3

Patch Changes

  • Updated dependencies [ff1cf65]:
    • @astrojs/solid-js-renderer@0.1.0

@astrojs/svelte@9.1.3

Patch Changes

  • Updated dependencies [ff1cf65]:
    • @astrojs/svelte-renderer@0.1.0

@astrojs/vue@7.1.3

Patch Changes

  • Updated dependencies [ff1cf65]:
    • @astrojs/vue-renderer@0.1.0

astro-vscode@2.17.4

Patch Changes

  • #18692 ad77e9e Thanks @Princesseuh! - Republishes the extension to the VS Code Marketplace and Open VSX, which were missed in the previous release
withastro/astro

Changes

  • Fixes the broken pnpm-lock.yaml on main (ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY: no entry for 'rolldown@1.3.0'), which fails pnpm install in every CI job.
  • #18679 pinned rolldown to ~1.2.16 and removed the 1.3.0 entries from the lockfile, while #18610 resolved @astrojs/vite-plugin-astro's rolldown to 1.3.0. The two lockfile changes merged cleanly as text but left a reference to a removed entry.
  • Pins rolldown in @astrojs/vite-plugin-astro to ~1.2.16, like the rest of the repo, and regenerates the lockfile.

Testing

  • pnpm install --frozen-lockfile passes.

Docs

  • No docs update needed.
withastro/astro

This PR contains the following updates:

Package Change Age Confidence
@hono/node-server 2.0.4 → 2.1.6 age confidence

@​hono/node-server: serveStatic decodes the request path a second time, leading to bypass of middleware on static paths

CVE-2026-118663 / GHSA-rmxm-3fg6-px4f

More information

Details

Summary

serveStatic decodes the request path a second time after Hono has already decoded it for routing. A crafted request can be routed as one path and served as another, so middleware mounted on a static prefix does not run for a file under that prefix.

Details

Hono decodes the request path once before routing. serveStatic decoded it again before resolving the file. With a malformed percent-encoded sequence, the first decode leaves part of the path encoded, the router matches the encoded form, and the second decode resolves the real directory. The file is still resolved inside the configured root; this is not a traversal outside it.

Impact

An unauthenticated attacker may reach static files without the middleware on their prefix running, for example an authentication check. This affects applications that mount middleware on part of the directory served by serveStatic. Applications that serve only public files are not affected.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


@​hono/node-server: Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy

CVE-2026-126210 / GHSA-jpvv-r467-5p4w

More information

Details

Summary

@hono/node-server passes the raw request-target to the WHATWG URL parser, which treats a backslash in the path as / and then resolves .. segments. A request for /admin\secret or /public\..\admin/secret reaches the application as /admin/secret. A reverse proxy that follows RFC 3986 forwards the backslash unchanged and applies its path-based rules to the original path, so the request reaches a route the proxy is meant to block.

Details

A raw backslash is not allowed in a request-target (RFC 3986, RFC 9112 Section 3.2.1), and RFC 9112 Section 3.2 says a recipient should reject such a request rather than correct it. Proxies such as nginx on Linux, HAProxy and Envoy keep the backslash as an ordinary character, so they and the application see different paths.

The fix responds with 400 Bad Request to a request whose path contains a raw backslash, for HTTP/1.1, HTTP/2, absolute-form request-targets and WebSocket upgrades. A percent-encoded backslash and a backslash in the query string are still accepted.

Impact

An unauthenticated client can reach a route that a reverse proxy, load balancer or WAF in front of the application blocks by path.

This affects applications served by @hono/node-server behind a front component that makes path-based decisions and forwards a backslash unchanged. Access control inside the Hono application, such as middleware on /admin/*, runs on the rewritten path and is not affected.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

honojs/node-server (@​hono/node-server)

v2.1.6

Compare Source

Security fixes

This release includes fixes for the following security issues:

Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy

Affects: all requests. The raw request-target was passed to the WHATWG URL parser, which treats a backslash in the path as / and resolves .. segments, so /admin\secret reached the application as /admin/secret. A reverse proxy that forwards the backslash unchanged applied its path-based rules to the original path. GHSA-jpvv-r467-5p4w

A request whose path contains a raw backslash is now rejected with 400 Bad Request, for HTTP/1.1, HTTP/2 and WebSocket upgrades. A percent-encoded backslash (%5C) and a backslash in the query string are still accepted.

WebSocket upgrade request-target starting with // replaces the host in c.req.url, bypassing Origin checks

Affects: upgradeWebSocket. The URL of an upgrade request was built by resolving the request-target against the Host header, so a request-target such as //attacker.example/ws set the host of c.req.url to a client-chosen value while routing still saw /ws. An application that compared Origin with the origin of c.req.url could be bypassed by a page on another site. GHSA-7v5p-43qr-wch5

The host of upgrade requests now comes from the Host header, as for ordinary requests.

Unhandled ECONNRESET on the socket during an asynchronous WebSocket upgrade crashes the process

Affects: upgradeWebSocket. While the application handled an upgrade request, the socket had no error listener. A client that reset the connection during asynchronous middleware caused an unhandled 'error' event and terminated the process. GHSA-qv5m-9pm6-hqp3

Error and close events on the socket are now handled while the application runs, and a pending upgrade is released when the socket closes.


The backslash fix also ships in @hono/node-server v1.19.18. Users of upgradeWebSocket are encouraged to upgrade to this version.

v2.1.5

Compare Source

What's Changed
New Contributors

Full Changelog: honojs/node-server@v2.1.4...v2.1.5

v2.1.4

Compare Source

What's Changed

Full Changelog: honojs/node-server@v2.1.3...v2.1.4

v2.1.3

Compare Source

Security fixes

serveStatic decodes the request path a second time, leading to bypass of middleware on static paths

Affects: @hono/node-server/serve-static. Fixes serveStatic decoding an already-decoded path, where a crafted request could be routed as one path and served as another, skipping middleware mounted on a static prefix. GHSA-rmxm-3fg6-px4f

serveStatic now rejects request paths that still contain % after decoding. To serve files whose names contain a literal %, set allowPercentInPath: true.

The same fix ships in hono v4.13.11.

v2.1.2

Compare Source

What's Changed

Full Changelog: honojs/node-server@v2.1.1...v2.1.2

v2.1.1

Compare Source

What's Changed

Full Changelog: honojs/node-server@v2.1.0...v2.1.1

v2.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v2.0.12...v2.1.0

v2.0.12

Compare Source

What's Changed

Full Changelog: honojs/node-server@v2.0.11...v2.0.12

v2.0.11

Compare Source

What's Changed

Full Changelog: honojs/node-server@v2.0.10...v2.0.11

v2.0.10

Compare Source

Security fixes

This release includes a fix for the following security issue:

Unauthenticated memory-leak DoS via aborted WebSocket handshake

Affects: upgradeWebSocket. A WebSocket upgrade request with a missing or malformed Sec-WebSocket-Key header leaked the request's IncomingMessage and left a promise pending, even though no connection was established. Since the route is reachable pre-handshake without authentication, an attacker could flood it to gradually exhaust memory. GHSA-9mqv-5hh9-4cgg


Users of upgradeWebSocket are encouraged to upgrade to this version.

v2.0.9

Compare Source

What's Changed

  • fix(websocket): polyfill missing ErrorEvent global by @​otnc in #​371
  • fix(serve-static): correct Range header parsing edge cases by @​otnc in #​372
  • fix: recover complete request bodies after client disconnect by @​usualoma in #​375

New Contributors

Full Changelog: honojs/node-server@v2.0.8...v2.0.9

v2.0.8

Compare Source

What's Changed

Full Changelog: honojs/node-server@v2.0.7...v2.0.8

v2.0.6

Compare Source

What's Changed

Full Changelog: honojs/node-server@v2.0.5...v2.0.6

v2.0.5

Compare Source

Security Fix

Fixed a security issue in Serve Static Middleware where prefix-mounted middleware could be bypassed on Windows. This only affects applications running on Windows that use Serve Static Middleware. Affected users are encouraged to upgrade to this version.

See GHSA-frvp-7c67-39w9 for details.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

Changes

  • getStaticPaths() routes whose params contain a literal % (e.g. 50%-off) or other URI-special characters are now correctly written to dist/ during a static build. Previously, getUrlForPath passed the raw decoded pathname to new URL() without encoding it first. Since 6.0 the render pipeline decodes request.url to recover the pathname, so a bare % caused decodeURI to throw, returning an empty 400 that silently dropped the file.
  • getUrlForPath (packages/astro/src/core/build/common.ts) now calls encodeURI(pathname) before constructing the request URL. This keeps the parallel prerenderer's static-path map keys and the request URLs produced by generate.ts in sync. renderPath now emits a warning that includes the HTTP status and pathname when an error response with no body is skipped, making similar regressions immediately visible.

Testing

  • New unit tests in packages/astro/test/units/build/common.test.ts cover getUrlForPath for paths containing %, \, and pre-escaped sequences (e.g. %23), asserting that round-tripping the resulting URL's pathname through validateAndDecodePathname returns the original path.
  • New build-level test packages/astro/test/static-paths-special-chars.test.ts exercises a getStaticPaths fixture with params 50%-off, café, tag#1, and a\b, asserting each is written to the expected dist/ path with the correct Astro.params value.

Docs

No docs update needed — this restores previously working behavior with no API or config changes.

Closes #18659

withastro/starlight

Description

  • What does this PR change? A few external links in the translated docs go to pages that don't exist:
    • https://astro.build/it/ (it/getting-started) and https://astro.build/ru/ (ru/guides/authoring-content, twice). astro.build has no localized home pages, so these now go to https://astro.build/ like the English pages.
    • https://docs.astro.build/pt-pt/concepts/islands/ and https://docs.astro.build/pt/reference/cli-reference/#astro-dev in the pt-pt pages. The Astro docs only have pt-br, which the other pt-pt pages already link to.
    • https://git-scm.com/docs/git-clone/de in de/reference/configuration. git-scm.com has no German translation of git-clone, so it now links to the English page with its current --depth anchor.
  • I checked each old URL (404) and new URL (200) with curl, and the astro-dev anchor exists on the pt-br page.
  • Nothing visual.
withastro/astro

Changes

Followup to another NFT fix I contributed last week

  • Ignore project-wide NFT globs even when the project root matches the trace base, preventing Vercel and Netlify functions from including entire repositories.
  • Keep package-scoped globs traceable and preserve the workspace trace base.
  • Made with AI

Testing

  • Add a Vercel unit test for filtering project-wide globs while retaining package-scoped globs.
  • The Vercel and Netlify monorepo trace tests cover server chunks, runtime process.cwd() assets, and unrelated workspace files.

Docs

Changeset

withastro/astro

Changes

  • Removes direct @emnapi/runtime pins from the language-tools packages so they can rely on @astrojs/astro2tsx to install the WASM runtime.
  • compiler-rs#219 moves @emnapi/runtime into @astrojs/astro2tsx runtime dependencies
  • Pins rolldown to a compatible version

Testing

N/A

Docs

Removes an unreleased changeset

AI was used to prepare this PR description.

withastro/astro

Changes

  • Hydrated island components imported through a tsconfig path alias are now resolved to their absolute module id (via this.resolve()) before being stored in pagesByHydratedComponent, matching how client:only components are handled. Previously the raw alias specifier was used, so shouldDeleteCSSChunk never matched it and the client CSS was never removed.
  • The CSS build plugin now also drops client CSS for chunks that island entry chunks import statically (non-dynamic imports only), when all of that chunk's CSS modules are already in the SSR build and no client:only component, <script>, or renderer has an exclusive path to the chunk. This covers the shared-module case (e.g. two islands sharing Card.tsx → Card.css) where Rollup/Rolldown splits the shared code into its own chunk whose CSS was always kept and injected by Vite's preload helper at runtime.

Testing

  • Extends the css-deduplication fixture and its test suite (packages/astro/test/css-deduplication.test.ts) with cases for alias-imported islands and islands that share a CSS-importing module, asserting that the client copies of the duplicate CSS files are absent from the build output and from __vite__mapDeps.

Docs

  • No docs update needed; this is an internal build-pipeline deduplication fix with no user-facing API changes.

Closes #18677

withastro/astro

This PR contains the following updates:

Package Type Update Change
mcr.microsoft.com/devcontainers/javascript-node final major 4-22 → 5-22

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

This PR contains the following updates:

Package Change Age Confidence
autocannon ^8.0.0 → ^9.0.0 age confidence

Release Notes

mcollina/autocannon (autocannon)

v9.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

This PR contains the following updates:

Package Type Update Change
withastro/automation (changelog) workflow digest 497c926 → 4105de6

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

This PR contains the following updates:

Package Type Update Change
semgrep/semgrep container digest 40579a2 → fb59331

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

Changes

  • When astro check loads @astrojs/check, a bare catch {} previously swallowed both require.resolve() failures (package not installed) and import() failures (package installed but broken). Both cases produced the same "dependency is missing" prompt, hiding the real crash. Now only the require.resolve() call is wrapped in the catch; import() runs outside it, so load-time errors like TypeError: this.bridge.setLastError is not a function propagate to the CLI's normal error handler with a full stack trace.
  • This surfaces the true failure when a transitive dependency version mismatch (e.g. @emnapi/core@1.11.3 paired with @emnapi/runtime@2.0.0-beta.2) causes the checker to crash on import, making the problem diagnosable without workarounds.

Testing

  • Updated packages/astro/test/units/cli/install-package.test.ts to cover the case where require.resolve() succeeds (package is present) but import() throws, verifying the error is now rethrown rather than treated as a missing package.

Docs

  • No docs update needed; this is a CLI error-reporting fix with no user-facing API change.

Closes #18653

withastro/astro

Changes

macos-14 has been retired since November 2nd, 2026: https://github.blog/changelog/2026-10-01-github-actions-macos-14-runner-image-retirement/

Our current CI is red because of the error The configuration 'macos-14-arm64-us-default' is not supported:

image

This PR updates the macOS runner to macos-15.

Testing

CI should be green.

Docs

N/A

withastro/astro

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@babel/core (source) ^8.0.10 → ^8.1.0 age confidence devDependencies minor
@cloudflare/vite-plugin (source) ^1.66.0 → ^1.67.0 age confidence dependencies patch
@cloudflare/vitest-plugin (source) 1.4.11 → 1.6.0 age confidence devDependencies minor
@cloudflare/workers-types ^5.20261101.1 → ^5.20261106.1 age confidence devDependencies minor 5.20261109.1 (+2)
@earendil-works/pi-ai (source) ^0.87.1 → ^0.99.2 age confidence devDependencies minor
@fastify/static ^10.1.8 → ^10.1.10 age confidence devDependencies patch
@flue/runtime (source) ^2.2.2 → ^2.3.0 age confidence devDependencies minor
@netlify/functions (source) ^6.0.3 → ^6.1.0 age confidence dependencies minor 6.1.1
@playwright/test (source) 1.64.1 → 1.65.0 age confidence devDependencies minor
@qwik.dev/partytown ^1.0.3 → ^1.0.4 age confidence dependencies patch 1.0.5
@shikijs/rehype (source) ^4.5.0 → ^4.6.0 age confidence devDependencies minor
@shikijs/twoslash (source) ^4.5.0 → ^4.6.0 age confidence devDependencies minor
@tailwindcss/vite (source) ^4.3.3 → ^4.3.4 age confidence dependencies patch 4.3.5
@vercel/functions (source) ^3.9.11 → ^3.11.0 age confidence dependencies minor
@vercel/nft ^1.11.0 → ^1.11.1 age confidence dependencies patch
@vercel/routing-utils (source) ^6.6.0 → ^6.6.1 age confidence dependencies patch
@vitejs/plugin-react (source) ^6.1.2 → ^6.2.1 age confidence dependencies minor 6.3.0
@vitest/snapshot (source) 5.0.5 → 5.1.0 age confidence devDependencies minor
@vue/compiler-sfc (source) ^3.5.44 → ^3.5.45 age confidence dependencies patch
CodSpeedHQ/action v5.6.1 → v5.6.3 age confidence action patch
cookie ^2.0.1 → ^2.0.2 age confidence dependencies patch
fast-xml-parser ^5.11.2 → ^5.12.0 age confidence dependencies minor
fastify (source) ^5.12.7 → ^5.12.8 age confidence devDependencies patch
fs-fixture ^2.16.0 → ^2.16.2 age confidence devDependencies patch
markdown-table ^3.0.4 → ^3.1.0 age confidence dependencies minor
mdast-util-mdx-jsx ^3.2.0 → ^3.2.1 age confidence devDependencies patch
muggle-string ^1.0.0 → ^1.0.3 age confidence dependencies patch 1.0.4
oxc-transform-react (source) ^0.156.0 → ^0.157.0 age confidence dependencies minor
oxc-transform-react (source) ^0.156.0 → ^0.157.0 age confidence devDependencies minor
pnpm (source) 11.28.10 → 11.28.11 age confidence packageManager patch
pnpm/action-setup v6.1.0 → v6.1.1 age confidence action patch
rehype-pretty-code (source) ^0.14.5 → ^0.14.6 age confidence devDependencies patch
rolldown (source) ^1.2.16 → ^1.3.0 age confidence dependencies minor
rolldown (source) ^1.2.16 → ^1.3.0 age confidence devDependencies minor
sass ^1.107.1 → ^1.108.0 age confidence devDependencies minor 1.108.1
sass ^1.107.1 → ^1.108.0 age confidence dependencies minor 1.108.1
shiki (source) ^4.5.0 → ^4.6.0 age confidence devDependencies minor
shiki (source) ^4.5.0 → ^4.6.0 age confidence dependencies minor
svelte2tsx (source) ^0.7.62 → ^0.7.63 age confidence dependencies patch
tailwindcss (source) ^4.3.3 → ^4.3.4 age confidence dependencies patch 4.3.5
undici (source) 8.12.2 → 8.12.4 age confidence devDependencies patch
vite (source) ^8.3.5 → ^8.3.6 age confidence dependencies patch
vite (source) ^8.3.5 → ^8.3.6 age confidence devDependencies patch
vitest (source) 5.0.5 → 5.1.0 age confidence devDependencies minor
vitest (source) ^5.0.5 → ^5.1.0 age confidence dependencies minor
vitest (source) ^5.0.5 → ^5.1.0 age confidence devDependencies minor
vue (source) ^3.5.44 → ^3.5.45 age confidence dependencies patch
vue (source) ^3.5.44 → ^3.5.45 age confidence devDependencies patch
wrangler (source) ^4.156.0 → ^4.158.0 age confidence devDependencies minor
wrangler (source) ^4.156.0 → ^4.158.0 age confidence dependencies minor
zizmorcore/zizmor-action v0.8.0 → v0.8.1 age confidence action patch

Release Notes

babel/babel (@​babel/core)

v8.1.0

Compare Source

🚀 New Feature
  • babel-helper-module-transforms, babel-helper-transform-fixture-test-runner, babel-helpers, babel-plugin-proposal-bytes-modules, babel-plugin-proposal-filtered-namespaces, babel-plugin-proposal-import-wasm-source, babel-plugin-proposal-text-modules, babel-plugin-transform-dynamic-import, babel-plugin-transform-json-modules, babel-runtime-corejs3, babel-runtime, babel-standalone
  • babel-generator, babel-helper-import-to-platform-api, babel-helper-module-transforms, babel-parser, babel-plugin-transform-export-namespace-from, babel-plugin-transform-json-modules, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd, babel-traverse, babel-types
  • Other
  • babel-helper-import-to-platform-api, babel-helper-transform-fixture-test-runner, babel-helpers, babel-plugin-proposal-bytes-modules, babel-plugin-proposal-import-wasm-source, babel-plugin-proposal-text-modules, babel-plugin-transform-json-modules, babel-runtime-corejs3, babel-runtime
  • babel-generator, babel-parser, babel-traverse, babel-types
  • babel-generator, babel-parser, babel-types
  • babel-generator, babel-helper-module-transforms, babel-parser, babel-plugin-transform-export-namespace-from, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd, babel-types
  • babel-cli, babel-core, babel-generator, babel-helper-transform-fixture-test-runner
  • babel-core
  • babel-core, babel-plugin-transform-classes
🐛 Bug Fix
  • babel-parser
  • babel-helper-skip-transparent-expression-wrappers, babel-plugin-transform-optional-chaining
🔬 Output optimization
cloudflare/workers-sdk (@​cloudflare/vitest-plugin)

v1.6.0

Compare Source

Minor Changes
  • #​16186 f1d81a2 Thanks @​leostera! - Support local Artifacts across Wrangler, Vite, and Workers Vitest

    Set remote: false on an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omitted remote continues to use the deployed resource, with a warning that changes affect real repositories; remote: true explicitly selects it. When remote bindings are disabled (wrangler dev --local, or Vite's remoteBindings: false), Artifacts bindings use the local simulator. Workers Vitest uses the local simulator when remote is omitted, so tests do not change real repositories by accident; set remote: true to test against the deployed resource. Local development does not require Cloudflare credentials, but does require Git 2.32 or newer on the host.

    In Miniflare's own options, Artifacts bindings route like every other binding: only dev.remote: true with a remote proxy connection uses the deployed resource. Wrangler and Vite resolve the deployed-by-default rule, and Workers Vitest its local default, before passing options to Miniflare.

Patch Changes
  • #​16700 dc35efb Thanks @​cjol! - Bump bundled brace-expansion to pick up security fixes

    These packages bundle brace-expansion (a dependency of minimatch), and the bundled versions were affected by published advisories. The bundles now include brace-expansion 2.1.7 (from 2.0.1) and 5.0.12 (from 5.0.5). Normal glob patterns expand as before; only the pathological patterns targeted by the advisories are handled differently.

  • #​16700 dc35efb Thanks @​cjol! - Bump bundled devalue from 5.6.3 to 5.9.3 to pick up security fixes

    devalue is bundled into these packages, which use it to serialise values between Node.js and workerd. Version 5.6.3 is affected by several published advisories, and 5.9.3 includes their fixes. Serialisation behaviour does not change.

  • #​16700 dc35efb Thanks @​cjol! - Bump bundled minimatch from 5.1.6 to 5.1.9 to pick up security fixes

    These packages bundle minimatch, and 5.1.6 is affected by published ReDoS advisories. Version 5.1.9 includes the fixes. 5.1.8 is skipped because it broke recursive ** matching, which D1's migrations_pattern relies on.

  • #​16695 b2061f4 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-04

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • Updated dependencies [dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, b8387a5, fa3edb3, 4cde694, b2061f4, b2061f4, f1d81a2, 4bb491b, 36e64f2, 92c4b97]:

v1.5.1

Compare Source

Patch Changes
  • #​16670 b14b9dc Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-03

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16609 da26b7f Thanks @​gpanders! - Fix tests failing to start with resolve.preserveSymlinks in isolated node_modules layouts

    With resolve.preserveSymlinks: true in a pnpm project, tests failed to start with No such module ".../node_modules/vitest/dist/chai", because a package's own dependencies are linked only next to its real path. Packages linked from a store inside node_modules now load from their real paths, and other files keep their symlinked paths.

  • Updated dependencies [b14b9dc, 44d1ee4, b14b9dc, d2eda1c, 2750917, 34f34b3]:

v1.5.0

Compare Source

Minor Changes
  • #​16424 1598fd3 Thanks @​edmundhung! - Promote experimental.newConfig to a stable config option

    The experimental experimental.newConfig option is now the stable config option. Pass config: true to cloudflareTest() to load your Worker's bindings, entrypoint and compatibility settings from cloudflare.config.ts in the project root, or pass the path of a cloudflare.config.ts elsewhere:

    cloudflareTest({ config: true });
    cloudflareTest({ config: "./worker/cloudflare.config.ts" });

    config can't be combined with wrangler. miniflare options are merged over the Worker from cloudflare.config.ts, with miniflare values taking precedence. Config functions receive Vitest's mode as ctx.mode, which defaults to test and can be changed with --mode.

    If you're moving from experimental.newConfig, secrets are now read from Vite's envDir instead of the directory containing cloudflare.config.ts, and remote bindings authenticate with cf instead of Wrangler.

Patch Changes
  • #​16642 d38cb02 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-02

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16623 51bbf8b Thanks @​petebacondarwin! - Deprecate shared tooling helper exports from Miniflare

    Miniflare continues to export getNodeCompat, NodeJSCompatMode, and getFreshSourceMapSupport for compatibility. These exports are deprecated and now use the implementations in @cloudflare/workers-utils. Add a dependency on that package and replace the Miniflare imports with:

    import {
      getNodeCompat,
      type NodeJSCompatMode,
    } from "@cloudflare/workers-utils/node-compat";
    import { getFreshSourceMapSupport } from "@cloudflare/workers-utils/sourcemap";

    Wrangler and the Cloudflare Vite and Vitest plugins now use the shared helpers directly. The helpers retain their behavior and can be imported without loading the Workers runtime.

    The deprecated Miniflare exports will be removed in a later release, allowing downstream tools such as cf to migrate and release independently first.

  • Updated dependencies [d38cb02, d38cb02, 51bbf8b, e5b1798]:

v1.4.12

Compare Source

Patch Changes
cloudflare/workerd (@​cloudflare/workers-types)

v5.20261106.1

Compare Source

earendil-works/pi (@​earendil-works/pi-ai)

v0.99.2

Compare Source

Added
  • Added the lightweight @earendil-works/pi-ai/models entry point for model collections and provider construction without loading TypeBox, built-in catalogs, or provider SDKs.
  • Added Anthropic workload identity federation from the Anthropic SDK environment variables ANTHROPIC_FEDERATION_RULE_ID, ANTHROPIC_ORGANIZATION_ID, and ANTHROPIC_IDENTITY_TOKEN_FILE (plus optional ANTHROPIC_SERVICE_ACCOUNT_ID and ANTHROPIC_WORKSPACE_ID). API keys and ANTHROPIC_AUTH_TOKEN take precedence (#​10177, #​10242 by @​philfreo)
Fixed
  • Fixed context overflow detection for Z.AI CN endpoint Prompt exceeds max length errors (#​10208)
  • Fixed Anthropic requests failing when a strict: "prefer" tool schema uses keywords Anthropic strict tool use rejects, such as minimum/maximum; such tools are now sent non-strict (#​9953)
  • Fixed provider retries firing immediately when a Retry-After header contains an unparseable date; they now use exponential backoff (#​9571)

v0.99.1

Compare Source

Added
  • Added GPT-6.1 Sol (gpt-6.1-sol) to the OpenAI, Azure OpenAI Responses, and OpenAI Codex providers.

v0.99.0

Compare Source

Breaking Changes
  • Unified image models into the regular Provider/Models surface. The separate ImagesModels collection is removed: createImagesModels(), createImagesProvider(), ImagesProvider, openrouterImagesProvider(), builtinImagesProviders(), and builtinImagesModels() are gone. Use builtinModels(), models.getModelOfType("image", ...), models.generateImages(), and createProvider({ models, images }) instead. Existing unqualified reads remain chat-only.
  • Image models are now ImageModel with a required type: "image" and share BaseModel with chat models. The old plural image type names (ImagesModel, ImagesApi, KnownImagesApi, KnownImagesProvider, and ImagesProviderId) are removed. generateImages() accepts only image models. Output modalities (output) remain on image models only.
  • Generated model data schema is now version 6: every entry carries type, operation-specific catalogs include chat, image, and classifier models, and one upstream ID may have separate entries per type. OpenRouter image models live in the openrouter-images api group of openrouter.json; image-models.generated.ts and scripts/generate-image-models.ts are removed. Run npm run hydrate:model-data.
Added
  • Added Models.generateImages() with provider-resolved auth, Provider.generateImages?, and createProvider({ images }) keyed by model.api. createProvider() models and fetchModels accept models of every type, and api is optional when images or classifiers is given.
  • Added an optional model type ("chat", "image", or "classifier"). Chat models may omit it, so existing chat models, providers, and stores keep working unchanged. Narrow mixed lists with the new isModelType() guard or read the effective type with getModelType().
  • Added getModelsOfType(), getModelOfType(), getAvailableOfType(), getAllModels(), and getAllAvailable() on Models; optional Provider.getAllModels() and Provider.filterAllModels(); corresponding generated-catalog accessors; and the AnyModel and ModelTypeMap types. hasApi(), calculateCost(), and modelsAreEqual() accept AnyModel.
  • Added support for models of every type in ModelsStoreEntry.models. Stored and fetched models of unknown types are dropped instead of failing a refresh.
  • Added classifier models and Models.classify() with a provider-neutral JEV-style choice/score/bool contract. The built-in TypeSafe provider exposes models.dev's jev-latest through the System One API and translates public bool questions to TypeSafe's noul wire format.
  • Added Jev classifier models on OpenRouter (typesafe/jev-1.13, ~typesafe/jev-latest) through its TypeSafe-compatible System One endpoint, and on Cloudflare Workers AI (typesafe/jev) through the new cloudflare-workers-ai-system-one classifier API.
  • Added Jev classifier models on Vercel AI Gateway (typesafe-ai/jev, generated from its evaluation model catalog) and OpenCode Zen (jev-1.13, jev-1.13-free) through their TypeSafe-compatible System One endpoints.
  • Added usage to ClassifierResult: System One classifications report token counts, priced from the model catalog like chat usage.
  • Added a runtime chat-model check to the Models stream entry points so non-chat models fail with a clear ModelsError instead of a missing-api stream error.
  • Added array-based models.all.json and providers/{id}.all.json variants to the generated and published JSON catalog, allowing the same upstream ID once per model type; the existing keyed models.json and providers/{id}.json stay chat-only for released clients.
  • Added onProviderStreamEvent to observe parsed provider stream events before normalization, including provider-specific fields not retained in assistant messages (#​9784, #​9901 by @​davidbrai).
  • Added Claude Sonnet 5.5 to the built-in Anthropic model catalog with adaptive thinking, mid-conversation effort, 1M context, and official pricing metadata.
  • Added Sign in with ChatGPT to the openai provider: an OAuth login that uses a ChatGPT subscription with the OpenAI API. Models.login() accepts LoginOptions with getDeviceId(), which supplies a stable installation ID to login flows that need one. Subscription usage-limit errors are not retried and link to the ChatGPT usage page; temporary usage errors are retried.
  • Added the llama-cpp-classify classifier API, which answers classifier questions from llama-server's next-token probabilities for single-token answer labels.
  • Added optional AssistantMessage.thinkingLevel, which records the thinking level the agent loop requested for a response.
Changed
  • Renamed the OpenAI Codex provider to "OpenAI Codex (legacy)"; Sign in with ChatGPT on the openai provider supersedes it.
  • Unified the Anthropic, OpenAI Codex, OpenRout

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

withastro/astro

Changes

  • Fixes NoImageMetadata for SVGs whose root <svg> tag ends after the first 1000 bytes, such as draw.io exports that store the diagram in the content attribute. Same root cause as image-size/image-size#410 (now on Codeberg: https://codeberg.org/image-size/image-size/issues/410), which #13006 was closed in favor of.
  • When the first 1000 bytes contain the start of an <svg tag but not its end, the vendored SVG check scans the rest of the input once for a > outside quoted attribute values. Other files keep the fast path, and the scan takes linear time.

Testing

  • Adds test/units/assets/image-size-svg.test.ts, covering an SVG whose root tag ends after the first kilobyte, a > inside a quoted attribute value after the first kilobyte, a long input whose root tag is never closed, and input that has an <svg> tag only after the first kilobyte (still rejected).

Docs

  • No docs update needed, because this is a bug fix with no API or configuration change.
withastro/astro

Changes

  • Removes the server-destroy dependency
  • no behavior change.
  • A small, safe cleanup

Testing

  • Added a unit test using AI

Docs

N/A, internal refactor.

withastro/astro

All three examples develop against astro ^7.4.7 but declare peer ranges that stop at 6:

examples/integration/package.json    peer ^4.0.0               dev ^7.4.7
examples/component/package.json      peer ^5.0.0 || ^6.0.0     dev ^7.4.7
examples/toolbar-app/package.json    peer ^4.6.1               dev ^7.4.7

create-astro scaffolds these straight into a user's project, so the mismatch is not internal. Reproduced with the published create-astro@5.3.1 against the live examples/* branches — scaffold, npm pack, install into a project with astro ^7.4.7:

npm error ERESOLVE could not resolve
npm error peer astro@"^4.0.0" from integration-app@0.0.1

npm exits 1 for all three (integration, component, toolbar-app).

Why it keeps happening

The v7 bump (#16488) raised devDependencies.astro in these three files and left every peer block untouched. The v6 bump (#14383) had widened component's peer the same way. So the peer range has been lagging the dev dependency by exactly one major, twice.

Change

Three lines: each peer range gains the missing majors up to 7.

integration   ^4.0.0             -> ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0
component     ^5.0.0 || ^6.0.0   -> ^5.0.0 || ^6.0.0 || ^7.0.0
toolbar-app   ^4.6.1             -> ^4.6.1 || ^5.0.0 || ^6.0.0 || ^7.0.0

I kept the older majors rather than replacing them, so existing consumers stay in range — a package released from these examples should probably drop the ones it no longer supports, but that is your call, not this fix's.

If the next major bump adds a step that updates the peer block alongside the dev dependency, this stops recurring. Happy to be told to do that differently.

withastro/astro

Changes

This PR mirrors the upstream change at vitejs/vite-plugin-react#1540

Now the range of the peer dependency oxc-transform-react allows multiple different minor versions like 0.150.0, 0.151.0, 0.152.0, etc.

Testing

CI should just be green.

Docs

A changeset file has been added to trigger a release.

withastro/astro

Changes

  • With Schibsted Grotesk from Fontsource configured as weights: ['400 700'], <Font cssVariable="--font-schibsted-grotesk" preload={[{ weight: '400 700', subset: 'latin' }]} /> rendered no preload links. Fontsource resolves the variable file to "400 900", and checkWeight only matched a requested range by exact string.
  • A requested weight or range now matches a file whose range contains it. A range that sticks out of the file's range ("300 700" against "400 900") still doesn't match. I went with containment because the existing returns variable weight test expects a "100 900" request to skip a "500 900" file. If you'd rather have overlap I can switch it, but that test would change.

I hit this on my own site and worked around it by filtering on subset only.

Testing

New unit test returns variable weight when the preloaded weight range is inside it: range inside a range, exact range, single weight inside, tab-separated range, decimal weights, ranges partly or fully outside. It fails on main with actual: [], expected: ['foo']. With the fix, node --test --experimental-strip-types test/units/assets/fonts/*.test.ts in packages/astro after pnpm run build:ci gives 118 tests, 118 pass.

Docs

No docs change. The preload docs say "Variable weight font files will be preloaded if any weight within its range is requested" and show a single weight. This makes a requested range behave the same way when it fits inside the file.

withastro/starlight

Description

This PR updates some of our lightweight CI jobs to use ubuntu-slim.

I added a comment for each change, and I also considered:

  • .github/workflows/welcome-bot.yml: uses zephyrproject-rtos/action-first-interaction which uses Docker so it's a no go.
  • .github/workflows/file-icons.yml: takes around 40s to run and would probably be compatible but it runs once a week, so the impact is minimal. It also installs some font-related dependencies relying on node-gyp that I'm not entirely sure would work with ubuntu-slim so I decided to leave it as is for now.

All other jobs either run some kind of build or CPU-heavy tasks and were left out of this change.

withastro/astro

Closes #18656

Changes

Projects without fonts configured were still loading unifont (and with it css-tree + mdn-data) and @capsizecss/unpackon every command. The fonts plugin also ran its fullbuildStartpipeline (xxhash wasm init, storage,UnifontFontResolver.create`) with zero families in need of it.

With this change:

  • fontsPlugin.buildStart returns early when settings.config.fonts is empty, matching the existing guard in buildEnd. Every other hook already handles the unset state (?? [], if (!fontFileById) return), so the virtual modules come out the same.
  • CapsizeFontMetricsResolver and UnifontFontResolver are imported on demand inside buildStart.
  • fontProviders.*() uses the literal provider name instead of providers.x()._name, and loads unifont in init(). The names already match unifont's and are pinned by test/units/assets/fonts/providers.test.ts ("references the right names").
  • Changeset included.

SVGO also pulls in css-tree through astro/config (#18655 / #18657), so the module count only drops fully once both land. Measured on a 400-post Markdown blog, no fonts, no SVGs, macOS arm64 and Node v26. Runs were interleaved against main (39ede5f):

main SVGO PR only SVGO PR + this PR
import('astro/config'): modules / source 905 / 6.6 MB 634 / 5.2 MB 496 / 4.4 MB
astro build: modules 1441 1170 1028
css-tree / unifont / svgo modules during build 358 130 0
import('astro/config') wall, median n=20 813 ms 643 ms 553 ms (−32%)
astro build (warm) wall, median n=20 2916 ms 2845 ms 2464 ms (−16%)
astro build (warm) CPU, median n=20 3030 ms 2910 ms 2740 ms

This PR on its own: import('astro/config') goes from 905 to 901 modules (unifont itself only), and astro build skips the font pipeline.

fontace (via fontProviders.local()) stays eager. Making it lazy needs FontFileReader.extract to become async, and it only costs ~20 ms, so I left it out to keep this diff small.

Testing

  • Fonts tests: fonts.test.ts 21, fontsource.test.ts 1, incremental-build-fonts.test.ts 1, test/units/assets/fonts/* 117. All pass.
  • Full astro suite: test:unit 3859 pass / 0 fail, test:integration 1361 pass / 0 fail, test:types passes.
  • The built dist/ (411 files) and .astro/ types of the benchmark project are byte-identical to main.

Docs

No user-facing behavior change, so no docs needed.

AI disclosure: Code review and benchmarks were something Claude Code (Opus 5.5) helped me with.

withastro/starlight

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

Releases

@astrojs/starlight-docsearch@0.8.2

Patch Changes

@astrojs/starlight@0.42.11

Patch Changes

  • #4332 ad19424 Thanks @RaphaelFakhri! - Fixes the twitter:site meta tag including a trailing slash when the configured X or Twitter social link ends with /
withastro/astro

Changes

  • createRoutesList checks for route collisions by calling detectRouteCollision on every pair of routes, and it copies the array with routes.slice(index + 1) on each outer iteration. That is O(R²) for R routes.
  • The list is rebuilt at astro dev startup, on build, sync, and preview, and in dev on every watcher add, unlink, and change under src/ (vite-plugin-routes → rebuildRoutes). So in dev, the quadratic loop runs on every save.
  • detectRouteCollision only warns in two cases: the routes have the same route string, or all of their segments are semantically equal. This PR groups routes by those two keys and runs the unchanged detectRouteCollision only on pairs within a group. The pairs are deduplicated and sorted by their original indices, so the same warnings are logged in the same order.
  • Routes within a group are still compared pairwise. That only matters when many routes share the same shape, and in that case they would all produce warnings anyway.

Median of 3, Node 24.22.1, measured with astro sync on generated projects of trivial .astro pages. Each project also has two deliberate collisions: a duplicate static route and an [a]/[b] SSR pair. "Collision loop" is the time spent in the collision check alone; "total astro sync" is the wall time of the whole command.

routes mode collision loop, before → after speedup total astro sync, before → after
1,000 static 8.2 → 1.9 ms 4.3× —
1,000 SSR (prerender = false) 21.8 → 2.0 ms 11× —
4,000 static 91.8 → 5.9 ms 16× 0.64 → 0.56 s
4,000 SSR 239 → 6.6 ms 36× 0.79 → 0.59 s
16,000 static 1,281 → 17.5 ms 73× 2.3 → 0.93 s
16,000 SSR 3,973 → 19.7 ms 202× 4.9 → 1.0 s

For a typical site with a few dozen routes, this makes no noticeable difference. It matters for sites with a thousand or more file-based pages: there, the loop is paid at startup and again on every save in dev. At 4,000 SSR routes, the loop took longer than the rest of createRoutesList combined, which includes the filesystem scan and reading every page for prerender. The warning output was identical before and after at every size, in both modes.

Testing

  • Added a createRoutesList unit test in test/units/routing/manifest.test.ts. It pins the exact warnings and their order for:
    • a duplicate static route (file-based plus injected)
    • colliding dynamic ([foo]/[bar]) and rest (docs/[...a]/docs/[...b]) SSR routes
    • same-shape routes where both or one is prerendered (no warning)
    • non-colliding look-alikes (blog/[slug] vs blog-[slug], item/[id]/edit vs item/[id]/view, [...rest])
  • test/units/routing/: 319 pass with this change. The new test also passes on main without the change, so it pins the existing warnings and order.

Docs

No docs change. There is no change to behavior or output, only to performance.


AI disclosure: this change, the test, and the benchmarks were prepared with Claude Code (an AI coding assistant).

🤖 Generated with Claude Code

withastro/astro

Summary

  • Dev trailing-slash and base middleware return HTTP 400 on `decodeURI` failure instead of passing the error through (500)
  • Static preview catches `fileURLToPath` failures from malformed paths and returns 400

Closes #18650

Test plan

  • Repro gist from the issue: `/`, `/fixture/%`, `/fixture/%C0%AF` status codes
withastro/astro

Changes

With all the workflow changes, it seems like something was broken, trying it out to see the logs (or maybe just have it working first try, that'd be cool)

Testing

We'll see

Docs

N/A

withastro/astro

Changes

  • Replaces the legacy compiler in the TypeScript plugin with @astrojs/astro2tsx, which uses compiler-rs to generate virtual TSX and source mappings.
  • Declares the Node.js range ^20.19.0 || >=22.12.0 and removes dependencies used only by the legacy converter.

Testing

  • Adds coverage verifying that script and style contents stay out of virtual TSX.
  • Existing plugin tests cover Astro references, completions, and implementations through the new converter.

Docs

Changeset

Made with AI.

withastro/astro

This PR contains the following updates:

Package Change Age Confidence
vscode-languageclient (source) ^10.1.2 → ^11.0.0 age confidence

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

This PR contains the following updates:

Package Change Age Confidence
vscode-jsonrpc (source) ^9.0.3 → ^10.0.0 age confidence

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

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

Releases

@astrojs/ts-plugin@1.11.0

Minor Changes

Patch Changes

  • #18647 f1c5a5f Thanks @florian-lefebvre! - Fixes TypeScript auto-import suggestions to use the .astro component name instead of its generated TSX name.

astro@7.4.8

Patch Changes

@astrojs/react@7.1.5

Patch Changes

  • #18664 1713dc0 Thanks @ocavue! - Expands the peer dependency version range for oxc-transform-react from ^0.145.0 to >=0.145.0 <0.157.0.

astro-vscode@2.17.3

Patch Changes

  • #18649 39ede5f Thanks @Princesseuh! - Publishes the Astro VS Code extension with the fix for source.organizeImports only organizing imports in one region of .astro files that have both frontmatter and <script> tags
withastro/astro

Changes

  • In validateForwardedHeaders(), a pattern without a protocol field in a mixed allowedDomains list could previously pass any X-Forwarded-Proto value (e.g. ftp, ws) into Astro.url. This happened because matchProtocol() treats undefined as "any protocol", making a mixed list less strict than a uniform list or the documented allow-all [{}]. Protocol-less entries in a mixed list now fall back to the same http/https-only check used by the other configurations.
  • Patterns with an explicit protocol (e.g. { hostname: 'x', protocol: 'wss' }) are still matched exactly, so intentional non-http configurations are unaffected.

Testing

  • Extended packages/astro/test/units/app/node.test.ts with cases covering mixed allowedDomains lists: verifies that ftp, ws, and other non-http(s) values are ignored and do not reach Astro.url, while https continues to pass through correctly.

Docs

  • No docs update needed. The security.allowedDomains API is unchanged; this corrects an unintended permissiveness rather than a documented behavior.

Closes #18639

withastro/starlight

👋 long time no see - we just finished moving https://www.defined.net/docs and https://nebula.defined.net/docs to starlight from docusaurus - the move went great! Noticed that the default contrast was hard to see, was hoping I could maybe upstream a fix before @HiDeoo gets the Pagefind UI 2 PR in (which also fixes this b/c Pagefind fixed it in their v2 UI)

Description

  • Pagefind's default UI styles the search input placeholder with opacity: 0.2, and Starlight doesn't override it. With Starlight's default palette, the placeholder renders at 1.53:1 in light mode and 1.89:1 in dark, well below the 4.5:1 that WCAG 1.4.3 asks of text. Placeholder text isn't covered by any of the criterion's exceptions.
  • This PR sets the placeholder to --sl-color-gray-3 at full opacity: 7.02:1 light, 5.24:1 dark. It still reads as secondary next to the --sl-color-white input text.
  • #4307 (Pagefind UI v2) also fixes this when it lands: Pagefind's component UI colors its placeholder with --pf-text-muted, which that PR maps to --sl-color-gray-3. This picks the same token, so the placeholder looks the same before and after the migration.
  • We hit this on the Nebula docs and patched it locally in DefinedNet/nebula-docs#406.

Screenshots are from examples/basics, built before and after the change:

Before After
Light Search dialog in light mode before the change, with a faint placeholder Search dialog in light mode after the change, with a gray placeholder
Dark Search dialog in dark mode before the change, with a faint placeholder Search dialog in dark mode after the change, with a gray placeholder

🤖 Generated with Claude Code

withastro/astro

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

Releases

astro@7.4.7

Patch Changes

  • 7da442b Thanks @matthewp! - Fixes the image endpoint treating directories whose names differ only by letter case as being inside the build output directory on case-sensitive filesystems
  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1
    • @astrojs/markdown-satteri@0.4.7

@astrojs/cloudflare@14.4.6

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1
    • @astrojs/underscore-redirects@1.0.4

@astrojs/markdoc@2.1.3

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1

@astrojs/mdx@8.1.3

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1
    • @astrojs/markdown-satteri@0.4.7

@astrojs/netlify@8.2.12

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1
    • @astrojs/underscore-redirects@1.0.4

@astrojs/node@11.1.11

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1

@astrojs/preact@6.1.2

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1

@astrojs/react@7.1.4

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1

@astrojs/vercel@11.0.20

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1

@astrojs/internal-helpers@0.13.1

Patch Changes

  • 7da442b Thanks @matthewp! - Fixes the image endpoint treating directories whose names differ only by letter case as being inside the build output directory on case-sensitive filesystems

@astrojs/markdown-remark@7.3.6

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1

@astrojs/markdown-satteri@0.4.7

Patch Changes

  • Updated dependencies [7da442b]:
    • @astrojs/internal-helpers@0.13.1
withastro/astro

Summary

  • Register a single process unhandledRejection listener with one shared AsyncLocalStorage
  • Stops standalone from logging in-request rejections as "outside request context" and from setting process.exitCode = 1

Closes #18624

Test plan

withastro/astro

Part of the implementation of the enhanced content collections RFC (collection metadata).

Changes

  • With experimental.collectionMetadata, astro:build:done receives collections.metadata, the metadata of the build-time collections, and collections.entries(name, { content }), their entries. This is for integrations that validate or post-process content after a build, without the workarounds they use today.
  • The metadata comes from .astro/collections-metadata.json, written by sync. Entries come from the data store the build's sync wrote, which keeps every collection, so collections with a storage driver are included. Each entries() call reads only its collection and keeps nothing: with a chunked data store only the collection's parts are read, and a single-file store is parsed whole and the other collections dropped on return.
  • Entries are plain data, with references and images unresolved. content: false leaves out body and rendered. Live collections and unknown names return no entries. Each integration gets its own copy of the metadata, and each entries() call returns new objects.
  • astro:build:done gets a collections option, typed by BuildDoneCollections. The storage stack (#18632) adds collections.storage to the same option, so whichever lands second merges both fields.
  • Moves the metadata changesets here from #18596, so they stay in the last PR of the stack, and adds one for this hook.

Testing

  • collection-metadata.test.ts builds the fixture with an integration reading collections in astro:build:done: the metadata of build-time collections, entries with and without content, and no entries for a live collection. Without the flag, the hook receives no metadata or entries.

Docs

  • The changesets describe the feature. Docs will come with the experimental flag page.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection storage).

Changes

  • With experimental.collectionStorageDrivers, astro:build:done receives collections.storage: a handle for each storage descriptor the build wrote a snapshot with. Each handle has the collections it holds, the snapshot the build wrote, readAtRuntime (whether pages rendered on demand read it), and the driver's listSnapshots() and deleteSnapshot() when it implements them.
  • Astro never deletes snapshots: it can't know which ones deployed servers, deploy previews or rollback targets still read. Integrations that know decide, through the handles.
  • The handle's deleteSnapshot() throws CollectionStorageSnapshotInUse when asked to delete the build's own snapshot while readAtRuntime is true. It can't protect the snapshots older deployments read.
  • readAtRuntime is true when the server renders a route on demand, except Astro's internal routes that never run project code (the image endpoint and the default 404 page). Server islands and actions count, as they run project code. Builds that skip the content sync, which only in-memory builds do, get no handles.
  • syncInternal() returns the driver loader it used, so the build reuses the drivers sync created. They were loaded through Vite, which closes after sync.
  • Moves the storage changesets here from #18583, so they stay in the last PR of the stack, and adds the cleanup to them.

Testing

  • collection-storage-handles.test.ts covers the handles, the guard, readAtRuntime: false, and drivers without listSnapshots() or deleteSnapshot().
  • collection-storage.test.ts checks the handles a real build passes to an integration.
  • The SQLite package's fixture, a static build, deletes its own snapshot in astro:build:done, which readAtRuntime: false allows.

Docs

  • The changesets describe the feature. Docs will come with the experimental flag page.
withastro/starlight

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

Releases

@astrojs/starlight-docsearch@0.8.1

Patch Changes

  • #4337 c5d0a7f Thanks @moonmeister! - Fixes DocSearch not loading when its script runs after the page has finished loading, for example when a Content Security Policy requires scripts to be added dynamically

@astrojs/starlight@0.42.10

Patch Changes

  • #4354 56b8587 Thanks @jasikpark! - Improves the color contrast of the search input placeholder text

  • #4337 c5d0a7f Thanks @moonmeister! - Fixes search not loading when the search script runs after the page has finished loading, for example when a Content Security Policy requires scripts to be added dynamically

  • #4352 3edab29 Thanks @delucis! - Fixes the Astro trailingSlash and build.format options not being applied correctly to sidebar links that include a query string or hash

withastro/astro

Changes

  • Fixes a case where some dependency-resolution warning logic could throw and stop the build
  • Made with AI

Testing

Adds regression tests

Docs

Changeset

withastro/astro

Changes

  • When security.csp.scriptDirective.strictDynamic is enabled, Astro now emits a <script type="importmap"> in <head> (before any module scripts) that maps every client .js/.mjs asset URL to its SHA digest. Browsers propagate the integrity metadata through dynamic imports, so <script src> entry points, the chunks they import, and import() calls from <astro-island> all load without being blocked by 'strict-dynamic'.
  • The hash of the import map itself, plus the hash of every hashed file, is added to script-src. A new trackScriptIntegrity() helper in core/csp/common.ts reads files from the client output on disk (avoiding the for...in-over-Set bug in the old trackScriptHashes/trackStyleHashes loops that prevented any chunk hashes from reaching the policy). The dead for...in loops are removed. Pages without strictDynamic are unaffected.

Testing

  • New unit tests in packages/astro/test/units/csp/common.test.ts cover trackScriptIntegrity(): hash generation, import map structure, deterministic ordering, and query-string variants for adapters with assetQueryParams.
  • Integration tests added in packages/astro/test/csp.test.ts verify that a built page with strictDynamic: true contains a <script type="importmap"> with the expected integrity entries and that all file hashes appear in script-src.

Docs

  • The strictDynamic JSDoc in types/public/config.ts is extended to explain the import map behaviour and the minimum browser versions required (Chrome 127, Firefox 138, Safari 18). No separate docs-site update is needed beyond that inline note.

Closes #18607

withastro/astro

Changes

  • spreadAttributes now merges the scoped class into a copy of the spread object instead of into the object itself.
  • Before, spreading an object that outlives a render, like a constant imported from another module, appended the scoped class to that object on every render, so the rendered class attribute kept growing per request (class="astro-abc astro-abc astro-abc") and the HTML of unchanged content differed between requests.
  • {...Astro.props} was not affected, because the props are a new object on every render.
  • Adds a changeset.

Closes #18628

Testing

Adds two unit tests to test/units/render/html-primitives.test.ts: spreading an object with a scoped class leaves the object unchanged, and spreading the same object twice renders the same attributes. Both fail without the change and pass with it.

Also checked with the reproduction from the issue: with the change, the element gets the scoped class once on every request in astro dev, and the imported object stays unchanged.

Updates the existing Allows scoped classes with spread test in test/astro-basic.test.ts. Its fixture spreads the same object onto three elements, and only the first gets the scoped class passed in. Before this change, that class leaked into the shared object, so the other two rendered two class attributes (class="astro-xxx" class="has-class"), and the test passed on the leaked one. They now get only their own class; scoping still applies through data-astro-cid-*, which the test now checks for all three.

Docs

No docs change: this restores the behaviour you would expect from a spread, and the docs do not describe spreads as changing their source object.

withastro/astro

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
node (source) major 24.22.2 → 26.13.0
node uses-with major 24.22.2 → 26.13.0
node (source) final major 24.20.0-bullseye → 26.8.1-bullseye

Release Notes

nodejs/node (node)

v26.13.0: 2026-10-28, Version 26.13.0 'Lithium' (LTS), @​richardlau

Compare Source

Notable Changes

This release marks the transition of Node.js 26.x into Long Term Support (LTS)
with the codename 'Lithium'. It will continue to receive updates through to
the end of April 2029.

Other than updating metadata, such as the process.release object, to reflect
that the release is LTS, no further changes from Node.js 26.12.1 are included.

If you are updating from an earlier Long Term Support release (e.g. Node.js 24
or 22 or earlier) please note that since Node.js 25 the official binaries for
Linux are linked against libatomic, which may need to be installed separately
depending on your Linux distribution.

v26.12.1: 2026-10-21, Version 26.12.1 (Current), @​aduh95 prepared by @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
  • (CVE-2026-106069, CVE-2026-106072) tls: reject non-canonical IP addresses (Matteo Collina) – High
  • (CVE-2026-105482) dns: validate resolve inputs for null bytes (James M Snell) – High
  • (CVE-2026-105483) tls: fix ip normalization regression (James M Snell) – High
  • (CVE-2026-111497) src: expose BROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH (Antoine du Hamel) – High
  • (CVE-2026-111497) deps: brotli: cherry-pick 0ed4268 (Evgenii Kliuchnikov) – High
  • (CVE-2026-105481) http: ensure agent data guard works without I/O (James M Snell) – Medium
  • (CVE-2026-106074) crypto: reset random caches across snapshots (Filip Skokan) – Medium
  • (CVE-2026-106070) zlib: avoid caching invalid ZIP local headers (Matteo Collina) – Low
  • (CVE-2026-106071) src: fix the fs permission tree node on wildcard nodes (James M Snell) – Low
  • (CVE-2026-106073) permission: check permission model in realpathSync (RafaelGSS) – Low
  • deps: V8: backport 93cd21e (Joyee Cheung)
  • crypto: update root certificates to NSS 3.131.1 (Antoine du Hamel)
  • tls: reject chains containing blocked public keys (Ulises Gascon)
  • deps: update c-ares to 1.34.9 (Node.js GitHub Bot)
  • tools: retry Gatekeeper check and stapling after notarization (Ryan Aslett)
  • crypto: harden X.509 conversion and formatting (Filip Skokan)
Commits

v26.12.0: 2026-10-14, Version 26.12.0 (Current), @​richardlau

Compare Source

Notable Changes
  • [1ebd6d3677] - (SEMVER-MINOR) doc,lib,src: throw on missing WebAssembly or RX support (Paolo Insogna) #​66533
  • [7f1937d2b9] - (SEMVER-MINOR) http: add websocketMask() and websocketUnmask() (James M Snell) #​66335
Commits

v26.11.1: 2026-10-07, Version 26.11.1 (Current), @​aduh95

Compare Source

Commits
  • [2dc4638e85] - Revert "build: toggle doc-kit verbosity based on V" (Antoine du Hamel)
  • [3febbc54ec] - Revert "build, doc: move to redesign" (Antoine du Hamel)
  • [173250e2e7] - Revert "tools: bump the doc group in /tools/doc with 4 updates" (Antoine du Hamel)

v26.11.0: 2026-10-07, Version 26.11.0 (Current), @​aduh95

Compare Source

Notable Changes
  • [232f178825] - (SEMVER-MINOR) buffer: add isLatin1 (James M Snell) #​66298
  • [27778036de] - (SEMVER-MINOR) buffer: add Buffer.stringLength() (Matteo Collina) #​66064
  • [4f84c4bda2] - build, doc: move to redesign (Aviv Keller) #​62045
  • [6f6296fef9] - (SEMVER-MINOR) doc: promote Alpine Linux to tier 2 support (Stewart X Addison) #​63737
  • [e998d260d0] - (SEMVER-MINOR) http: add isValidHeaderName() and isValidHeaderValue() (James M Snell) #​66334
  • [7702a50e08] - (SEMVER-MINOR) http2: add connectionWindowSize option (Tim Perry) #​65619
  • [e06aa62cec] - (SEMVER-MINOR) perf_hooks: fix truncation of monitorEventLoopDelay() resolution (James M Snell) #​66115
  • [ee126e37e8] - (SEMVER-MINOR) perf_hooks: allow RecordableHistogram to record 0 (James M Snell) #​66114
  • [1fef8f54db] - (SEMVER-MINOR) perf_hooks: add histogram.diff() (James M Snell) #​66099
  • [f1b9758c4e] - (SEMVER-MINOR) perf_hooks: add histogram.snapshot() (James M Snell) #​66099
  • [291d56ea3e] - (SEMVER-MINOR) perf_hooks: harden histogram CBOR import validation (James M Snell) #​66098
  • [6299b09d5c] - (SEMVER-MINOR) process: graduate process.ref/unref to stable (James M Snell) #​66213
  • [41d6707b63] - (SEMVER-MINOR) sqlite: rename DatabaseSync and StatementSync (Guilherme Araújo) #​65988
  • [60d0aa0cd4] - (SEMVER-MINOR) src: add --process-timeout=N (James M Snell) #​66138
  • [f39916a7e3] - (SEMVER-MINOR) src: expose size and count in heap profile output (Ilyas Shabi) #​65737
  • [0b00d5ea59] - (SEMVER-MINOR) src: let embedders exempt linked bindings from the addon permission (Shelley Vohr) #​66067
Commits

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

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

withastro/astro

This PR contains the following updates:

Package Change Age Confidence
sitemap ^9.0.1 → ^10.0.0 age confidence

Release Notes

ekalinin/sitemap.js (sitemap)

v10.0.0

Compare Source

[BREAKING CHANGES]
Dropped CommonJS build — the package is now ESM-only
  • require('sitemap') is no longer supported on Node versions without
    built-in require(esm). The dist/cjs build, the require export condition,
    and tsconfig.cjs.json are all gone; exports now resolves to dist/index.js
    for every consumer. Migrate to import { SitemapStream } from 'sitemap'.
  • Node.js >=22.22.1 now required (previously >=20.19.5). CommonJS
    consumers can still load this package through require(esm), which landed
    unflagged in 22.12; the floor is 22.22.1 to match the development toolchain.
  • Build output flattened from dist/esm/* and dist/cjs/* to dist/*. The
    bin entry is now dist/cli.js.
simpleSitemapAndIndex defaults to 45,000 URLs per sitemap
  • The default limit drops from 50,000 to 45,000, the same default
    SitemapAndIndexStream and the CLI already use (DEFAULT_SITEMAP_ITEM_LIMIT).
    The headroom keeps rich entries (images, video, news) under the 50MB
    uncompressed file-size limit. A 50,000-URL input now produces two sitemap
    files instead of one; pass limit: 50000 to keep the old output.
SitemapStream writes an empty sitemap instead of erroring
  • Ending a SitemapStream without writing any items now produces a
    well-formed empty <urlset> instead of failing with EmptySitemap
    (#​394, #​421). This matches SitemapIndexStream, which already wrote an empty
    <sitemapindex>. EmptySitemap is still exported but deprecated and no
    longer thrown. An empty <urlset> does not pass strict sitemap.xsd
    validation, which requires at least one <url>; search engines accept it.
One logger option across the library; xmlNS renamed to xmlns
  • SitemapStream, SitemapIndexStream, SitemapAndIndexStream and
    simpleSitemapAndIndex accept the same logger option the parsers already
    had (#​348). Validation warnings that went straight to console.warn now go
    through it. Pass false to silence. The Logger type is now exported.
  • Invalid news and video attribute values now go through errorHandler (and
    so the logger) like every other validation error, instead of a hardcoded
    console.warn. The warning text is now the error's name and message, which starts with
    the item's URL. Under ErrorLevel.THROW a custom errorHandler receives
    these errors too, like every other validation error; the default handler
    still throws.
  • The SitemapStream property xmlNS is now xmlns, matching the option
    name (#​300). xmlNS still works as a deprecated alias. SitemapStream.errorHandler is always set now; it defaults to
    a handler that warns through logger.
Both XML parsers share one error store and entry cap

XMLToSitemapItemStream and XMLToSitemapIndexStream now extend one internal
base class, so they report errors and cap entries the same way.

  • XMLToSitemapIndexStream.error is a read-only getter for the first error
    (errors[0], or null). Assigning to it now throws a TypeError in strict
    mode. The index parser also gains the errors array (capped at
    LIMITS.MAX_PARSER_ERRORS) and errorCount, where it previously kept only
    the first error.
  • XMLToSitemapItemStream reports a sitemap with more than 50,000 <url>
    entries once, instead of logging and recording an error for every dropped
    entry, so errorCount and the log no longer grow with the overflow. It
    gains the index parser's maxEntries option, entryCount property and
    'maxEntriesExceeded' event, and an error getter. urlCount still works
    as a deprecated alias for entryCount. parseSitemap still resolves with
    the first 50,000 items, but it now stops reading once the cap is crossed
    and destroys the source stream, as parseSitemapIndex already did.
  • Both parsers now fail on a truncated document (an element left unclosed
    when the input ends), like any other malformed XML. Before, the
    unfinished entry was dropped silently. parseSitemap and
    parseSitemapIndex reject in that case, and parseSitemap now also
    rejects when the source stream fails instead of never settling.
  • The index parser's warnings for an invalid <loc> or <lastmod> are now
    logged as one message, the same text recorded in errors. The recorded
    lastmod error now reads Invalid lastmod date format in sitemap index: ….
SitemapAndIndexStream destroys itself on error
  • When a sitemap stream errors, or getSitemapStream throws or returns an
    invalid tuple, SitemapAndIndexStream now destroys itself and emits the
    error once. It used to emit the error without stopping, so the same failure
    could be emitted twice, and a getSitemapStream failure was followed by a
    generic No sitemap stream available error. Code that listened for error
    and kept writing now gets write-after-destroy errors instead.
sitemap --index --gzip names sitemaps sitemap-N.xml.gz
  • With --gzip, sitemap --index now writes each sitemap to sitemap-N.xml.gz
    and lists that URL in the index, as simpleSitemapAndIndex already did. It
    used to write gzipped data to sitemap-N.xml and index it under that name,
    so crawlers fetched gzip bytes from a .xml URL. Update scripts that upload
    or serve sitemap-*.xml after a gzipped run.
SitemapStream reports item errors as stream errors
  • SitemapStream and SitemapItemStream now report a failure on an item
    through the stream: write() no longer throws, and the stream emits
    error and is destroyed. This covers an invalid item at
    ErrorLevel.THROW, an item normalizeURL rejects (such as an invalid
    lastmod), and an item that can't be serialized (such as a non-string
    video attribute at ErrorLevel.SILENT). Before, the error was thrown out
    of write(), so a piped source crashed the process with an uncaught
    exception. Code that wrapped write() in try/catch must listen for
    error instead, or use pipeline().
  • SitemapStream checks xmlns.custom in its constructor, so an invalid
    custom namespace now throws from new SitemapStream() instead of from the
    first write().
  • SitemapStream serializes each item itself instead of piping it through an
    internal SitemapItemStream, so it now outputs one chunk per item. The XML
    is unchanged.
Stricter priority and alternate-link validation
  • A priority of NaN is now reported as a PriorityInvalidError: it
    throws at ErrorLevel.THROW and warns at WARN. It used to skip
    validation and write <priority>NaN</priority> at every level.
  • An alternate link with no lang or hreflang is now reported as the new
    InvalidLinkHreflang error at WARN and THROW, and dropped from the
    output at WARN and SILENT. SitemapItemStream, which doesn't
    validate, drops it too, with no warning. Every level used to fail with a
    TypeError from the XML writer. Writing the link without hreflang would
    produce the androidLink markup, which parses back as androidLink.
Error classes are exported by name; UndefinedTargetFolder removed
  • index.ts lists the error classes explicitly instead of
    export * from './lib/errors.js', like the public types, so a new error
    class is public only once it is added there.
  • UndefinedTargetFolder is removed. Nothing has thrown it since 7.0.0,
    which removed createSitemapsAndIndex, its only user.
Changed
  • The CLI parses arguments with Node's built-in util.parseArgs instead of
    the arg package, which is no longer a dependency (#​471). Unknown options
    and a non-integer --limit now print a message and exit with code 2 instead
    of throwing an uncaught error.
  • Test suite migrated from Jest to the built-in Node.js test runner. Coverage
    thresholds moved from jest.config.cjs into the test:coverage script and are
    enforced in CI by a dedicated job.
  • CI now runs on Linux, Windows and macOS across Node 22/24/26. Lint, formatting
    and typechecking run once rather than on every matrix leg.
  • Stricter <loc> validation in the sitemap parser: XMLToSitemapItemStream
    now validates <loc> values with the same validateURL used by the sitemap
    index parser, adding a URL-parseability check on top of the existing length
    and protocol checks. A malformed URL that passed the old checks but fails
    new URL() is now dropped with a warning (or throws under
    ErrorLevel.THROW). Warn/error messages for invalid <loc> values changed to
    the Invalid URL in sitemap: … form.
  • validateURL throws InvalidURLError, a new subclass of
    InvalidHostnameError (so instanceof InvalidHostnameError still matches).
    Its message reads Invalid URL "…": … instead of Invalid hostname "…": …,
    and it shows at most the first 100 characters of the offending value.
  • Stricter video validation in validateSMIOptions: a video duration,
    rating or view_count that is NaN, Infinity or otherwise non-numeric
    is now reported as invalid (and throws under ErrorLevel.THROW). Previously
    only out-of-range finite numbers were caught, so NaN slipped through.
  • XMLToSitemapItemStream now buffers each element's character data and
    handles it once at the next tag boundary: text and CDATA chunks within one
    element are joined, surrounding whitespace is trimmed for CDATA as it already
    was for text, whitespace between chunks is kept (Episode <![CDATA[One]]>
    now parses as Episode One, not EpisodeOne), and stray character data
    between elements is reported against
    the enclosing element instead of overwriting the previous one. Character data
    longer than LIMITS.MAX_PARSER_CHAR_DATA_LENGTH (64 KiB) for one element is
    dropped with a warning.
  • Internal: the parser's duplicated text/cdata SAX handlers were collapsed
    into one, and its inline bounds checks (priority, video duration/rating/view
    count, ISO dates) now delegate to shared guards in lib/validation.ts, with
    the bounds defined once in LIMITS.
  • XMLToSitemapIndexStream now handles character data the same way: text and
    CDATA within one <loc> or <lastmod> are joined and trimmed, stray
    character data is reported against the enclosing element, and values longer
    than LIMITS.MAX_PARSER_CHAR_DATA_LENGTH are dropped with a warning.
    Unhandled CDATA is now logged as unhandled text for tag: instead of
    unhandled cdata for tag:. Both parsers share one buffer,
    createCharDataBuffer in lib/utils.ts.
  • XMLToSitemapIndexStream enforces the 50,000-entry spec limit itself.
    Entries past LIMITS.MAX_SITEMAP_ITEM_LIMIT are dropped with a single error
    (which throws under ErrorLevel.THROW), and a new entryCount property counts
    every <sitemap> seen. Previously only the parseSitemapIndex wrapper capped
    entries, so piping the stream directly had no limit. parseSitemapIndex still
    rejects an over-limit index and stops reading as soon as the limit is crossed,
    but a maxEntries above 50,000 no longer raises the limit. A new
    maxEntries stream option lowers the cap, or raises it (Infinity turns it
    off) for callers that knowingly parse oversized indexes. When the cap is
    crossed the stream emits 'maxEntriesExceeded', and logs the overflow only
    if nothing listens for that event, so parseSitemapIndex rejects without
    also logging. maxEntries: 0 is allowed (nothing is emitted, and
    parseSitemapIndex rejects on the first entry); a negative, fractional or
    NaN value is rejected, and parseSitemapIndex destroys the source stream
    before rejecting.
  • Errors that simpleSitemapAndIndex and SitemapAndIndexStream wrap, such
    as Failed to write sitemap files: … or a getSitemapStream failure, now
    carry the original error as cause.
  • SaxParserStreamOptions, the shared base of XMLToSitemapItemStreamOptions
    and XMLToSitemapIndexItemStreamOptions, is exported.
  • LIMITS gains the bounds the validators use: MIN_PRIORITY,
    MAX_PRIORITY, PRIORITY_STRING_REGEX, MIN_VIDEO_DURATION,
    MAX_VIDEO_DURATION, MIN_VIDEO_RATING, MAX_VIDEO_RATING and
    MIN_VIDEO_VIEW_COUNT.
  • LIMITS.MAX_URL_ENTRIES is deprecated. Nothing reads it; the parsers cap
    entries at LIMITS.MAX_SITEMAP_ITEM_LIMIT (the same value), which their
    maxEntries option overrides.
Fixed
  • A string priority no longer crashes SitemapStream with
    item.priority.toFixed is not a function (#​393). A plain decimal string
    such as '0.5' or '.5' is converted to a number (hex, binary and
    exponent forms such as '0x1' or '1e-1' are not), and
    SitemapItemLoose.priority now accepts number | string. Any other value,
    including an empty string, is reported as a PriorityInvalidError at
    WARN and THROW, and written as given at WARN and SILENT, like other
    invalid values. isValidPriority rejects non-numbers instead of coercing
    them.
  • isValidYesNo accepts only a whole yes, Yes, YES, no, No or NO.
    Its unanchored alternation used to accept any value that started with YES,
    contained NO or yes, or ended in no, such as NOPE or maybe-yes, so
    the parsers and validateSMIOptions let those values through.
  • XMLToSitemapItemStream reports an invalid video:requires_subscription,
    video:family_friendly, video:live or player_loc allow_embed value as a
    warning and a parse error. It used to drop the value without a word. It also
    trims whitespace around allow_embed, as it already does for element text.
  • validateSMIOptions checks requires_subscription, live and
    player_loc:allow_embed as well as family_friendly, and reports an invalid
    value with the new InvalidVideoYesNo error.
  • SitemapAndIndexStream errors with ERR_STREAM_PREMATURE_CLOSE instead of
    hanging when a sitemap's write stream is destroyed before it finishes, at any
    point in the sitemap. A SitemapAndIndexStream destroyed during rotation no
    longer opens another sitemap file once the current one has finished.
  • SitemapAndIndexStream destroys itself with the error when a sitemap's write
    stream fails while the sitemap is still open, such as EACCES or EISDIR
    when opening the file. It used to crash the process with an unhandled
    error event. simpleSitemapAndIndex now rejects in that case.
  • Destroying a SitemapAndIndexStream also destroys the open sitemap and its
    write stream, so the file descriptor is released.
  • SitemapAndIndexStream destroys the streams getSitemapStream returned when
    it rejects the tuple, instead of leaving their file open.
  • At ErrorLevel.THROW, SitemapAndIndexStream fails when the index rejects a
    sitemap's index item, such as a non-http(s) URL. It used to drop the error,
    writing the sitemap file without listing it in the index.
  • simpleSitemapAndIndex and the CLI connect each sitemap to its gzip and file
    streams with pipeline(), so a gzip failure fails the sitemap instead of
    leaving the write stream open.
  • SitemapAndIndexStream fails with the error, instead of leaving an unhandled
    promise rejection, when writing the first item of a sitemap after rotation
    throws.
  • At ErrorLevel.THROW, SitemapIndexStream no longer outputs a partial
    <sitemap><loc> element before it fails on an invalid lastmod.
  • simpleSitemapAndIndex and the CLI validate each sitemap URL before they
    create its file, so a URL the index rejects no longer leaves an empty
    sitemap file behind. They now fail on such a URL at every error level.
  • sitemap --index prints a stream error and exits with code 1 instead of
    crashing with an unhandled error event.
  • sitemap --validate exits with code 1 when the sitemap is invalid and 2 when
    validation cannot run (xmllint missing or not executable, or schema not
    found). It used to exit 0 in every case, so scripts and CI could not detect a
    failed validation. An xmllint that fails to start for a reason other than
    ENOENT, such as EACCES, now rejects xmlLint() with [error] alone
    instead of [error, ''], so it is no longer reported as an invalid sitemap.
  • sitemap --prepend writes every entry of the prepended sitemap, then the new
    URLs. Both sources were piped into one stream, so whichever ended first
    ended the sitemap: a large prepended file was cut off after its first entries
    and failed with a write-after-end error.
    A prepended file with more than 50,000 URLs, the most a sitemap may hold,
    now fails with exit code 1 instead of being silently truncated.
  • sitemap --parse, --prepend and the default mode print a stream error,
    such as a parse error or a missing input file, and exit with code 1 instead
    of crashing with an unhandled error event. In those modes a reader that
    closes stdout early, such as | head, is not treated as an error. In
    --index mode it still is (exit code 1), because the sitemap files written
    so far are left incomplete.
  • xmlLint() and sitemap --validate find the bundled schema/ directory
    when the package is installed as a dependency. The lookup searched relative
    to process.cwd(), so outside this repository it threw a synchronous
    "Schema directory not found" error that crashed the CLI. It now walks up from
    the module's own directory, and a missing schema rejects the promise instead
    of throwing.
  • xmlLint() destroys a Readable input if xmllint exits or fails to start
    before reading all of it, so the source no longer stays paused with its file
    descriptor open.
  • SitemapStream and SitemapIndexStream check their public level field
    when they warn, so changing level after construction takes effect again,
    as it did in 9.0.1.
  • @types/node is a runtime dependency again, as it was in 9.0.1, because the
    published type definitions import Node's stream types. The range now covers
    every supported Node major (^22 || ^24 || ^26), so npm can share a
    consumer's own copy.
  • XMLToSitemapItemStream now treats CDATA sections as ordinary character data
    in every tag. Previously only the 8 tags from issue #​445 (loc, image:loc,
    video:title, video:description, news:name, news:title,
    image:caption, image:title) accepted CDATA; content in any other tag was
    logged as unhandled. See docs/adr/0001-cdata-is-character-data.md.
  • xmlLint() no longer probes for the binary with which, which is not a
    command on Windows and made validation report XMLLintUnavailable there even
    when xmllint was installed. A missing binary is now detected via ENOENT from
    the spawn itself, which is correct on every platform.
  • The published tarball now contains only dist/ and schema/ (via a files
    allowlist), so maintainer files such as CLAUDE.md no longer ship to
    consumers (#​480).
  • The CLI locates package.json by walking up from its own directory instead of
    a hardcoded relative depth, so --version no longer breaks when the build
    output layout changes.
  • sitemap --index reports an invalid --limit with the same message as
    simpleSitemapAndIndex's InvalidLimitError, prefixed with --limit:, and
    accepts only decimal digits: forms such as 1e3, 0x10 or 250 are
    rejected rather than converted.
  • InvalidLimitError says the limit must be an integer between 1 and 50000,
    rather than a number, since fractional limits are rejected too.
  • XMLToSitemapItemStream no longer adds an empty { url: '', lang: '' }
    entry to links for an xhtml:link that lacks rel or href or has an
    unsupported rel. It still warns and records a parse error.
  • XMLToSitemapItemStream and XMLToSitemapIndexStream copy their options
    instead of setting objectMode on the object the caller passed in.
Documentation
  • api.md now documents XMLToSitemapIndexStream and parseSitemapIndex, and
    the 50,000-entry and error-array caps the parsers enforce.
  • api.md no longer claims simpleSitemapAndIndex accepts an absolute
    destinationDir; absolute paths have been rejected since 9.0.1 (#​478).
  • JSDoc examples for parseSitemap and parseSitemapIndex use import and
    current APIs instead of require() and the removed createSitemap.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/starlight

Description

  • Fixes #4286
  • Supersedes and closes #4287
  • This fixes cases where a user passes a link containing a search query or fragment hash in their sidebar config. Our link formatter would previously incorrectly include those as part of the URL pathname, instead of ensuring they are appended after any .html extension or trailing slashes.
  • This PR incorporates @HiDeoo’s reviews from #4287 given OP was not responsive there.
withastro/astro

Changes


  • The audit's perf-use-image-component and perf-use-videos rules read a loaded image's size from its Resource Timing entry (decodedBodySize) instead of fetching it again.
  • They still fetch when there is no entry, as for an image that hasn't loaded.
  • In WebKit, fetching an animating SVG's URL froze its CSS animations, so Safari stopped them under astro dev.

Testing

  • New e2e test in dev-toolbar-audits.test.ts: the audit flags a large <img> without a second fetch of it. It fails without the fix.
  • The reproduction, checked in WebKit and Chromium: the ring now completes under astro dev.

Docs

None: no user-facing behaviour changes beyond the fix.

withastro/starlight

Description

withastro/astro

This PR contains the following updates:

Package Change Age Confidence
p-queue ^9.3.5 → ^10.0.0 age confidence

Release Notes

sindresorhus/p-queue (p-queue)

v10.0.0

Compare Source

Breaking
  • Require Node.js 22 300a52d
  • The queue is now an EventTarget instead of an EventEmitter 300a52d
    • Use .addEventListener() and .removeEventListener() instead of .on(), .once(), .off(), and the other EventEmitter methods.
    • The completed and error events have the result or the error in event.detail.
    • An error thrown in an event listener now exits the process. Node.js reports it as an uncaught exception.
  • .clear() now rejects the promises of the removed tasks with an AbortError instead of leaving them pending forever 64311ff
    • .clear() marks these promises as handled, but a promise made from them, like the one from .addAll() or queue.add(fn).then(…), now rejects, so handle it.
  • TimeoutError is now a DOMException named TimeoutError, like the error of AbortSignal.timeout() 300a52d
  • Remove the deprecated carryoverConcurrencyCount option: use carryoverIntervalCount 300a52d
  • Stricter validation of options 76a48ba d65d567
    • concurrency and intervalCap must be integers (or Infinity). A limit of 1.5 used to let 2 tasks run.
    • timeout and interval above 2147483647 ms (the maximum timer delay) are rejected. They used to fire after 1 ms.
    • .add() rejects with a TypeError when priority is NaN or not a number.
  • .start(), .clear(), and setting concurrency no longer emit empty and idle when the queue is already empty, so idle no longer fires on a queue that never had a task aeedf53
  • A custom queueClass must now implement remove() 300a52d
Improvements
  • Zero dependencies! 300a52d
  • A task now runs in the async context of its .add() call, so it sees the AsyncLocalStorage values of the caller, also when it starts later (Node.js 22.3 and later, Deno, and Bun) (#​200) a5b7b54
    • Previously, a waiting task could see the values of whatever started it, like another request on a server.
  • A task with a timeout now gets a signal that aborts when the task times out, so you can pass it on to fetch() and similar to stop the work 300a52d
  • .onEmpty() and the empty event now fire when the last waiting task starts, not when the next task finishes 1cf5b82 cb25a0a
  • .addAll() now resolves with a typed tuple when the tasks return different types 36e83aa
Fixes
  • Fix many rate-limit bugs where intervalCap was exceeded at the end of a window, a waiting task got stuck, or isRateLimited was wrong 6af55a7 1cf5b82 6c08a4f ac89911 450356a
  • Fix slow add, run, and abort for many tasks that share a signal, and PriorityQueue keeping finished tasks in memory 95622a4 6fb8337
  • Fix many edge cases with events and priorities, like infinite recursion in an idle listener and events in the wrong order aeedf53 b33dd44 8792846 e79f970 d65d567 6f6028a
  • Fix undefined options and an invalid .timeout setter breaking the queue d6cf96b 48586f4
  • Fix many TypeScript types 36e83aa fa3c3e0

Migration guide

Events
-queue.on('completed', result => {
-	console.log(result);
-});
+queue.addEventListener('completed', event => {
+	console.log(event.detail);
+});

-queue.once('idle', () => {});
+queue.addEventListener('idle', () => {}, {once: true});

If the result or the error is undefined, event.detail is null, because CustomEvent works that way.

Other differences from EventEmitter:

  • If you add the same listener twice, it is called once.
  • A listener that is removed while an event is dispatched is not called for that event.
.clear()

The promises of the removed tasks now reject with an AbortError. If you await them, handle the rejection:

const results = await queue.addAll(tasks).catch(error => {
	if (error.name === 'AbortError') {
		return [];
	}

	throw error;
});
Timeouts and signals

error instanceof TimeoutError still works. You can also check error.name === 'TimeoutError', which also matches the error of AbortSignal.timeout().

Other changes:

  • The TimeoutError stack trace no longer shows where the task was added.
  • With timeout set, the task's signal is no longer linked to your signal after the task finishes.
  • Tasks with a signal or timeout settle 2 microtasks later than before.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

This PR contains the following updates:

Package Change Age Confidence
muggle-string ^0.4.1 → ^1.0.0 age confidence

Release Notes

johnsoncodehk/muggle-string (muggle-string)

v1.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

This PR contains the following updates:

Package Change Age Confidence
chokidar ^5.0.0 → ^6.0.0 age confidence

Release Notes

paulmillr/chokidar (chokidar)

v6.0.0

Compare Source

High-level changes
  • Rewrote the watcher around a single observation pipeline. Backend callbacks are treated as invalidations and confirmed with lstat, stat, or readdir before any event is emitted, so the final state after a burst of changes matches the filesystem.
  • Added native recursive watching through fs.watch({ recursive: true }). The default auto backend uses it on macOS and Windows and per-directory watching elsewhere.
  • Shared native handles across watchers and opened them per directory only: files no longer own handles. This fixes EBADF errors when watching many files on macOS (#​1385, #​1452).
  • Replaced fs.watchFile with Chokidar-owned stat polling. Poll loops are shared across watchers at the fastest requested interval.
  • Required Node.js 22.22 or later.
API changes
  • Added the backend option: 'auto' (default), 'native', 'native-recursive', or 'polling'.
    • usePolling: true remains as a deprecated alias for backend: 'polling'.
  • Renamed interval and binaryInterval to pollingInterval and pollingBinaryInterval.
    • The old names remain as deprecated aliases; the new names win when both are given.
  • Changed the atomic default to false with polling. An explicit value is preserved.
  • Made close() terminal: add() now throws once closing has started. Construct a new watcher instead.
  • Validated options in the constructor: invalid backend, atomic, depth, awaitWriteFinish, and polling intervals throw TypeError.
  • Emitted errors from add() as error events instead of unhandled rejections (#​1378).
  • Made getWatched() return a null-prototype object, so a watched directory named __proto__ is listed (#​1493). Use Object.hasOwn() instead of hasOwnProperty() on the result.
  • Stopped applying ignored to directories above a path passed to watch() or add(), so a missing path is still watched through its parent (#​1374). Other entries in those directories are still filtered.
Fixes
  • Fixed a 100% CPU loop when the process working directory containing a relatively watched file was deleted (#​1474).
  • Fixed watching a filesystem root, which emitted unlink and unlinkDir for every entry (#​1184, #​452).
  • Fixed UNKNOWN errors from fs.watch on macOS sockets, which prevented watching /var/run (#​1391).
  • Fixed a symlink whose target passes through a regular file (ENOTDIR) disabling watching of its directory and preventing ready (#​1476).
  • Fixed files created in a newly added directory between its scan and watch registration being missed (#​1471).
  • Fixed watching a missing nested path stopping its parent directory's subtree from being watched (#​1470).
  • Fixed false change events on Windows when many sibling files are written (#​1466).
  • Fixed duplicate add events for unchanged files under directory activity (#​1465).
  • Fixed replacing a watched directory with a file of the same name hanging the process (#​1464).
  • Fixed persistent watching stopping after a watched directory was removed (#​1463).
  • Fixed a deleted watched path not being reported when recreated: previously only a deleted file that was the sole watched path was watched for its return. Any path passed to watch() or add() is now awaited from its nearest existing parent.
  • Fixed event throttling discarding updates; the newest differing change is now replayed when the window closes (#​1455).
  • Fixed relative ignored paths; relative strings now resolve against cwd or the process working directory (#​1436).
  • Fixed files not being detected when their directory did not exist before watching (#​1422).
  • Fixed removed files being reported as unlinkDir instead of unlink (#​1421).
  • Fixed ignored files and directories still being watched in WSL (#​1418).
  • Fixed change being reported for every file when one file changed under Deno (#​1417).
  • Fixed changes not being detected after the second save (#​1399).
  • Fixed renaming a watched directory that contains subdirectories on Windows (#​1380, #​1398).
  • Fixed re-watching a path not honoring ignoreInitial (#​1386).
  • Fixed EISDIR errors during the initial scan of network drives (#​1376).
  • Fixed watching an array of absolute file paths (#​1366).
  • Fixed unwatching a deleted watched directory on Windows, contributed by @​sapphi-red in pull request #​1467.
  • Documented that unwatched paths stay ignored until they are added again (#​1439).
Misc

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

withastro/astro

Changes

  • Replaces yargs-parser with mri for Astro CLI argument parsing while preserving existing option handling. Recommended by e18e
  • Leaves @astrojs/check on its existing parser and dependency.

Testing

  • Adds parser contract coverage for positionals, aliases, negated flags, optional and repeated values, unknown options, and the -- delimiter.

Docs

Changeset

AI was used to help implement this change.

withastro/starlight

Description

This PR tweaks some of our workflows to reduce the number of unnecessary CI workflow runs triggered by Changesets release PRs.

Sharing a diagram of the new approach to make it easier to follow if needed:

flowchart LR
  A["PR merged to main"] --> B["Draft release PR created or updated"]
  B --> C["CI skipped"]
  C --> D["Maintainer marks release PR as ready for review"]
  D --> E["CI runs once"]
  E --> F{"Another PR merged to main?"}
  F -- "Yes (back to draft)" --> B
  F -- "No" --> G["Release PR merged"]
Loading

When a Changesets release PR is opened, every merge to the main branch updates it and triggers CI workflows on the release branch. These runs do not provide a lot of value as they run in parallel with the ones we already run on the main branch on slightly different content (package.json files updates, lockfile changes, and Markdown changes for the changelogs).

The idea is to not automatically run CI workflows for Changesets release PRs until we are ready to release as a last verification step. In the Starlight repository, the impact should be moderate but it's a good test bed for this approach to see if we could use something similar in a few other repos where some workflows take a long time to run and count heavily against our org runner limits.

These workflows are automatically started because the changesets/action action does not use the default GITHUB_TOKEN token. When the default GITHUB_TOKEN is used, GitHub automatically puts triggered workflows in an approval-required state. Unfortunately, this is more of a behavior than a feature as I could not find any documented way to say "if ... then put this workflow in an approval-required state".

I experimented with various approaches to implement this behavior in a private repo, e.g. an environment with required reviewers to gate workflow runs, but this PR ends up using an approach that sounds simpler to me as everything happens in the PR page itself and only involves a well-known feature: draft PRs.

In practice, Changesets release PRs are now created (and updated) as draft PRs. We use this state to prevent some CI workflows from running automatically, and when we are ready to release, a maintainer can mark the PR as ready for review, which will then trigger all expected CI workflows. As draft PRs cannot be merged, this also prevents merging an untested release PR.

If a PR is merged to main while the release PR is already ready for review, the release PR is updated and converted back to a draft and needs to be marked as ready for review again.

withastro/astro

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@astrojs/astro2tsx (source) ^0.1.2 → ^0.1.3 age confidence dependencies patch
@astrojs/compiler-rs (source) ^0.5.1 → ^0.5.2 age confidence dependencies patch
@astrojs/language-server (source) ^2.17.2 → ^2.17.3 age confidence devDependencies patch
@babel/core (source) ^8.0.7 → ^8.0.10 age confidence devDependencies patch 8.1.0
@cloudflare/vite-plugin (source) ^1.63.1 → ^1.66.0 age confidence dependencies minor 1.67.0
@cloudflare/vitest-plugin (source) 1.4.4 → 1.4.11 age confidence devDependencies patch 1.5.1 (+2)
@cloudflare/workers-types ^5.20261012.1 → ^5.20261101.1 age confidence devDependencies minor 5.20261104.1 (+2)
@earendil-works/pi-ai (source) ^0.87.1 → ^0.99.2 age confidence devDependencies minor
@fastify/middie ^9.3.5 → ^9.3.6 age confidence devDependencies patch
@fastify/static ^10.1.6 → ^10.1.8 age confidence devDependencies patch 10.1.9
@flue/runtime (source) ^2.2.2 → ^2.3.0 age confidence devDependencies minor
@markdoc/markdoc (source) ^0.5.10 → ^0.5.11 age confidence dependencies patch
@netlify/blobs (source) ^11.1.4 → ^11.1.7 age confidence dependencies patch
@netlify/functions (source) ^6.0.2 → ^6.0.3 age confidence dependencies patch
@preact/signals (source) ^2.11.3 → ^2.11.4 age confidence dependencies patch
@preact/signals (source) 2.11.3 → 2.11.4 age confidence dependencies patch
@qwik.dev/partytown ^1.0.1 → ^1.0.3 age confidence dependencies patch
@rolldown/plugin-babel (source) ^0.2.4 → ^0.3.0 age confidence devDependencies minor
@solidjs/router ^1.0.0 → ^1.0.1 age confidence dependencies patch
@types/estree (source) ^1.0.9 → ^1.0.10 age confidence devDependencies patch
@vercel/functions (source) ^3.9.11 → ^3.10.5 age confidence dependencies minor 3.10.6
@vercel/routing-utils (source) ^6.6.0 → ^6.6.1 age confidence dependencies patch
@volar/kit (source) ~2.4.28 → ~2.4.30 age confidence dependencies patch
@volar/language-core (source) ~2.4.28 → ~2.4.30 age confidence devDependencies patch
@volar/language-core (source) ~2.4.28 → ~2.4.30 age confidence dependencies patch
@volar/language-server (source) ~2.4.28 → ~2.4.30 age confidence devDependencies patch
@volar/language-server (source) ~2.4.28 → ~2.4.30 age confidence dependencies patch
@volar/language-service (source) ~2.4.28 → ~2.4.30 age confidence dependencies patch
@volar/test-utils (source) ~2.4.28 → ~2.4.30 age confidence devDependencies patch
@volar/typescript (source) ~2.4.28 → ~2.4.30 age confidence dependencies patch
@volar/typescript (source) ~2.4.28 → ~2.4.30 age confidence devDependencies patch
@volar/vscode (source) ~2.4.28 → ~2.4.30 age confidence devDependencies patch
@vscode/vsce (source) ^4.0.0 → ^4.1.0 age confidence devDependencies minor
@vue/compiler-sfc (source) ^3.5.43 → ^3.5.44 age confidence dependencies patch
CodSpeedHQ/action v5.4.2 → v5.6.1 age confidence action minor v5.6.3
alpinejs (source) ^3.17.4 → ^3.17.5 age confidence dependencies patch
autoprefixer ^10.6.1 → ^10.6.2 age confidence dependencies patch
devalue ^6.0.2 → ^6.0.3 age confidence dependencies patch
devalue ^6.0.2 → ^6.0.3 age confidence devDependencies patch
es-module-lexer ^3.0.3 → ^3.0.4 age confidence dependencies patch
eslint (source) ^10.12.0 → ^10.14.0 age confidence devDependencies minor
eslint-plugin-regexp ^3.3.1 → ^3.3.3 age confidence devDependencies patch
hast-util-to-html ^9.0.5 → ^9.0.6 age confidence dependencies patch
hast-util-to-text ^4.0.2 → ^4.0.3 age confidence dependencies patch
hono (source) ^4.13.13 → ^4.13.16 age confidence dependencies patch
hono (source) ^4.13.13 → ^4.13.16 age confidence devDependencies patch
linkedom ^0.18.13 → ^0.18.15 age confidence devDependencies patch
linkedom ^0.18.14 → ^0.18.15 age confidence devDependencies patch
magic-string ^1.4.3 → ^1.4.5 age confidence dependencies patch
node (source) 24.21.0 → 24.22.2 age confidence minor
node 24.21.0 → 24.22.2 age confidence uses-with minor
ovsx (source) ^1.2.0 → ^1.3.0 age confidence devDependencies minor
oxc-transform-react (source) ^0.153.0 → ^0.156.0 age confidence dependencies minor 0.157.0
oxc-transform-react (source) ^0.153.0 → ^0.156.0 age confidence devDependencies minor 0.157.0
pkg-pr-new (source) ^0.0.88 → ^0.0.93 age confidence devDependencies patch
pnpm (source) 11.28.4 → 11.28.10 age confidence packageManager patch
postcss (source) ^8.5.29 → ^8.5.32 age confidence dependencies patch
postcss-preset-env (source) ^11.6.1 → ^11.6.2 age confidence devDependencies patch
preact (source) ^11.0.1 → ^11.1.1 age confidence devDependencies minor
preact (source) ^11.0.1 → ^11.1.1 age confidence dependencies minor
preact (source) ^11.0.2 → ^11.1.1 age confidence dependencies minor
preact-render-to-string ^6.8.0 → ^6.8.2 age confidence dependencies patch
prettier (source) ^3.9.9 → ^3.9.10 age confidence devDependencies patch
prettier-plugin-astro ^1.1.1 → ^1.1.2 age confidence dependencies patch
prettier-plugin-astro ^1.1.0 → ^1.1.2 age confidence devDependencies patch
react (source) ^19.3.0 → ^19.3.1 age confidence dependencies patch
react (source) ^19.3.0 → ^19.3.1 age confidence devDependencies patch
react (source) 19.3.0 → 19.3.1 age confidence dependencies patch
react-dom (source) ^19.3.0 → ^19.3.1 age confidence dependencies patch
react-dom (source) ^19.3.0 → ^19.3.1 age confidence devDependencies patch
react-dom (source) 19.3.0 → 19.3.1 age confidence dependencies patch
rolldown (source) ^1.2.13 → ^1.2.16 age confidence dependencies patch
rolldown (source) ^1.2.13 → ^1.2.16 age confidence devDependencies patch
rolldown (source) ^1.2.14 → ^1.2.16 age confidence dependencies patch
sass ^1.105.1 → ^1.107.1 age confidence devDependencies minor
sass ^1.105.1 → ^1.107.1 age confidence dependencies minor
satteri ^0.10.5 → ^0.11.6 age confidence dependencies minor
satteri ^0.10.5 → ^0.11.6 age confidence devDependencies minor
solid-js (source) ^1.9.17 → ^1.9.18 age confidence devDependencies patch
solid-js (source) ^1.9.17 → ^1.9.18 age confidence dependencies patch
svelte (source) ^5.57.2 → ^5.57.3 age confidence dependencies patch
svelte (source) ^5.57.2 → ^5.57.3 age confidence devDependencies patch
svelte2tsx (source) ^0.7.61 → ^0.7.62 age confidence dependencies patch 0.7.63
tinyps ^0.5.0 → ^0.5.1 age confidence dependencies patch
turbo (source) ^2.11.7 → ^2.11.10 age confidence devDependencies patch
typescript-eslint (source) ^8.71.0 → ^8.72.1 age confidence devDependencies minor
unist-util-visit ^5.1.0 → ^5.2.0 age confidence dependencies minor
unist-util-visit ^5.1.0 → ^5.2.0 age confidence devDependencies minor
unist-util-visit-parents ^6.0.2 → ^6.1.0 age confidence dependencies minor
unstorage ^1.17.5 → ^1.17.6 age confidence dependencies patch
vite (source) ^8.3.4 → ^8.3.5 age confidence dependencies patch
vite (source) ^8.3.4 → ^8.3.5 age confidence devDependencies patch
vite-plugin-solid ^2.11.14 → ^2.11.15 age confidence dependencies patch
vitest (source) ^5.0.4 → ^5.0.5 age confidence dependencies patch 5.1.0
vscode-languageserver-protocol (source) ^3.18.4 → ^3.18.5 age confidence devDependencies patch
vscode-languageserver-textdocument (source) ^1.0.15 → ^1.0.16 age confidence dependencies patch
vscode-languageserver-textdocument (source) ^1.0.15 → ^1.0.16 age confidence devDependencies patch
vue (source) ^3.5.43 → ^3.5.44 age confidence dependencies patch
vue (source) ^3.5.43 → ^3.5.44 age confidence devDependencies patch
wrangler (source) ^4.149.0 → ^4.156.0 age confidence devDependencies minor 4.157.0 (+2)
wrangler (source) ^4.149.0 → ^4.156.0 age confidence dependencies minor 4.157.0 (+2)
zizmorcore/zizmor-action v0.6.4 → v0.8.0 age confidence action minor v0.8.1
zod (source) ^4.6.6 → ^4.6.7 age confidence dependencies patch

Release Notes

withastro/compiler-rs (@​astrojs/astro2tsx)

v0.1.3

Compare Source

Patch Changes
  • 266acf4: Fixes an issue where processing instructions weren't correctly parsed, resulting in an error. Now the following code is correctly transformed:

    <?xml version="1.0" encoding="UTF-8"?>
    <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 10 10" {...Astro.props}>
    	<circle cx="5" cy="5" r="4" />
    </svg>
  • 089b077: Updates Astro’s oxc fork to the latest commit

withastro/compiler-rs (@​astrojs/compiler-rs)

v0.5.2

Compare Source

Patch Changes
withastro/astro (@​astrojs/language-server)

v2.17.3

Compare Source

Patch Changes
babel/babel (@​babel/core)

v8.0.10

Compare Source

🐛 Bug Fix
🏠 Internal
  • babel-build-external-helpers, babel-core, babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-class-properties, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-regenerator, babel-runtime-corejs3, babel-runtime
🏃‍♀️ Performance
🔬 Output optimization

v8.0.9

Compare Source

v8.0.9 (2026-10-23)

This release contains no changes. It is needed only to update the repo (which is based on @babel/core's last release) in Node.js's CITGM.

cloudflare/workers-sdk (@​cloudflare/vite-plugin)

v1.66.0

Compare Source

Minor Changes
  • #​16539 046db08 Thanks @​petebacondarwin! - Update the development registry to use the canonical Cloudflare path

    Upgrade Miniflare to 5.20261023.1-beta and Wrangler to 4.154.0. Vite plugin v1 now uses CLOUDFLARE_DEV_REGISTRY_PATH or <Cloudflare config directory>/dev-registry/v5 for Worker discovery. MINIFLARE_REGISTRY_PATH is no longer read. When mixing Vite and Wrangler development sessions, set the same CLOUDFLARE_DEV_REGISTRY_PATH for both because Wrangler retains its legacy default.

  • #​16407 9ec1101 Thanks @​petebacondarwin! - Support remote Hyperdrive bindings in Vite plugin v1 development and preview

    Set remote: true on a Hyperdrive binding in wrangler.jsonc to connect to its deployed configuration without a local database connection string. The retained remote proxy exposes the binding's connection string and socket streams, and remote session cleanup preserves startup errors and shares one disposal attempt.

Patch Changes
  • #​16542 ef573d4 Thanks @​petebacondarwin! - Preserve machine-readable error properties from remote bindings

    Enable enhanced error serialization on the remote proxy Worker used by Vite plugin v1. Combined with Miniflare 5.20261023.1-beta, remote binding errors retain properties such as code and numericCode so Worker code can handle them without parsing error messages.

  • #​16480 ccaa34a Thanks @​petebacondarwin! - Prevent malformed token-exchange responses from crashing remote binding startup

    Update the Undici dependency bundled from the retained remote-bindings package to 7.30.1. Responses with excessive content encodings now reject without a later unhandled stream error when the server closes the connection early.

  • #​16502 6f2eda1 Thanks @​petebacondarwin! - Update the retained asset configuration validator to Zod 4.6.6

    The Vite plugin validates _headers and _redirects through its private workers-shared package. Update that bundled copy to address excessive memory consumption when validating oversized collections.

  • #​16444 79678c4 Thanks @​petebacondarwin! - Update Vite plugin v1 to the October 23 Workers runtime

    Use Miniflare 5.20261023.0-beta and the matching Wrangler release for local development and preview. Align bundled helpers and Workers types with this runtime, and use 2026-10-23 as the fallback compatibility date when none is configured. The runtime and helper updates also prevent malformed HTTP responses with excessive content encodings from causing unhandled stream errors. The published helpers also update their bundled Zod validator a

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

withastro/starlight

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

Releases

@astrojs/starlight@0.42.9

Patch Changes

  • #4218 effea21 Thanks @delucis! - Reduces install size by ~400 KB by switching the YAML parser used internally for projects using Astro 7.3.6 or later

  • #4316 8679b1c Thanks @clean99! - Fixes localized routes and language switcher links for pages in directories named like Object.prototype properties, such as constructor.

  • #4341 e1ac1b4 Thanks @delucis! - Prevents tables overflowing and clipping when printing a page

withastro/astro

Which issue does this PR close?

Fixes #18606

Rationale for this change

With security.csp enabled, Astro adds the <meta http-equiv="content-security-policy"> element using a placeholder emitted inside renderHead() at the end of <head>. A <meta> CSP policy only applies to content parsed after it per the W3C CSP specification. As a result, scripts declared in <head> (e.g. is:inline scripts, analytics snippets, and injected scripts) run outside the policy and are not covered.

What changes are included in this PR?

  • In packages/astro/src/runtime/server/render/page.ts:
    • Updated replaceCspMetaPlaceholder() to remove the placeholder from the tail of <head> and insert the rendered CSP <meta> tag at the start of <head>.
    • Places the tag immediately after <meta ... charset=...> so character encoding declarations stay within the first 1024 bytes of the document (HTML spec compliant). If no <meta charset> is found, places it right after the <head> opening tag.
    • If no <head> tag is present, falls back to replacing the placeholder in-place.
  • In packages/astro/test/units/csp/rendering.test.ts:
    • Added unit test verifying that the CSP <meta> is placed after <meta charset> and before head scripts in non-streaming renders.
    • Added unit test verifying that the CSP <meta> is placed at the start of <head> when <meta charset> is absent.
  • Added changeset (astro: patch).

Are these changes tested?

Yes:

  • Unit tests: Added 2 new tests in packages/astro/test/units/csp/rendering.test.ts (all 30/30 CSP rendering tests passing, all 84/84 CSP tests passing).
  • Type checking: pnpm run test:types passed with 0 errors.
  • Formatting: pnpm biome check passed with 0 errors.
withastro/astro

Part of the composable Vite plugins RFC. Fourth PR of the stack: framework islands in a plain Vite project.

Changes

  • Adds @astrojs/react-renderer, @astrojs/preact-renderer, @astrojs/solid-js-renderer, @astrojs/svelte-renderer and @astrojs/vue-renderer under packages/renderers/. Each exports its renderer as plain data, for astro({ renderers: [react()] }) next to the framework's own Vite plugin, and has no dependency on astro, so a Vite project doesn't install the CLI. The renderer code is moved (not copied) from the integrations, in a renames-only commit.
  • @astrojs/react, @astrojs/preact, @astrojs/solid-js, @astrojs/svelte and @astrojs/vue depend on their renderer package and register it alongside the framework's Vite plugin. Their public paths (./server.js, ./client.js, ./container-renderer, …) re-export the renderer package, so options and output are unchanged.
  • reexportRenderer() in @astrojs/internal-helpers/renderer points a renderer's module ids at the integration's re-exports, since an Astro project depends on the integration and may not be able to resolve the renderer package (pnpm doesn't hoist it).
  • Adds examples/vite-plugin-astro-hono: a Hono app that renders an Astro component with a React island using renderToResponse().

Testing

  • A frameworks fixture with an island per framework, server-rendered and hydrated in dev and in a build.
  • Renderer tests in each renderer package, moved from the integrations; the standalone fixture uses react().
  • The existing integration and astro framework tests cover the integrations.

Docs

withastro/astro

Part of the composable Vite plugins RFC. Third PR of the stack: Astro components rendered from any server in a plain Vite project.

Changes

  • astro() works without the Astro CLI: add it to a Vite config, import .astro files from server code, and render them with renderToString() or renderToResponse() from @astrojs/runtime.
  • Styles, scripts and islands are collected per component tree: from the module graph in dev, and in a build from the server environments, which decide the client build entries. The rendered HTML links to the built assets.
  • Compiled components register the plugin's config with the runtime (virtual:astro:render-setup), so the render functions need no manifest. createRenderer() renders components without Vite; rendering before any compiled component is loaded throws RenderNotConfigured.
  • Renderers are plain data with declarative fields (options, optimizeDeps, dedupe, noExternal, devHeadScript, appEntrypoint) that astro() applies; the framework's own Vite plugin compiles its files.
  • Drops the srcDir option of astro(). A root-relative <script src> now errors only when it points to a file in publicDir, so project files outside src/ are bundled.

Testing

  • vite-plugin-astro tests for options, the plugin API and the CLI argument, rendering in dev (styles, islands, style HMR, markup reloads) and in a build (linked stylesheets, client chunks), and the public <script src> check, with a standalone fixture.
  • runtime tests for renderToString, renderToResponse and createRenderer.

Docs

  • A guide for using Astro components in a Vite project is drafted in withastro/docs (docs/vite-plugin-astro).
withastro/astro

Part of the composable Vite plugins RFC. Second PR of the stack: makes the moved code work where it now lives, with no behavior change.

Changes

  • Adds the @astrojs/runtime and @astrojs/vite-plugin-astro packages (manifests, tsconfigs, READMEs) around the moved code, rewrites imports, and narrows the moved files' config types (CompileConfig instead of AstroSettings).
  • astro(options, cli) from @astrojs/vite-plugin-astro serves the compile, renderer, script, head and HMR plugins. createVite() calls it once; plugins only the CLI uses stay in astro.
  • The astro/* paths of moved modules stay as re-exports, and the Astro config schema is built from the plugin's option schemas, so config validation and defaults are unchanged.
  • Modules that other packages import live under src/internal/ and are exported as @astrojs/runtime/_internal/* and @astrojs/vite-plugin-astro/_internal/* (mapped to dist/internal/*). These are for use within the monorepo only, with no stability guarantees.

Testing

  • No new tests: behavior is unchanged, and the existing astro unit and integration suites cover it.

Docs

  • No docs update needed: nothing user-facing changes.
withastro/astro

Part of the composable Vite plugins RFC. First PR of a stack: this one only moves files.

Changes

  • Moves Astro's render runtime to packages/runtime (server rendering, client directive scripts, JSX and compiler runtimes, head propagation, errors and error data, encryption, view transitions) and the .astro compiler and syntax-layer Vite plugins to packages/vite-plugin-astro.
  • Pure git mv: 92 renames, no content changes (git diff -M100% --summary shows only renames). The old paths are removed here and come back as re-exports in the next PR.
  • Does not build on its own; the next PR wires the moved code up.

Testing

  • None in this PR: it only moves files. The next PR is the first one that builds and runs the existing suites.

Docs

  • No docs change for the move itself. The docs repo's error reference script reads errors-data.ts from its old path, so the Smoke job fails until that script is updated.
withastro/astro

Fixes #18568

attachDataStoreInvalidation always called invalidateDataStore with notifyClient: true. In astro dev, the initial content-layer sync writes the data store before the server is listening. Vite buffers that full-reload and delivers it right after the first client connected, so the first page loads twice on a fresh start.

dev() now passes a shouldNotifyClient callback that returns false while the initial sync runs. Server-side invalidation still happens. sync() awaits waitUntilSaveComplete(), so the startup write finishes before the flag flips. Writes after startup still reload, including ones Vite buffers for a temporarily disconnected browser. This mirrors buildStart, which already skips the client notify (#17286).

Test plan

  • Unit: a write during initial sync invalidates the server but sends no client full-reload. A later write does reload.
  • Existing invalidation, watcher-echo and prerender tests still pass
withastro/starlight

Description

  • Closes #4336
  • <site-search> (Pagefind) and <sl-doc-search> (@astrojs/starlight-docsearch) only initialized in a DOMContentLoaded listener, so if their script ran after that event, search never set up. The listener was left over from when Pagefind loaded via an inline script; module scripts already run after parsing, so both components now initialize directly in their constructors.
  • Starlight's default output is unaffected in practice: its module scripts run before DOMContentLoaded, and Pagefind setup still waits for requestIdleCallback. This matters when page scripts are added dynamically, for example on a static site using a CSP with 'strict-dynamic' and no nonces (see withastro/astro#18607).

Important

The DocSearch change isn't tested in a browser because it requires an Algolia setup (which I don't have). The Pagefind change is verified in the reproduction.

withastro/astro

Changes

  • Negation patterns like !_docs now correctly exclude files inside that folder during dev server reloads, matching the behavior of the initial sync via tinyglobby. Previously, the watcher's picomatch ignore check only tested a file's own path, so _docs/x.md wasn't caught by !_docs, causing excluded files to be added to the collection on edit.
  • Each negation is now passed to picomatch's ignore list both as written and with /** appended, so a negation that matches a folder also excludes all files inside it.

Testing

  • Added a unit test in packages/astro/test/units/content-layer/glob-loader.test.ts covering the watcher filter with folder-level negation patterns (!_docs, !_doc*, !**/_docs). The test fails before the fix and passes after.

Docs

  • No docs update needed; this restores already-documented behavior for negation patterns in the glob loader.

Closes #18590

withastro/astro

Changes

  • envField.number() parses the value with Number.parseFloat(), which stops at the first character that isn't part of a number. So abc is rejected, but 8080abc, 10px or 1,5 pass validation as 8080, 10 and 1. The last one is easy to hit with a decimal comma, and the wrong value is used silently.
  • The validator now uses Number(), which only accepts the whole string as a number, and rejects blank values first, since Number('') is 0. Valid values such as 42, 4.5, -1 or 1e3 parse the same as before. (Number() also reads 0x10 as 16, where parseFloat() gave 0.)
  • Changeset added (astro patch).

Testing

Added a case to packages/astro/test/units/env/env-validators.test.ts that checks 8080abc, 1,5, 10px, an empty string and a blank string are all rejected with a type error. It fails on main (8080abc validates as ok) and passes with the fix. The rest of test/units/env/ and test/env-secret.test.ts / test/env-public.test.ts still pass.

Docs

No docs change. The docs don't describe the lenient parsing, and invalid numbers are already reported as a type error.

I used Claude Code to write this change.

withastro/astro

Changes

  • Group all minor and patch dependency updates into one Renovate PR while keeping major updates separate (see current jobs list at https://developer.mend.io/github/withastro/astro, there are dozens entries). This reduces routine PR volume and makes dependency reviews easier to manage.
  • Made with AI.

Testing

N/A

Docs

N/A

withastro/astro

Changes

  • astro check now flushes all buffered stdout/stderr output before the process exits. Previously, process.exit() was called synchronously after check() resolved, which silently dropped any data the pipe reader hadn't consumed yet — causing truncated output and a missing Result summary in CI wrappers reading from a slow pipe.
  • A new flushAndExit(code) helper in packages/astro/src/cli/flush-and-exit.ts writes an empty chunk with a callback to each stream and defers process.exit(code) until both callbacks fire. A companion ignoreEpipe() helper registers a no-op 'error' listener on stdout and stderr before check() runs, so early-closing readers (e.g. | head) exit cleanly instead of crashing with an unhandled EPIPE error.

Testing

  • packages/astro/test/units/cli/check.test.ts was added, covering the full-flush path (all bytes delivered to a slow reader), correct exit codes for error and no-error projects, and clean exit when the reader closes early.

Docs

  • No docs update needed; this is an internal CLI reliability fix with no user-facing API change.

Closes #18600

withastro/astro

Changes

  • The two failing font E2E tests hard-coded roboto@latest URLs; the Fontsource API now returns versioned URLs (e.g. roboto@5.3.0/...), causing both URL assertions and the font file IDs hashed from those URLs to no longer match.
  • Adds a getFontsourceFile() helper in the test file that locates each remote Roboto file by ID prefix and validates its URL against a roboto@[^/]+/<file> pattern, making assertions version-agnostic without relaxing any other checks (family hashes, unicode ranges, fallback metrics).

Testing

  • Updated the two previously failing tests in packages/astro/test/units/assets/fonts/e2e.test.ts to use the new helper instead of hard-coded @latest URLs and file IDs, covering version-independent URL matching.

Docs

  • No docs update needed; this is a test-only change with no user-facing behavior impact.

Closes #18598

withastro/starlight

Description

  • Closes #4331
  • When the X or Twitter link in the social config ends with a slash, for example https://x.com/astrodotbuild/, Starlight renders <meta name="twitter:site" content="@astrodotbuild/">, which is not a valid handle.
  • This PR strips both the leading and trailing slashes from the link pathname, so the tag is @astrodotbuild with or without the slash.
  • Adds a unit test with a trailing-slash x.com social link, and a changeset.
  • No visual change.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection metadata).

Changes

  • MDX entries and deferRender Markdown entries are compiled as modules after sync, so sync writes .astro/collection-files.json, mapping their files to their collection. A new astro:collection-files Vite plugin exposes the lookup through its api, used by @astrojs/mdx and Astro's Markdown plugin.
  • A file loaded by more than one collection is compiled once for all of them, so its collection is left undefined.
  • COLLECTION_FILES_PLUGIN_NAME and CollectionFilesApi live in @astrojs/internal-helpers/collections, shared by astro and @astrojs/mdx. The MDX plugin looks the collection up by file: entries and direct imports of a file share its compiled module.
  • In development, the map is also written after loader changes outside syncs, and modules whose collection changes are invalidated and compiled again.

Testing

  • Unit test for the file to collection map, including files shared by collections.
  • mdx-collection-metadata.test.ts builds MDX and deferred Markdown entries and a shared file, and checks in dev that editing descriptors recompiles the MDX page.

Docs

  • No docs yet, see the first PR of the stack.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection metadata).

Changes

  • Markdown plugins receive the metadata of the collection being rendered as file.data.astro.collection (ctx.data.astro.collection in Sätteri), for entries rendered by glob() and by renderMarkdown() in custom loaders.
  • Moves AnyCollectionMetadata and JSONValue to a new @astrojs/internal-helpers/collections export, re-exported by astro, so the Markdown processors don't depend on astro.
  • Adds an optional collection to MarkdownRenderOptions, an optional fourth argument to MdxRenderer.process(), and an optional second argument to ContentEntryRenderFunction. Processors and entry types that ignore them keep working.

Testing

  • remark and Sätteri collection.test.ts cover Markdown and MDX processors.
  • The astro collection-metadata fixture renders glob() and renderMarkdown() entries through a remark plugin, with the flag on and off.

Docs

  • No docs yet, see the first PR of the stack.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection metadata).

Changes

  • Adds the astro:collections:resolved integration hook, called with the metadata of the build-time collections before any loader runs, and again in development only when the content config changes. Requires experimental.collectionMetadata.
  • Live collections aren't included, because live.config.ts isn't loaded during sync.
  • The hook is called during the content sync, after astro:config:done and before any loader runs. In astro build, it runs on every build before astro:build:start, so before the build's Vite pipeline loads any module, except the modules content.config.ts imports. In astro dev, it runs after astro:server:setup and before astro:server:start. The hook's JSDoc documents this order.

Testing

  • Unit tests check the hook is called once per content config with the metadata, and not called when the flag is off.
  • collection-metadata.test.ts checks the order in a build: astro:config:done, astro:collections:resolved, astro:build:start, then the first module the build's Vite pipeline loads.

Docs

  • No docs yet, see the first PR of the stack.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection metadata).

Changes

  • Adds the experimental.collectionMetadata flag and getCollectionsMetadata() in astro:content: every build-time then live collection, as { name, type, loader: { name }, descriptors }, without loading entries. It throws CollectionMetadataNotEnabled when the flag is off.
  • Adds descriptors on loaders (build-time and live), defineCollection() and defineLiveCollection(). The collection's values override the loader's. They are ignored when the flag is off, so libraries can set them on their loaders unconditionally.
  • With the flag off, descriptors are ignored and not checked at all, so a library can set them whether or not its users enable the flag. A dedicated fixture checks that a descriptors value that isn't an object doesn't fail the content config without the flag.
  • Loader and LiveLoader take a TDescriptors generic, and defineCollection()/defineLiveCollection() keep the literal types of their descriptors. The generated CollectionMetadata type is a union with one member per collection, whose descriptors merge the loader's and the config's types, so editors autocomplete them. An index signature lets code read a key on every collection, including those that don't set it.
  • Adds the CollectionMetadataWith<D, T> type in astro:content, which narrows CollectionMetadata to the collections with the descriptors D, and optionally the type T, for use in type guards.
  • Names the general shape AnyCollectionMetadata in astro, for code outside a project, like integrations and Markdown plugins, which can't see its generated types. CollectionMetadata is only the generated type of astro:content, so the two no longer share a name.
  • Build-time metadata is written at the start of each sync to .astro/collections-metadata.json and served by an astro:collections-metadata module; live metadata is computed at runtime from live.config.ts.

Testing

  • collection-metadata.test.ts (unit) covers descriptor merging, inline loaders, writing and removing the file, and the generated module.
  • collection-metadata.test.ts (integration) builds a fixture with build-time, inline and live collections, checks lookup by descriptor, that results are copies, and the flag-off error.
  • test/types/collection-descriptors.ts checks that ExtractCollectionMetadata, which CollectionMetadataWith uses, narrows by descriptors and by type.

Docs

  • No docs yet: docs will come with the experimental flag page.
withastro/astro

Changes

  • Implements roadmap#1458: on a cache miss, the memory cache provider (memoryCache()) returns the response as it renders and stores a copy when the body completes, instead of reading the whole body before the first byte. The stored entry is unchanged; a body that fails mid-stream is logged and not stored.
  • The store is passed to waitUntil when the adapter provides one, so serverless runtimes keep it alive after the response is sent. Without waitUntil (e.g. Node) it completes on its own.
  • As on an uncached page, a render error once the page has started streaming ends the response instead of rendering the 500 page.

Testing

  • Why existing tests changed: a miss is now stored after onRequest returns, so a test that checks the cache straight after a miss races the store. An expected HIT fails, and an expected MISS (different host, Set-Cookie) passes whether or not the entry was keyed correctly. Tests now record the store through a waitUntil they pass in and await it before those checks, using a new test/units/cache/test-helpers.ts; the helpers fail after 1s instead of hanging. app-cache passes the hook to app.render, and the test adapter forwards it so cache-memory-query can too; that file's helper also fails if no store was recorded.
  • New memory-provider streaming miss tests fake a slow render with a body that sends <head> and holds </html> until the test releases it:
    • the miss response returns and streams <head> while the body is held, then the full page is stored, with and without waitUntil; on a provider that waits for the body, onRequest fails a 1s guard instead of hanging;
    • a visitor who cancels mid-stream still leaves the full page stored;
    • a body that errors mid-stream logs one warning and stores nothing, with and without waitUntil; without it, a store that didn't catch its own failure would be an unhandled rejection.

Docs

No docs update needed: there is no API or configuration change.

🤖 Generated with Claude Code

withastro/astro

Changes

  • astro check now exits with code 1 when @astrojs/check or typescript cannot be loaded (e.g. in CI where packages can't be auto-installed). Previously, the missing-packages branch did a bare return;, which resolved to undefined and caused the CLI to call process.exit(0), silently passing CI even though no type-checking ran.
  • Changed return; to return true; in packages/astro/src/cli/check/index.ts, matching the existing behavior of the TypeScript 7 incompatibility branch added in #18053.

Testing

  • Adds a unit test in packages/astro/test/units/cli/check.test.ts covering the case where getPackage() returns undefined for @astrojs/check or typescript, asserting that check() returns true (triggering exit code 1).

Docs

  • No docs update needed; this is a bug fix restoring the expected exit-code contract with no API or configuration changes.

Closes #18588

withastro/astro

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

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@astrojs/cloudflare@15.0.0-beta.5

Patch Changes

  • #18553 bf39bf6 Thanks @petebacondarwin! - Updates the Cloudflare adapter to use the Vite plugin's full configuration API while preserving user-defined Worker settings, bindings, and Containers
withastro/starlight

Description

This PR is a follow-up to #4175:

  • Adds the SHA for the #4175 commit to .git-blame-ignore-revs so it doesn’t show in git blame.
  • Removes two files from our .prettierignore file as these can now be successfully formatted with the updated plugin. (@HiDeoo suggested this in a review but I forgot to apply it there.)
  • Runs formatting for those two files.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection storage).

Changes

  • Adds createStorageDriverTests() at astro/content/storage-driver-tests: the tests a driver must pass, independent of any test runner.

Testing

  • Runs the suite against the in-memory test driver, and checks that it fails for a driver that ignores the snapshot ID.
  • The SQLite driver tests use the suite instead of their own copies.
  • The suite also checks that writing a snapshot again in development replaces its entries, and, when the driver implements them, listSnapshots() and deleteSnapshot().

Docs

  • No docs yet. The changesets are in #18632, the last PR of the stack.
withastro/astro

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

Releases

astro@7.4.6

Patch Changes

  • #18565 cd09986 Thanks @praveen-kumary! - Avoids attributing client-only components or scripts to unrelated pages importing astro:i18n by bounding top-level page graph traversal at virtual page entries

  • #18608 babd96d Thanks @umeraamir69! - Fixes an extra page reload on the first page load after starting astro dev without an existing .astro directory

  • #18589 402c0fa Thanks @astro-factory! - Fixes astro check exiting with code 0 when @astrojs/check or typescript is not installed. The command now exits with code 1 so CI fails instead of silently skipping type checking.

  • #18503 54fcdd5 Thanks @SwastikTripathi! - Preserves the last-modified date of cached font files and unchanged public files when copying them into the build output. Public-file timestamp preservation respects the resolved public-directory configuration, follows source symlinks, and avoids backdating files overwritten by build plugins.

  • #18605 76cd239 Thanks @astro-factory! - Fixes the glob() loader adding files from a folder excluded with a negation pattern such as !_docs when they change during astro dev

  • #18432 ed60d82 Thanks @alexmv! - Improves the MissingSharp error to include the reason Sharp failed to load, such as its prebuilt binaries not supporting the current CPU

  • #18474 59543c3 Thanks @miottid! - Fixes i18n fallback for on-demand rendered pages. A locale-prefixed request for a page that only exists in the fallback locale (for example /de/about with fallback: { de: 'en' }) was answered with status 302 and no Location header. Such requests are now rewritten or redirected to the fallback locale according to i18n.routing.fallbackType, including encoded paths and sites with a configured base. Query strings are preserved, and explicit page statuses and redirects are left unchanged.

  • #18541 cfa2d2b Thanks @ump45nose! - Fixes matchAllRoutes to consider fallbackRoutes, matching matchRoute and the production router. Dev-server i18n fallback requests now resolve to the source route's metadata instead of the 404 route, and SSR-only fallback candidates can fall through the prerender handler.

  • #18602 d856064 Thanks @astro-factory! - Fixes astro check losing the end of its output, including the Result summary, when stdout is piped to a slow reader. When the reader closes the pipe early, for example astro check | head, astro check now exits with code 1 instead of crashing with an EPIPE stack trace.

  • #18574 da0f149 Thanks @astro-factory! - Fixes an unnecessary full page reload in astro dev when a content loader calls store.clear() or store.delete() and the content store has no asset imports

  • #18570 e71c038 Thanks @astro-factory! - Fixes pages using <ClientRouter /> briefly showing the top of the page on reload before jumping back to the previous scroll position. Full reloads now use the browser's native scroll restoration.

  • #18531 f75553b Thanks @praveen-kumary! - Fixes an unhandled TypeError: Cannot convert undefined or null to object when calling route.generate() without arguments on static routes

@astrojs/cloudflare@14.4.5

Patch Changes

  • #18562 9055de2 Thanks @astro-factory! - Fixes the passthrough /_image endpoint returning a 404 instead of 304 Not Modified when the browser revalidates a cached local image with If-None-Match. Revalidation supports weak ETags, tag lists, and wildcard conditions for local and allowed remote images while preserving image-type validation.
  • Updated dependencies []:
    • @astrojs/underscore-redirects@1.0.4

@astrojs/node@11.1.10

Patch Changes

  • #18563 8a92f7c Thanks @astro-factory! - Fixes on-demand routes receiving an empty request body on Node.js 26 when staticHeaders is enabled

@astrojs/react@7.1.3

Patch Changes

  • #18535 b21d724 Thanks @praveen-kumary! - Preserves component-rendered resource links, including stylesheets, preloads, and modulepreloads, in React island output. Automatic React resource hints are also preserved so that authored links are not removed during server rendering.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection storage).

Changes

  • Adds @astrojs/collection-storage-sqlite: sqlite({ url, authTokenEnv }) keeps collections in a local SQLite file or a remote libSQL database such as Turso.
  • Snapshots share two tables. A snapshot is listed in the snapshots table only once committed, so a reader can't open an uncommitted one. Entries are written and read in pages.
  • Implements listSnapshots() and deleteSnapshot(), which deletes a snapshot's entries and row in one transaction. The snapshots table records dev, and opening a writer clears the snapshot's entries, so a dev server can write its snapshot again.
  • The auth token is read with getSecret() from astro:env/server, from the variable named by authTokenEnv, never passed as an option. It can come from a .env file at build time, and is never written into the build.
  • @libsql/client is a peer dependency: it must be a direct dependency of the project, so the server build keeps it external and libSQL can load its native binding.
  • sqlite() points at the driver file with a file URL. The package doesn't ship a web version: the driver runs in Node only, and runtimes such as Cloudflare Workers are expected to use their own driver, e.g. a D1 driver shipped by the adapter.

Testing

  • driver.test.ts covers the descriptor, uncommitted snapshots and config errors.
  • fixture.test.ts builds a site whose collection is stored in SQLite.

Docs

  • The package has a README. Docs will come with the experimental flag page.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection storage).

Changes

  • In astro dev, collections with storage are read through their driver too, so driver problems show up during development.
  • Development has a single snapshot: every dev server, in every session, writes the snapshot dev, again after each sync and each store write that loaders make outside of syncs. createSnapshotId() isn't called, as it may return the ID of a deployment. Writing .astro/collection-storage.json invalidates the bundled drivers module, so readers reopen.
  • Dev restarts sync through syncInternal(), which passes dev: true for command: 'dev', so a restart writes the dev snapshot too.

Testing

  • Adds a dev server suite to collection-storage.test.ts: it reads a stored entry, edits its file, and checks that the page updates from the same snapshot.
  • collection-storage-sync.test.ts checks that dev servers write to the snapshot dev, with dev: true, without calling createSnapshotId().

Docs

  • No docs yet, see the first PR of the stack.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection storage).

Changes

  • A new astro:collection-storage module bundles the drivers and the snapshot each one must read. getCollection() and getEntry() read those collections through a reader per driver, created on first use.
  • getEntry() and getEntries() accept { content: false }, and getCollection() accepts it in a query object, getCollection({ name, filter?, content? }), so the filter doesn't have to be undefined. Entries are returned without body and rendered, with matching types. It works for bundled collections too. render() throws RenderEntryWithoutContentError for those entries.
  • The content option requires experimental.collectionStorageDrivers: with the flag off, the read functions throw ContentOptionNotEnabled, and the generated types only accept content when astro sync sees the flag on.
  • Trims the internal DataStoreSource interface to the three methods the runtime uses.

Testing

  • collection-storage-runtime.test.ts covers the stored, in-memory and composite sources, and the generated module.
  • collection-storage.test.ts builds a fixture with a JSON file driver: prerendered pages, an on-demand endpoint using every read function, no stored entries in the server bundle, and a new snapshot per build.
  • The fixture also stores a collection with deferRender entries, sharing the driver of docs, and an image field, and a second fixture checks the error and the types with the flag off.

Docs

  • No docs yet, see the first PR of the stack.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection storage).

Changes

  • At the end of each sync, collections with storage are written to a new snapshot of their driver and committed. Collections sharing a descriptor share a driver and a snapshot. Loaders are unchanged: they still write to the in-memory store.
  • astro sync and astro check write no snapshot (writesStoredCollections: false): nothing would read it, as builds and dev servers write their own. They also don't load drivers, so generating types never connects to a remote database.
  • The snapshots are recorded in .astro/collection-storage.json, and those collections are left out of the bundled data store module. They stay in the cached data store, so loaders keep their incremental state.
  • Drivers are imported once per descriptor, through the Vite runner that loads the content config (createViteDriverLoader()), wired into sync, dev and dev restarts. Entrypoints resolve from the project root, and drivers can import virtual modules such as astro:env/server, as they do once bundled with the server. Entrypoints are normalized by normalizeEntrypoint(), moved out of the logger along with importEntrypoint(), which stays the default import function. Invalid entrypoints throw InvalidCollectionStorageDriver.

Testing

  • Adds an in-memory test driver to the content layer test helpers.
  • collection-storage-sync.test.ts covers snapshot grouping and IDs, driver loading errors, the content layer writing and removing the record, and the exclusion from single-file and chunked bundled stores. It also checks that a content layer that doesn't write stored collections loads no driver.

Docs

  • No docs yet, see the first PR of the stack.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection storage).

Changes

  • Adds the public CollectionStorageDriver contract: an optional createSnapshotId(), openWriter({ snapshot, dev }) with write()/commit(), openReader({ snapshot }) with get()/entries(), and optional listSnapshots() and deleteSnapshot().
  • A dev server writes a single snapshot, again after each change: opening a writer on a committed snapshot replaces its entries on commit. dev tells drivers which snapshots dev servers wrote, and listSnapshots() returns it as CollectionStorageSnapshot.
  • Adds the stored entry format: Astro serializes an entry into a metadata string and an optional content string (body and rendered), so drivers can skip content.

Testing

  • collection-storage-entries.test.ts covers the round trip and the metadata/content split.

Docs

  • No docs yet, see the first PR of the stack.
withastro/astro

Part of the implementation of the enhanced content collections RFC (collection storage).

Changes

  • Adds the experimental.collectionStorageDrivers flag and a storage option on build-time collections, which takes a storage descriptor ({ entrypoint, config }).
  • Loading the content config throws CollectionStorageDriversNotEnabled when a collection sets storage without the flag.

Testing

  • collection-storage-config.test.ts covers parsing and the flag check.
  • define-collection-storage.ts type-checks the storage option.

Docs

  • Not yet: the feature is not usable until the rest of the stack lands. Docs will come with the experimental flag page.
withastro/astro

Changes

  • writeAssetImports() in mutable-data-store.ts no longer writes a second, differently-formatted empty map when the asset set is empty. Previously the empty-map branch wrote export default new Map(); and fell through, causing a second write with different whitespace. The watcher then saw .astro/content-assets.mjs change and sent full-reload, which on the Cloudflare adapter cleared the module runner mid-request and produced React hook errors.
  • The fix adds this.#assetsDirty = false; return; after the empty-branch write, matching the existing pattern in writeModuleImports().

Testing

  • Added a unit test in packages/astro/test/units/content-collections/mutable-data-store.test.ts covering store.clear() when there are no asset imports, asserting that writeAssetImports() writes only once and that the result is the canonical empty-map string.

Docs

  • No docs update needed; this is an internal dev-server correctness fix with no user-facing API change.

Closes #18573

withastro/astro

Changes

  • <ClientRouter /> now sets history.scrollRestoration = 'auto' in a pagehide listener so a full reload lets the browser restore scroll position natively, before any JS runs. Previously the router kept 'manual' forever, causing the page to paint at the top and then jump to the saved position after the module script executed.
  • A pageshow listener (bfcache restores) and the module init reset it back to 'manual', so the router retains full control of scroll for its own client-side navigations.

Testing

  • Added an e2e regression test in packages/astro/e2e/view-transitions.test.ts ("Reload leaves scroll restoration to the browser") that scrolls a page with <ClientRouter />, triggers a reload, and asserts that scrollRestoration is 'auto' at the point of unload, covering the new pagehide listener.

Docs

  • No docs update needed; this is an internal implementation fix with no API or configuration surface change.

Closes #18569


Last fetched:  | Scheduled refresh: Every Saturday

See Customizing GitHub Activity Pages to configure your own

Inspired by prs.atinux.com