temp: patch wasm-pack to point to latest binary

[abcxff]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[abcxff]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• TODO: ktichen sink counter latency #5051
• fix(rivetkit): use engine actor stop threshold for shutdown #5049
• DO NOT MERGE: serverless restart race condition #4997
• fix(rivetkit): exit pid1 after signal shutdown #5045
• fix(rivetkit-core): decrement active actor metrics #5044
• fix(envoy-client): dont abort drain after 20s #5043
• temp: patch wasm-pack to point to latest binary #5037 👈 (View in Graphite)
• fix(rivetkit): require engine ping for health #5022
• feat(rivetkit): add current actor metrics #5020
• feat(rivetkit): expose low-cardinality metrics routes #5019
• docs(serverless): document timeout tuning #5018
• feat(kitchen-sink): add load testing harness #5017
• fix(rivetkit): expose client actor metadata #5016
• fix(runtime): avoid bounded dispatch channel stalls #5015
• fix(sqlite): fence remote requests by generation #5014
• feat(rivetkit-core): expose metrics endpoint #5013
• WIP: counter latency monitor #5011
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[abcxff]

See wasm-bindgen/wasm-pack#1577

[claude]

PR Review for PR 5037 (temp: patch wasm-pack)

Overview: Patches wasm-pack@0.14.0 to fix its binary download URL (moved from drager to wasm-bindgen org), bumps from 0.13.1 to 0.14.0, and disables the build-wasm CI job.

ISSUE 1 - Stale pnpm-lock.yaml override (bug): package.json removed the wasm-pack entry from overrides, but pnpm-lock.yaml line 26 still reads wasm-pack: =0.13.1. The lock file also retains a wasm-pack@0.13.1 snapshot near line 17998. Run pnpm install and recommit the updated lock file.

ISSUE 2 - Commented-out CI job leaves dead code: The entire build-wasm job is commented out in publish.yaml rather than deleted. If temporary, add an inline comment explaining the condition to re-enable. If the wasm package is no longer published, delete the job and remove references to rivetkit-typescript/packages/rivetkit-wasm/pkg from downstream steps.

ISSUE 3 - Missing newline at end of package.json: The diff shows No newline at end of file. Add a trailing newline.

CONCERN - Supply chain: The patch redirects binary downloads from github.com/drager/wasm-pack to github.com/wasm-bindgen/wasm-pack. This appears correct given the project transferred orgs, but confirm the new release URL resolves to the expected artifact before merging.

CONCERN - Patch fragility: Patching binary.js is a reasonable short-term workaround. Once wasm-pack ships an npm release with the corrected URL, this patch and the patchedDependencies entry can be dropped.

Summary: The core change (patching the download URL) is the right approach. Three things to fix before merging: regenerate the lock file to remove the stale =0.13.1 override, add a trailing newline to package.json, and either delete the commented-out build-wasm job or add a note explaining when to restore it.