Fix build regressions when main repo has build artifacts#5
Open
Fix build regressions when main repo has build artifacts#5
Conversation
- Phase 1: Expand rsync exclusions to exclude all build artifacts (out-build, out-vscode-min, .cache, dist, *.tsbuildinfo, react/out) - Phase 2: Add post-copy cleanup to remove any artifacts that slip through - Phase 3: Add source state verification (warn only, non-blocking) for uncommitted changes and missing package-lock.json - Phase 4: Force clean node_modules before npm install to prevent contamination - Phase 5: Add file integrity check to verify critical files exist after copy - Phase 6: Normalize timestamps to prevent build cache issues All phases tested and validated. This ensures that if main repo runs without issues, builder will also build successfully.
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
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.
All phases tested and validated. This ensures that if main repo runs without issues, builder will also build successfully.