From 8d76af3e5fcfdfaefd6ec604fc24c928ce475c61 Mon Sep 17 00:00:00 2001 From: gsxdsm Date: Tue, 18 Aug 2026 20:40:41 -0700 Subject: [PATCH] docs: correct a stale dev-tunnel comment describing the removed fallback Co-Authored-By: Claude Opus 5 --- scripts/dev-with-memory.mjs | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/scripts/dev-with-memory.mjs b/scripts/dev-with-memory.mjs index c0ff0035dd..27fca59de3 100644 --- a/scripts/dev-with-memory.mjs +++ b/scripts/dev-with-memory.mjs @@ -106,8 +106,9 @@ normal Fusion already holding 4040, the tunnel pointed at THAT instance and serv under a dev-looking URL. Wait for the child's listening report and tunnel the port it actually got. An explicit `--tunnel=PORT` names a target the operator chose (a Vite server the dev child knows -nothing about), so it is used immediately and never waits. If the report never arrives the tunnel -still comes up on the configured port, since a mis-targeted preview beats no preview at all. +nothing about), so it is used immediately and never waits. Without one the wrapper WAITS for the +report rather than falling back to the configured port: publishing a guess pointed a dev-looking URL +at whatever else held that port, which is the exact confusion this fix exists to remove. */ /* FNXC:DevTunnel 2026-08-19-03:38: