Repository navigation
Conversation
cf migrate needs wrangler/experimental-config (>= 4.100.0). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- cloudflare.config.ts (from cf migrate) + wrangler.config.ts (bundler rules) - dev/deploy npm scripts use cf; deploy workflow uses cf deploy and cf workers versions create (Node 22 for cf) - bump wrangler 4.136, sentry 10.76, workers-types 5.20260929.1 (older 5.x pinned: newest is blocked as recently published) wrangler.toml stays for d1 execute / tail, which cf can't replace yet. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…isory wrangler 4.136's miniflare pulled undici 7.29.0 (high severity), which fails the npm audit gate via @sentry/cloudflare's wrangler peer. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- tee hid a failed cf upload (default Actions bash has no pipefail) - cf dev defaults to ~/.config/cloudflare/state; point it at .wrangler/state - refresh stale wrangler mentions in .dev.vars.example Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🚀 Cloudflare previewURL: https://2554500f-htmlbin.utkarsh2012.workers.dev Built from commit
|
- db:* scripts use cf d1 raw / cf d1 migrations (by database UUID) - stats.mjs and the dashboard query through cf d1 raw - setup.mjs provisions D1/KV and secrets with cf - drop the tail script (no cf equivalent; use cf observability telemetry query) - local cf d1 commands use .wrangler/state, the dir cf dev always writes - docs: command map, the --sql= gotcha, why wrangler stays a dependency Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
utsengar
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves htmlbin from Wrangler to Cloudflare's
cfCLI (open beta,cf@1.0.0-beta.12). Every npm script, CI step and doc command now runs throughcf, andwrangler.tomlis gone.cloudflare.config.ts(fromcf migrate), pluswrangler.config.tsfor the CompiledWasm bundler rulecf workers versions createfor PR previews,cf deployon merge, Node 22 (cf needs >= 22.18),pipefailso a failed upload fails the stepdev/deploy→cf;db:*→cf d1 raw/cf d1 migrations;stats.mjs, the dashboard andsetup.mjs→cftailscript removed (nocfequivalent;cf observability telemetry querycovers recent logs)Why Wrangler is still in package.json
cfbuilds by delegating to Wrangler and runscf devthrough it;@cloudflare/vite-plugindepends on it too. It's a build dependency ofcf, not a CLI we call.cf devalso always keeps local state in.wrangler/state, so localcf d1commands point there.Tested locally
npm run db:apply:local(cf),npm run dev(cf),npm run test:e2e: 152/152 pass;/og.pngrenders (CompiledWasm)npm run stats -- --localand the dashboard's/api/overviewreturn the e2e data throughcf d1 rawcf deploy --dry-runandcf workers versions create --dry-runbuild with the same bindingscfsource: deploys keep existing secrets (keep_bindingsincludes secrets), anddomainsmap to custom-domain routes as beforeNot verified
CLOUDFLARE_API_TOKENhas the scopescfneeds. The last two runs never got a GitHub runner.cf d1 raw/ migrations (db:*:remote, remote stats/dashboard): no production queries were run.setup.mjsagainst a fresh account (it would create resources).cf devneeds bothcf auth loginandnpm exec -- wrangler login(the bundled Wrangler handles the remote AI binding).🤖 Generated with Claude Code