Run cloud app bundling in a dynamic Worker#1375
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 144f683 | Commit Preview URL Branch Preview URL |
Jul 09 2026, 01:55 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 144f683 | Jul 09 2026, 01:57 AM |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
executor
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
commit: |
RhysSullivan
force-pushed
the
apps-cloud-bundler-isolate
branch
from
4bf4840 to
fe68780
Compare
The publish bundler (esbuild-wasm plus npm install) now runs in its own dynamically loaded Worker instead of the request isolate, matching the selfhost workerd design. A heavy dependency tree no longer exhausts the serving isolate's memory.
Invoke now uses a stable Worker Loader ID derived from the owner-scoped content-addressed bundle key and driver version, allowing warm isolates to be reused without sharing state across owners. Collect remains one-shot and uses loader.load when the binding exposes it.
RhysSullivan
force-pushed
the
apps-cloud-bundler-isolate
branch
from
fe68780 to
144f683
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The publish bundler (esbuild-wasm plus the npm install of app dependencies) now runs in its own dynamically loaded Worker on cloud instead of the serving isolate, matching the selfhost workerd design. A heavy dependency tree no longer exhausts the request isolate's memory; a bundling failure now surfaces as a failed sync instead of a dropped connection.
Also reuses app tool isolates across invocations via a stable, tenant-scoped Worker Loader ID keyed on the content-addressed bundle.