Can the build ship only canonical pages?
We ran the production source as the fixture, generated the static output, then compared every sitemap entry with the intended canonical route set. The question is deliberately narrow: does this repository produce the release contract it claims?
Astro generated the expected static HTML, retained a custom 404, and kept the redirect-only alias and error route out of the generated sitemap. This is a repository-specific publishing result, not a general Astro performance score.
Build first. Inspect the output, not the promise.
The runner executes the pinned Astro build in this repository. It walks the generated HTML files, reads Astro's sitemap index and child sitemap, then checks the complete URL set. A passing run requires the custom 404 file, all intended canonical pages, and zero redirect/error aliases in the sitemap.
corepack pnpm exec astro build- Static output existsPASS
- Custom 404 existsPASS
- Redirect alias excludedPASS
- Error route excludedPASS
- Sitemap matches canonical setPASS
Useful for this release, not a universal benchmark.
- One warm local run on a Windows x64 workstation; this is not a cross-platform performance benchmark.
- The result covers Astro static output for this repository, not SSR, server islands, adapters, or cold dependency installation.
- Elapsed time includes local filesystem and process-start variance and should not be compared across machines.
Clone the public repository, install the pinned dependencies, and run the capture command. The runner and saved JSON are versioned beside the site.
corepack pnpm install --frozen-lockfile
corepack pnpm field-test:astro:capture