You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
- stop generating full executable action ID arrays in the Node and
Cloudflare provider registries
- use the loaded executor module service keys to identify locally
executable providers
- resolve those services to the exact action IDs present in the loaded
catalog before creating `CatalogStore`
- preserve explicit `executableActionIds`, runtime execution metadata,
and public response shapes
This is the first of the two changes discussed in #235. Catalog asset
chunking will follow in a separate PR.
## Why
The generated Cloudflare registry repeated all 12,743 executable action
IDs even though each included provider already has a lazy executor
module entry. The existing generator marks every action from an included
provider executable, so the executor module service keys carry the same
information more compactly.
## Wrangler size comparison
Measured from `v1.3.3` and this branch with Wrangler 4.115.0, the same
Cloudflare bindings/configuration, `--dry-run`, and `--minify`:
| Build | Minified upload | Gzip |
| --- | ---: | ---: |
| `v1.3.3` baseline | 11,935.15 KiB | 2,854.70 KiB |
| This PR | 11,566.36 KiB | 2,777.99 KiB |
| Reduction | **368.79 KiB** | **76.71 KiB** |
The emitted `cloudflare.js` decreased from 12,221,596 to 11,843,955
bytes, a reduction of 377,641 bytes.
## Validation
- generated both provider registries for 1,194 total / 1,192 Cloudflare
providers
- `oxlint . --fix`
- `oxfmt .`
- `node scripts/typecheck.ts src scripts-all examples`
- `vitest run` — 61 test files and 591 tests passed
- Wrangler dry-run builds for both baseline and optimized revisions
Refs #235
0 commit comments