ci: strip dead default-module-path branch from pg-wasm web build

[rubenhensen]

Summary

The @e4a/pg-wasm web target generated by wasm-pack build --target web ships an unreachable default-value branch in __wbg_init:

if (module_or_path === undefined) {
    module_or_path = new URL('index_bg.wasm', import.meta.url);
}

Webpack 5 statically analyzes new URL("...", import.meta.url) as an asset import and tries to resolve index_bg.wasm at build time — even though the branch never fires for callers that always pass module_or_path explicitly (e.g. @e4a/pg-js, which inlines the WASM as base64). Downstream consumers therefore hit Module not found: Can't resolve 'index_bg.wasm'.

wasm-pack does not expose wasm-bindgen's --omit-default-module-path flag, so this PR adds a post-build step to delivery.yml's publish-wasm job that strips the branch from the generated pg-wasm/pkg/web/index.js. The strip:

• Matches the assignment block by pattern (not line numbers), with a flexible if condition so a wasm-bindgen version change to e.g. typeof module_or_path === 'undefined' still matches.
• Fails loudly (exit 1) if the pattern is gone, so a future wasm-bindgen change can't silently no-op the strip and ship the regression again.

The bundler target is unaffected — it emits import * as wasm from "./index_bg.wasm" with no __wbg_init function and no new URL(...) branch — so no strip is needed there (this corrects fix-option 2 in the issue body).

Verification

Built the web target locally with wasm-pack 0.14.0 and confirmed against the real generated output:

• The dead branch is present at pg-wasm/pkg/web/index.js before stripping.
• The exact node script from this PR removes the 3-line block, leaving zero index_bg.wasm references.
• The remaining __wbg_init flow is intact — control passes straight into the typeof module_or_path === 'string' || ... instanceof Request || ... instanceof URL path that fires when a caller passes module_or_path explicitly.
• node --check passes on the stripped file.

Behavior change: a caller that invokes init() with no argument now gets a runtime error at instantiate time instead of a webpack build-time error — exactly what --omit-default-module-path produces. All current consumers pass module_or_path, so they are unaffected.

Downstream

Once a new @e4a/pg-wasm ships with this fix, @e4a/pg-js only needs a dep bump + republish, and the parser: { url: false } webpack workaround in downstream consumers can be removed.

Fixes #153

[dobby-coder]

Dobby hit a rate limit mid-task and had to pause. Resets 6/12/2026, 4:00:00 PM. I'll automatically resume where I left off — no work lost!

[dobby-coder]

Opened #222 as an alternative that resolves the same issue via wasm-bindgen's --omit-default-module-path flag (the issue's preferred option 1) rather than a post-build regex strip.

wasm-pack 0.15.0 (the version CI installs) exposes this flag through crate-manifest metadata:

[package.metadata.wasm-pack.profile.release.wasm-bindgen]
omit-default-module-path = true

Verified locally: with this set, wasm-pack build --target web generates __wbg_init with no new URL('index_bg.wasm', import.meta.url) branch at all (0 index_bg.wasm refs), while the explicit-module_or_path fetch path is retained. Bundler target unaffected.

Advantages over this PR: it's a Cargo.toml-only change (no .github/workflows/ edit, which also unblocks the bot's missing workflows: write permission), and it doesn't pattern-match against generated output. Whichever you prefer — flagging so you don't merge both.