What problem does Astro Build Manifest solve?
It exposes which pages and assets Astro actually generated, without requiring log inspection or filesystem access.
Astro & Builds
Astro Build Manifest Plugin FAQs
Clear answers explaining what Astro Build Manifest records — and what it intentionally excludes.
Questions covered
Answers
Which pages are included in the manifest?
All routes Astro generated during the build, normalised with leading and trailing slashes.
Which assets are included?
Public, web-facing files emitted by Astro such as HTML entrypoints and bundled CSS and JavaScript.
What is intentionally excluded?
Public directory files, environment variables, runtime state, absolute filesystem paths, and adapter details.
Does Astro Build Manifest run at runtime?
No. It runs only during astro build and produces static output.
Is the manifest compatible with CDNs?
Yes. The output is static and can be cached indefinitely behind any CDN.
Will additional metadata be added in future versions?
Possibly in v2, with opt-in features such as diffing or public directory inclusion.
Is Astro Build Manifest open source?
Yes. Astro Build Manifest is released under the MIT license.
Want to try it yourself? Astro Build Manifest plugin or Astro Build Info plugin or Astro Status plugin
Need a clear record of what Astro actually built?