Every checkout registered the dev server as the same portless name on the machine-shared multiplex proxy, so the proxy's duplicate-app selector listed every parallel checkout's server under one host — and its per-entry Kill button SIGTERMed whichever sibling you clicked. The name now derives from the checkout directory, scoping the selector (and its Kill button) to that checkout's own processes.
Unified · Split
| @@ -10,7 +10,7 @@ · 9 unmodified lines | ||
| 10 | 10 | "scripts": { |
| 11 | 11 | "dev": "bun run dev:proxy && bun run dev:vite", |
| 12 | 12 | "dev:proxy": "portless proxy start --multiplex --port 1355 || true", |
| 13 | − "dev:vite": "EXECUTOR_DATA_DIR=${EXECUTOR_DATA_DIR:-.executor-dev} portless --name executor-local bunx --bun vite dev", | |
| 13 | + "dev:vite": "EXECUTOR_DATA_DIR=${EXECUTOR_DATA_DIR:-.executor-dev} portless --name \"executor-local-$(basename \"$(cd ../.. && pwd)\")\" bunx --bun vite dev", | |
| 14 | 14 | "build": "turbo run build --filter @executor-js/vite-plugin && bunx --bun vite build", |
| 15 | 15 | "start": "bun run src/serve.ts", |
| 16 | 16 | "db:generate": "drizzle-kit generate", |