Skip to content

Add the edge-light export condition once a Vercel Edge run justifies it #806

Description

@tobyhede

Follow-up from the portable-encryptedSupabase design (#708).

edge-light (Vercel Edge Runtime) was carried in an early draft of the export map and cut before shipping. It was never in the design spec, had no evidence behind it, and — unlike every other unevidenced claim in the series — was not acknowledged anywhere as unevidenced. It would have shipped in the export map, README, changeset and AGENTS.md on the assumption that "it is probably the same build as workerd".

Probably is not a condition to ship. Vercel Edge has its own WASM instantiation constraints, and nobody has tested them against @cipherstash/protect-ffi's inlined-base64 bootstrap — which is the specific thing most likely to differ, since Vercel Edge historically restricted dynamic WebAssembly.instantiate on non-imported buffers.

What to do

Run @cipherstash/stack-supabase's WASM build on Vercel Edge. If the blob instantiates and a round-trip works, add edge-light to the export map alongside workerd/deno, add it to the runtime lists in the skill, README and AGENTS.md, and extend package-exports.test.ts.

Size is worth checking at the same time: the inlined blob is 4,379,681 bytes raw / 1,564,507 gzipped, and Vercel Edge's bundle limits are tighter than Cloudflare's.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions