Conversation
This file was missing on main branch causing deploy failures. Added explicit build config for clarity.
Ensure vite.config.js is present for production builds
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix deploy workflow failing with "Could not resolve entry module index.html"
Problem
The
vite.config.jsfile was missing on the main branch, causing the Vite build to fail during deployment. Without the Laravel Viteplugin configuration, Vite doesn't know the entry points.
Solution
vite.config.jsto ensure it's included in the merge to mainAfter merging
After merging this to develop, merge develop to main to ensure
vite.config.jsis present on main for deployments.