What problem does it solve?
Porting a Cloudflare Sandbox application from the stable @cloudflare/sandbox package to the @next (Sandbox SDK 1.0 preview) line involves breaking API changes—removed sessions, transport settings, and buffered exec results—that are easy to get wrong. This Skill provides a structured audit, replacement map, and cutover procedure so the migration is complete and consistent.
Core Features & Use Cases
- Codebase Audit: Grep patterns locate every stable-only API usage (SANDBOX_TRANSPORT, sessions, execStream, gitCheckout, string kill signals) that must be replaced.
- Replacement Map: A stable-to-@next mapping table plus code shapes for argv-based exec with process handles, createTerminal/connect terminals, withInterpreter, and git via argv.
- Safe Production Cutover: Enforces matching Worker package and container image versions and an immediate container rollout via wrangler, avoiding a broken mixed-protocol window.
- Use Case: You have a production Worker using stable Sandbox sessions and buffered exec calls. Run this Skill to audit the code, rewrite call sites to the @next handle-based API, upgrade the Dockerfile image, and deploy with --containers-rollout=immediate.
Quick Start
Migrate my Cloudflare Sandbox app from the stable @cloudflare/sandbox package to @cloudflare/sandbox@next and update the code, Dockerfile, and deployment accordingly.