Astro Integration
Astro Build Manifest
Expose exactly what Astro generated — pages and assets — using a static, deterministic build manifest.
Last Updated: 01 April 2026
Usage Snapshot
140
Downloads in Last 30 Days
v1.0.1
Latest npm Version
Source: npm registry
Why This Plugin Exists
After a build, teams often need to know which routes were generated and which files Astro actually emitted.
Today, those answers usually require inspecting build logs, browsing output directories, or guessing from production behaviour.
Astro Build Manifest exposes this information safely and deterministically via a static JSON file.
Design Principles
- Static-first design
- Deterministic output
- Public-safe metadata only
- No runtime execution
- No environment or filesystem leakage
What This Plugin Delivers
- Generates a static /build-manifest.json file
- Lists all generated pages
- Lists emitted HTML, CSS, and JS assets
- Normalised route formatting
- Deterministic, cache-safe output
- Zero runtime JavaScript
Installation
npm install astro-build-manifest
The plugin runs during astro build and writes build-manifest.json to the output directory.
FAQs
What does Astro Build Manifest generate?
It generates a static build-manifest.json file listing all pages and public assets produced by Astro during build.
Is this a runtime or server feature?
No. Astro Build Manifest runs only at build time and never executes at runtime.
Is the output safe to expose publicly?
Yes. The manifest includes only public, web-facing paths and no sensitive information.
Implementation FAQs
What problem does Astro Build Manifest solve?
It exposes which pages and assets Astro actually generated, without requiring log inspection or filesystem access.
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.
Project Links
Source code, package distribution, releases, and documentation.
Need Implementation Details?
Read the FAQs for usage patterns, integration caveats, and rollout guidance.