Build failure due to missing sharp dependency in production environment

In Astro projects, the <Image /> component functions correctly during local development without the sharp library installed, as the development server typically defaults to a basic processing method that does not require external binaries.

However, when the astro.config.mjs file explicitly sets the image service to sharp, the production build requires the package to perform asset transformations. If sharp is listed as a devDependencies or is missing entirely, the build process may fail or produce unoptimized assets that differ from the local output.

This discrepancy creates a gap between the permissive local environment and the strict requirements of the production-grade build-time optimization service.

• What are the specific error signals generated when the sharp service is configured but unavailable during astro build?
• Can Astro fallback to a default service if sharp is missing without breaking the build?