Turns nothing into a deployable drupflare/worker tree, and resumes rather than repeating.
The steps are a clone, a bun install and a bun run hydrate, which is what PUBLISHING.md
documents as the path from git clone to wrangler deploy. drangler does not reimplement any of
it: the checkout is where the pack format, the payload manifest and the asset plan live, and
running that repository's own scripts inside a clone of it is what keeps there being one copy.
Turns nothing into a deployable
drupflare/workertree, and resumes rather than repeating.The steps are a clone, a
bun installand abun run hydrate, which is whatPUBLISHING.mddocuments as the path fromgit clonetowrangler deploy. drangler does not reimplement any of it: the checkout is where the pack format, the payload manifest and the asset plan live, and running that repository's own scripts inside a clone of it is what keeps there being one copy.