Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
⏭️ Performance benchmarks were skippedPerf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to To run them on this PR, do any of the following, then push a commit (or re-run CI):
|
Binary size checks passed✅ 7 passed
Generated by |
|
Closing in favor of #4052, which now includes the cargo-nextest setup for building and installing @boundaryml/baml-bridge-web into the TypeScript test fixtures. |
Summary
This is an alternative to #4052 for comparing the TypeScript Web SDK release scaffolding. It keeps the same package/release scope, but generates the Workers Wasm entrypoint through Cloudflare's
workers-rs/worker-buildtoolchain instead of adapting wasm-bindgen's bundler output directly.workerandworker-build0.8.5 with their wasm-bindgen 0.2.125 toolchainworker-buildCargo feature, leaving browser Wasm unchangedWorkerEntrypoint.prototypemethods back into the named library API expected by@boundaryml/baml-bridge-webTradeoffs
strip = truecloudflare/workers-rs#1014The runtime remains intentionally scaffold-only, matching #4052: the package imports and exposes its API, but runtime calls may fail until the Web/Workers implementation change is applied.
Validation
mise run stowmise run fmtmise run clippyactionlint .github/workflows/build2-web-sdk.reusable.yamlpnpm pack --dry-run