Build failure due to missing sharp dependency in production environment

Direct Resolution

The build failure occurs because Astro, when configured to use the sharp image service in astro.config.mjs, requires sharp to be present in the production dependencies (dependencies), not just devDependencies. Local development often uses a fallback that does not mandate this external binary.

Likely Explanation vs. Confirmed Facts

Likely Explanation: The build process attempts to execute sharp binaries during asset optimization, and the absence of the package leads to an execution failure.

Confirmed Fact: Astro does not automatically revert to a default image service if sharp is explicitly selected in the configuration.

Required Steps

1. Ensure sharp is listed under dependencies in your package.json.
2. Reinstall dependencies using your package manager (e.g., npm install or yarn install).
3. Execute astro build to confirm the resolution.

Diagnostic Follow-up

If the build still fails after ensuring sharp is a production dependency, please provide the specific error message output from the astro build command.