What problem does it solve? After a bundler or framework major upgrade (Rsbuild, Next.js, Vite), the dev server may silently change its default host binding to localhost, making it unreachable through the published Docker port. Every CI job that starts the dev container then fails at the start-container step, and the failure looks like a fleet of unrelated broken jobs rather than one binding misconfiguration. ## Core Features & Use Cases - Root-cause identification: Recognizes the signature of a host-binding failure — healthcheck loops timing out, connection refused on the published port, and dev server logs printing only a loopback URL. - Config-level fix: Sets server.host to 0.0.0.0 in the bundler config at the repository root so the Makefile, compose file, and IDE runs all share the same binding. - Verification workflow: Starts the dev container via the mapped make target, runs the wait-for-dev healthcheck, and confirms reachability through the published port. - Use Case: After bumping Rsbuild from v1 to v2, all CI jobs (static, unit, integration, Lighthouse) fail at container startup. Use this Skill to identify the changed server.host default, pin the binding in rsbuild.config.ts, and verify with the healthcheck target. ## Quick Start Diagnose why my containerized dev server is unreachable on the published Docker port after the Rsbuild upgrade and fix the host binding in the bundler config.
