Maintenance: Add build artifacts cleanup tooling#231
Open
Conversation
- Add scripts/cleanup-build-artifacts.sh to remove untracked build files - Removes node_modules, .next, dist, and log files from pipeline outputs - Add npm run clean:artifacts command for convenient execution - Addresses directory bloat (agent-factory was 1.9GB, now 1.4MB) - Script is safe - only removes gitignored files, won't affect tracked code - Includes before/after size reporting for transparency
- Fixed Ajv constructor usage (removed .default and invalid 'strict' option) - Resolved npm audit vulnerabilities with npm audit fix - All type checks and tests now passing
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
Addresses directory bloat issues identified in repository review. Provides tooling to clean up large untracked build artifacts that accumulate in pipeline outputs.
Problem
Solution
=======================================
📏 Checking current directory sizes...
Before cleanup:
agent-factory: 1.4M
website-pipeline: 2.1M
claw-pipeline: 560K
miniapp-pipeline: 1.1M
🗑️ Cleaning up build artifacts...
📏 Directory sizes after cleanup:
agent-factory: 1.4M
website-pipeline: 2.1M
claw-pipeline: 560K
miniapp-pipeline: 1.1M
✅ Cleanup complete!
💡 Tip: Add this to your workflow:
npm run clean:artifacts # (if added to package.json)
./scripts/cleanup-build-artifacts.sh
🔒 Note: All cleaned files are already gitignored and won't be committed
🧹 AppFactory Build Artifacts Cleanup
📏 Checking current directory sizes...
Before cleanup:
agent-factory: 1.4M
website-pipeline: 2.1M
claw-pipeline: 560K
miniapp-pipeline: 1.1M
🗑️ Cleaning up build artifacts...
📏 Directory sizes after cleanup:
agent-factory: 1.4M
website-pipeline: 2.1M
claw-pipeline: 560K
miniapp-pipeline: 1.1M
✅ Cleanup complete!
💡 Tip: Add this to your workflow:
npm run clean:artifacts # (if added to package.json)
./scripts/cleanup-build-artifacts.sh
🔒 Note: All cleaned files are already gitignored and won't be committed for convenient execution
Results
After cleanup:
Usage
npm run clean:artifacts # or directly: ./scripts/cleanup-build-artifacts.shThis is a maintenance improvement with no impact on functionality.