withastro/astro - CodSpeed

withastro

astro

Blog Docs Changelog

Performance History

Latest Results

delete: e2e test file

fkatsuhiro:migrate/e2e-to-integration-vite-virtual-modules

3 hours ago

delete: e2e test file

fkatsuhiro:migrate/e2e-to-integration-vite-virtual-modules

3 hours ago

feat: integration test of vite-virtual-module

fkatsuhiro:migrate/e2e-to-integration-vite-virtual-modules

6 hours ago

fix(astro): warn on invalid content collection references After the Zod 4 upgrade, reference() no longer validated that a referenced entry exists, so an invalid reference (e.g. an un-slugified id like "John-Doe" when the glob loader exposes "john-doe") silently passed validation and only failed at render time. Add a post-sync validation pass in the content layer that walks every synced entry, finds reference objects, and warns when a reference points to a missing entry in an otherwise-loaded collection. Closes #17322

xianjianlf2:fix/content-reference-validation-17322

6 hours ago

Fix CSS missing when building from a symlinked directory

lazerg:fix/17319-symlink-css

21 hours ago

Merge branch 'main' into triagebot/fix-17283

triagebot/fix-17283

22 hours ago

Improve rendering performance for pages with many components (#17344) * fix(head-propagation): collect propagated head parts in a single pass The collection loop restarted its scan of the propagator set once per propagator (skipping seen entries) to reach propagators registered during init(). That skip-scan is O(N^2) in set-iteration steps; pages rendering thousands of propagating component instances spend most of their render time in it. A JS Set iterator already visits entries added during iteration, in insertion order, so a single pass has identical traversal order and semantics. Pending slot evaluations are drained before the iterator advances, so nothing can register a propagator after the iterator has completed. Adds regression tests asserting linear iteration and covering the in-loop drain of async slot pre-renders queued by a propagator's init(). * benchmark: add head-propagation scaling pages to rendering-perf Every MDX <Content /> instance registers a head propagator, so these pages put N entries into the set that collectPropagatedHeadParts iterates. Two sizes (1000/2000) make the complexity class visible, not just point cost: linear collection keeps the 2000-page near 2x the 1000-page, while a quadratic rescan of the propagator set pushes the pair toward 4x and more than doubles the 2000-page's absolute cost. The entry must be MDX: plain data-store markdown does not mark the route for propagation (handlePropagation), so its Content instances never enter the propagator set.

main

24 hours ago

Add security-focused tests for default normalizePathname

fetch-state-decodepathname

1 day ago

Latest Branches

refactor(test): migrate vite virtual module tests from e2e to integration#17360

6 hours ago

e1793dd

fkatsuhiro:migrate/e2e-to-integration-vite-virtual-modules

fix(astro): validate content collection references and warn on dangling ids#17359

7 hours ago

e759c93

xianjianlf2:fix/content-reference-validation-17322

Fix CSS missing when building from a symlinked directory#17356

21 hours ago

bb18ffc

lazerg:fix/17319-symlink-css

Home Terms Privacy Docs