node-static-proxy-cloudflare

What problem does it solve?

This Skill eliminates common failures when starting a Node.js static file server with API proxy functionality and a Cloudflare tunnel, including EADDRINUSE errors, connection refused issues, and zombie lingering processes caused by incorrect startup sequencing or poor process management.

Core Features & Use Cases

• Sequential Startup Workflow: Enforces the correct order of operations (kill existing processes → start backend → start static proxy → start Cloudflare tunnel) to prevent port conflicts.
• Process Management Best Practices: Guides proper use of background process handling and log redirection to avoid orphaned processes.
• Troubleshooting & Edge Case Handling: Includes fixes for common errors like Vite config loading issues, custom hostname authentication requirements, and NAT server detection.
• Use Case: When deploying a full-stack web app with a separate backend API, use this Skill to expose the frontend and proxy API calls publicly via Cloudflare Tunnel without running into process or port conflicts.

Quick Start

Use the node-static-proxy-cloudflare skill to start your static proxy server and Cloudflare tunnel in the correct sequence to avoid port conflicts and process errors.