Skip to content

fix(cloudflare): rely on autoprovisioning while preserving resource names - #3529

Merged
james-elicx merged 1 commit into
mainfrom
codex/binding-autoprovision-cleanup
Sep 28, 2026
Merged

james-elicx merged 1 commit into
mainfrom
codex/binding-autoprovision-cleanup

Conversation

@james-elicx

@james-elicx james-elicx commented Sep 28, 2026 •

Copy link
Copy Markdown
Member

Keep Response Store's configured resource names and let cf deploy provision missing R2 buckets with those exact names. The generated bucket names and bindings.r2({ name: options.bucket }) remain unchanged. Remove the obsolete instruction to create those buckets manually from init and the deployment docs. The Response Store Worker still has its explicit deployment command.

Remove the D1 placeholder ID from the README while retaining name: "my-db", and remove the remaining KV placeholder ID from the pages-router-complex example.

Validation:

  • 266 initializer tests passed, including both Response Store modes and the auxiliary Worker deployment guidance.
  • D1, R2, and KV binding examples type-checked against the installed Cloudflare config API.
  • Targeted formatting, lint, type checks, and git diff checks passed.
  • Verified the installed cf 1.0.0-beta.1 deploy path enables provisioning and creates missing named R2 buckets; no live deployment was performed.

@pkg-pr-new

pkg-pr-new Bot commented Sep 28, 2026

Copy link
Copy Markdown

Open in StackBlitz

@vinext/cloudflare

npm i https://pkg.pr.new/@vinext/cloudflare@3529

create-vinext-app

npm i https://pkg.pr.new/create-vinext-app@3529

@vinext/types

npm i https://pkg.pr.new/@vinext/types@3529

vinext

npm i https://pkg.pr.new/vinext@3529

@cloudflare/workers-response-store

npm i https://pkg.pr.new/@cloudflare/workers-response-store@3529

commit: e794fdd

@github-actions

Copy link
Copy Markdown
Contributor

Performance benchmarks

Compared e794fdd against base 226e39e using alternating same-runner rounds. Next.js was unchanged and skipped.

1 improved · 0 regressed · 5 within ±1.5%

Scenario Framework Baseline Current Change
Client bundle size (gzip) vinext 142.3 KB 142.3 KB ⚫ -0.0%
Client entry size (gzip) vinext 130.4 KB 130.4 KB ⚫ -0.0%
Dev server cold start vinext 2.63 s 2.56 s 🟢 -2.5%
Production build time vinext 2.83 s 2.83 s ⚫ +0.1%
RSC entry closure size (gzip) vinext 128.3 KB 128.3 KB ⚫ -0.0%
Server bundle size (gzip) vinext 226.8 KB 226.8 KB ⚫ -0.0%

View detailed results and traces

🟢 improvement · 🔴 regression · ⚫ change below 1.5% · paired base/head

@github-actions

Copy link
Copy Markdown
Contributor
Example Preview Production Original
app-router-cloudflare preview production
pages-router-cloudflare preview production
app-router-playground preview production original
realworld-api-rest preview production
nextra-docs-template preview production
benchmarks preview production
hackernews preview production original
response-store-demo preview production
workers-cache preview production
kv preview production
static-assets-cache preview production
static-export preview production
web preview production

@james-elicx james-elicx changed the title fix(cloudflare): remove manual binding provisioning steps fix(cloudflare): rely on autoprovisioning while preserving resource names Sep 28, 2026
@james-elicx
james-elicx merged commit 074e64f into main Sep 28, 2026
83 checks passed
@james-elicx
james-elicx deleted the codex/binding-autoprovision-cleanup branch September 28, 2026 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant