feat: support binding dev server to all network interfaces via --host

[hackxixi]

Summary

• Add PEAKCODE_HOST and VITE_WS_PORT to turbo.json globalEnv so Turbo passes them through to Vite and the server processes
• Read PEAKCODE_HOST in vite.config.ts to bind Vite's dev server to the configured interface (default: localhost)
• When binding to a wildcard address (0.0.0.0 / ::), inject VITE_WS_PORT instead of hardcoding [::1] into VITE_WS_URL, so the browser constructs the WebSocket URL from window.location.hostname + the correct server port
• Fix bug in wsTransport.ts: fallback URL was using window.location.port (Vite port 5733) instead of the WS server port (3773), breaking WebSocket connections when accessed from external hosts
• Add VITE_WS_URL and VITE_WS_PORT to ImportMetaEnv type declarations

Usage

bun run dev -- --host 0.0.0.0

Test plan

• bun run dev (no flags) still binds to localhost only — behaviour unchanged
• bun run dev -- --host 0.0.0.0 binds both Vite (5733) and the WS server (3773) to 0.0.0.0
• Accessing the app from another device on the LAN connects successfully and the WebSocket handshake completes
• bun fmt && bun lint && bun run typecheck pass

https://claude.ai/code/session_01B95xcqmnLyWiAhApQdjtLC

[jwangkun]

感谢这个 PR @hackxixi,支持 --host 绑定网卡的需求是合理的,代码改动本身(vite.config / wsTransport 端口 bug 修复 / dev-runner 的 wildcard 处理)质量也不错 👍

但是这个 PR 目前没法合并,核心问题是 bun.lock 被本地 npm 镜像污染了:

这个 PR 有 +1333/−1306 的改动,其中 1303 行删除全部来自 bun.lock。进一步看 diff,bun.lock 里每个包的解析地址被从空字符串改成了 https://registry.npmmirror.com/...:

- "@anthropic-ai/claude-agent-sdk": [..., "", ...]
+ "@anthropic-ai/claude-agent-sdk": [..., "https://registry.npmmirror.com/@anthropic-ai/claude-agent-sdk/-/claude-agent-sdk-0.2.112.tgz", ...]

这会把贡献者本地的 npmmirror 镜像源固化进仓库,影响所有其他开发者的依赖解析,属于 lockfile drift,不能合入。

如果你愿意重新提交,建议这样做:

1. 基于最新 main 重新开分支(main 已经有较多更新)。
2. 只保留代码改动(vite.config.ts、wsTransport.ts、dev-runner.ts、vite-env.d.ts、turbo.json),不要提交 bun.lock 的改动(或者用官方源重新 bun install 生成一份干净的 lockfile)。
3. 重新开一个聚焦的 PR。

整理好之后欢迎再提,这个功能是有价值的 🙏