cloudflare-mbt-worker-bundle

Bundling a Cloudflare Worker with MoonBit requires shipping the MoonBit core JS output alongside a TypeScript entry shim. This process aligns the deployment pipeline with wrangler deploy and uses pre-bundle and post-bundle scripts to generate the core file under src/_generated.

A MoonBit Cloudflare Worker may hang on startup due to missing FFI rewrites or failed post-build bundle integrity checks. Enforcing mandatory FFI rewrites and running post-build checks prevents these startup hangs and ensures the worker starts reliably.

Yes, deploying a MoonBit-powered Worker requires the wrangler toolchain and the MoonBit output located in _build/js/release/build. These dependencies are necessary to execute the pre-bundle and post-bundle scripts that produce the generated core file.

The best way to integrate MoonBit FFI rewrites into a wrangler deployment workflow is by running pre-bundle and post-bundle scripts located in assets/scripts/. This enforces mandatory FFI rewrites and generates the core file under src/_generated for wrangler deployments.

Limitations when bundling MoonBit JS output for Cloudflare Workers include the strict requirement for mandatory FFI rewrites and post-build bundle integrity checks. Without these enforced steps, the generated core file may cause startup hangs during wrangler deployment.