[ben-reitz]

A host module can't tell which run a call came from. A module that keeps per-run state, such as one browser session per run, has nothing to key it on: callId changes on every call.

Every host module call now gets context.execution, a frozen { id }. Every call of one run gets the same value, and a replayable run keeps it when it resumes after a restart or an answer. A module's functions belong to one backend connection, so the id alone tells its runs apart.

modules: {
  "codemode:session": {
    open: (_args, { execution }) => sessions.open(execution.id),
  },
}

The bridge now takes the execution rather than a bare call id prefix and still builds callId from its id, so call ids don't change. A bridge test checks that every call of a run gets the same frozen value, and a workerd test restarts the object mid-run and checks that calls before and after the restart see the same execution. The host module context table in docs/17_isolate_javascript.md lists the new field.

[changeset-bot]

🦋 Changeset detected

Latest commit: 77b68d2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@cloudflare/computer	Minor
@cloudflare/dofs	Minor
@cloudflare/computer-rpc	Minor
@cloudflare/computerd	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@cloudflare/computer@290

commit: 77b68d2