Astro Integration

Astro Build Info

Expose exactly what was built — and when — using a static, machine-readable file.

Last Updated: 01 April 2026

Usage Snapshot

282

Downloads in Last 30 Days

v1.1.0

Latest npm Version

Source: npm registry

Teams often need to know which build is deployed, when it was generated, and which site it belongs to.

These answers are usually hidden in CI logs, guessed from HTML, or leaked via debug endpoints.

Astro Build Info exposes build metadata cleanly and deterministically, without runtime logic or environment leakage.

npm install astro-build-info

The plugin runs during astro build and writes a static build-info.json file to the output directory.

What does Astro Build Info generate?

It generates a static /build-info.json file containing deterministic build metadata.

Is this a health check or status endpoint?

No. Astro Build Info reports build metadata only and makes no runtime claims.

Is the output safe to expose publicly?

Yes. The file contains no secrets, environment variables, or system information.

What question does Astro Build Info answer?

It answers what was built, where it belongs, and when the artefact was generated.

Does Astro Build Info run at runtime?

No. It runs only during astro build and produces static output.

What metadata is included?

Framework name, Astro output mode, configured site URL, and build timestamp.

Does Astro Build Info expose environment or CI details?

No. Environment variables, machine data, and CI metadata are deliberately excluded.

Is the output compatible with CDNs?

Yes. The static file can be cached indefinitely behind any CDN.

What happens if the file cannot be written?

A warning is logged and the build continues safely.

Source code, package distribution, releases, and documentation.

Read the FAQs for usage patterns, integration caveats, and rollout guidance.