dsh web hangs at startup — pegs one CPU core, never binds 127.0.0.1:3080 (Windows 11)

[Chen1967-spec]

dsh web hangs at startup — pegs one CPU core indefinitely, never binds 127.0.0.1:3080 (Windows 11)

Summary

Running npx @deepseek-ai/dsh@latest web installs successfully, but the process never starts the Web UI. Instead it spins one CPU core at ~100% indefinitely, prints nothing, and never opens a listener on 127.0.0.1:3080. There is no error and no crash — it just hangs forever.

Environment

• OS: Windows 11 Home, build 10.0.26200 (x64)
• Package: @deepseek-ai/dsh@0.1.1-rc.2 (installed via npx --yes @deepseek-ai/dsh@latest web)
• npm: 11.17.0
• Node.js: reproduced on both v25.2.1 and v24.20.0 (LTS)
• Run from a normal Command Prompt (cmd.exe)

Steps to reproduce

npx --yes @deepseek-ai/dsh@latest web

Expected

The server starts and prints something like Web UI running at http://127.0.0.1:3080, and the UI is reachable at that URL.

Actual

• Install/resolution completes normally (~840 MB cached).
• The CLI then displays a spinner and hangs.
• One node process consumes ~100% of a single CPU core continuously. CPU time accumulates linearly with wall-clock time (e.g. observed climbing from 61s → 197s of CPU over ~110s), with no plateau.
• No listener ever appears on port 3080 (verified with Get-NetTCPConnection -LocalPort 3080 and repeated HTTP probes — connection always refused).
• No stdout/stderr output at all, even when redirected to a file (> log.txt 2>&1 produced a 0-byte file).
• Behavior persists indefinitely (left running several minutes on multiple attempts).

What I ruled out

• Not a download/install problem — happens after install.
• Not a Node.js version issue — identical hang on Node 25.2.1 and 24.20.0 (LTS).
• Not a stale npx cache — deleting %LocalAppData%\npm-cache\_npx and re-running gave the same hang.
• No interactive prompt involved — the process is actively burning CPU, not idle.

Notes

The steady, linear CPU consumption with no output and no port bind suggests a busy-loop during startup rather than a slow build. Happy to provide additional diagnostics if there's a debug flag that surfaces where startup stalls.