bun-frontend-deploy-sudo-path

What problem does it solve?

This Skill resolves the common issue where a Bun frontend build completes successfully and outputs files to the dist/ directory, but subsequent sudo cp or sudo rsync deployment commands fail with "No such file or directory" errors, or the dist directory appears empty after deployment, caused by sudo not preserving shell tilde (~) path expansion.

Core Features & Use Cases

• Root Cause Explanation: Clearly identifies why sudo mangles tilde-based paths and how default terminal working directories impact path resolution.
• Correct Deployment Pattern: Provides step-by-step guidance for using absolute paths in sudo commands to reliably copy built frontend assets to target system directories.
• Verification Checklist: Includes post-deployment checks to confirm assets are correctly placed before marking the deployment as successful.
• Use Case: Frontend developers or DevOps engineers deploying Bun-built static sites or single-page applications to web server directories like /var/www/html that require sudo access.

Quick Start

Use this skill to fix sudo path errors when deploying your completed Bun frontend build to a target server directory.