Cannot find module vite error in Astro's build process

Problem Context

The Cannot find module vite error surfaces during astro dev or astro build when the project’s Vite dependency is missing or incompatible with Astro’s required ESM features. Astro 4.x expects Vite 4.x; using an older Vite (3.x or earlier) triggers the failure because the internal @astrojs/vite package attempts to resolve Vite via Node’s module system and cannot locate the expected ESM loader.

Goal

Determine a robust strategy for managing Vite in Astro projects that prevents the module‑resolution error while maintaining flexibility for custom Vite configurations.

Constraints & Uncertainty

• Astro 4.x requires a Vite version that satisfies the ^4.0.0 peer dependency declared by @astrojs/vite.
• Projects that manually pin Vite to an older major version or omit Vite entirely experience the module‑resolution failure.
• There is no formal warning mechanism in Astro to alert users when Vite is missing or mismatched.
• Future Astro releases may shift the required Vite major version, potentially altering the compatibility landscape.

Unresolved Decision

Should Astro treat Vite as a peer dependency that triggers a clear warning when absent or incompatible, or should it bundle a specific Vite version to guarantee compatibility across all projects?

Specific Questions

1. What is the most reliable way to ensure that a compatible Vite version is installed without user error when setting up a new Astro project?
2. Would moving Vite to a peer dependency with an explicit version range improve developer experience, or would it introduce additional friction?
3. How might future Astro releases impact the current Vite compatibility strategy, and what migration path should be planned?