fix(runframe): use the embedded eval worker in CLI standalone mode

[addibble]

Problem

The CLI branch in standalone.tsx rendered <RunFrameForCli {...runframeStandaloneProps} />. runframeStandaloneProps carries the embedded eval-worker blob under evalWebWorkerBlobUrl, but RunFrameForCli reads workerBlobUrl — a different name — so the blob was silently dropped. RunFrameForCli then computes:

forceLatestEvalVersion={!props.workerBlobUrl && shouldLoadLatestEval}  // -> true

and fetches eval from the CDN instead of using the embedded worker.

Whenever an eval worker is embedded into the standalone (the tscircuit umbrella build fills that placeholder), CLI mode ignored it and silently downloaded a different eval from the network. This breaks offline / air-gapped / pinned-eval / locally-built-eval usage of tsci dev — the embedded worker should be authoritative.

Fix

Forward the blob explicitly under the name RunFrameForCli actually reads, and pass enableFetchProxy:

root.render(
  <RunFrameForCli
    workerBlobUrl={runframeStandaloneProps.evalWebWorkerBlobUrl}
    enableFetchProxy={runframeStandaloneProps.enableFetchProxy}
  />,
)

Forwarding by name (rather than spreading runframeStandaloneProps, typed as ComponentProps<typeof RunFrameWithApi>) also avoids passing RunFrameForCli an evalWebWorkerBlobUrl prop it does not accept. A comment documents that new standalone props must be added here explicitly.

Risk

Low, no regression for normal users: when no worker is embedded, evalWebWorkerBlobUrl is undefined, so behavior is unchanged and it still loads the latest eval from the CDN. Behavior only changes when a worker blob is actually embedded — the case this is meant to handle.

---

Draft: opening for review before merge. (package.json is intentionally excluded — local yalc artifacts only.)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
runframe	Ready	Preview, Comment	Jun 23, 2026 12:53am

[github-actions]

This PR has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs.