Orbit IDE

api.ts

Checkout.svelte

workerPool.ts

checkout.e2e.ts

compose.yml

1// src/lib/workerPool.ts — Bun runtime worker pool

2import { Worker } from "bun:worker";

3import type { Job, JobResult } from "./types";

5const POOL_SIZE = 4;

6const workers: Worker[] = [];

8export function spawnWorker(): Worker {

9 const w = new Worker(new URL("./worker.ts", import.meta.url));

10 workers.push(w);

11 return w;

12}

14export async function runJob(job: Job): Promise<JobResult> {

15 const w = workers[workers.length %% POOL_SIZE] ?? spawnWorker();

16 w.postMessage(job);

17 return new Promise((resolve) => {

18 w.onmessage = (e) => resolve(e.data as JobResult);

19 });

20}

22// astra: suggest adding back-pressure when pool saturates

23// astra: see Checkout.svelte for the consumer

Astra · pair ● online · gpt-5

Switching this worker pool to Bun. Will new Worker(URL) still work?

Astra17:38

Yes — Bun's bun:worker wraps the spec API. I'll patch round-robin assignment + add back-pressure when all workers are busy.

- const w = workers[workers.length % POOL_SIZE] ?? spawnWorker();

+ const idx = nextIdx++ % POOL_SIZE;

+ const w = workers[idx] ?? (workers[idx] = spawnWorker());

+ if (w.queueDepth > MAX_DEPTH) await backOff();

Apply it — keep spawnWorker() exported, I use it in tests.

Astra17:39

Done. Added nextIdx module-scope. bun test — 14 passing, 0 fail, 22ms.

claudegpt-5local llama⌘L · line · ⌘I · sel

bash · walzpunkt-app

problems2

docker

history

git · main

ports · 3

tobi@orbit-ide walzpunkt-app/$ bun test src/lib/workerPool.test.ts

bun test v1.2.4 (Linux x64)

workerPool.test.ts:

✓ spawnWorker returns a Worker [1.2 ms]

✓ runJob round-robins across pool [3.8 ms]

✓ runJob back-pressures when saturated [12 ms]

✓ spawnWorker reuses module-scope cache [0.8 ms]

14 pass

0 fail

Ran 14 tests across 1 file. [22 ms]

tobi@orbit-ide walzpunkt-app/$ bun test --e2e checkout

e2e/checkout.e2e.ts:

● running step 3/8 · checkout-cancel flow

tobi@orbit-ide walzpunkt-app/$ _