start: busy port should shift to the next free one (Vite-style) and the printed URL should be openable · Issue #557 · JavaScriptSolidServer/JavaScriptSolidServer · GitHub
Port-back from jspod (lib/start.js), where both behaviours are implemented and proven.
Problem
jss start on a busy port dies with a raw EADDRINUSE — a first-run papercut, especially when a stale instance is still running.
The startup banner prints the bind host verbatim — http://0.0.0.0:4443 isn't an openable URL (and bare IPv6 hosts need brackets).
Fix (proven downstream in jspod)
findFreePort — when the requested port is busy, probe upward one port at a time (cap ~10 tries, Vite's behaviour), print what happened, and bind there. Explicitly-passed --port could either still shift with a notice, or fail hard with a clear message (jspod shifts; either is fine if loud).
Activity
feat(cli): shift off a busy port + openable banner URL on jss start — c…
bump version to 0.0.209