Skip to content

feat(cloudflare): migrate deployments to Alchemy v2 - #1144

Merged
AmanVarshney01 merged 19 commits into
mainfrom
aman/alchemy-v2-core
Aug 12, 2026
Merged

AmanVarshney01 merged 19 commits into
mainfrom
aman/alchemy-v2-core

Conversation

@AmanVarshney01

@AmanVarshney01 AmanVarshney01 commented Aug 10, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Migrate generated Cloudflare infrastructure from Alchemy v1 to the Effect-based Alchemy v2 API.
  • Cover web-only, Workers server, combined, full-stack self, and D1 deployment topologies.
  • Use native Alchemy inputs and Vite resources where qualified, with explicit bindings and environment inference.
  • Add the Alchemy findings ledger, OpenSpec deployment contract, and maintenance skills.

Stack

Layer 1 of 8. Next: #1145.

The complete stack is verified at #1110.

Stack created with GitHub Stacks CLI • Give Feedback 💬

Summary by CodeRabbit

  • New Features

    • Expanded Cloudflare deployment support across Next.js, React Router, Svelte, Nuxt, Astro, TanStack Router, and Solid.
    • Added local D1 migration commands and automatic Prisma SQLite database setup.
    • Added guided OpenSpec workflows for planning, implementation, exploration, updates, synchronization, and archiving.
    • Improved generated Worker builds, deployment configuration, environment handling, and framework integrations.
  • Bug Fixes

    • Fixed Svelte Cloudflare environment handling, Prisma Worker builds, and local database paths.
    • Improved migration guidance and deployment setup reliability.
  • Documentation

    • Added Cloudflare and Alchemy compatibility findings, deployment guidance, and upgrade verification requirements.

@vercel

vercel Bot commented Aug 10, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
create-better-t-stack-web Ready Ready Preview Aug 12, 2026 3:17pm

Request Review

@AmanVarshney01 AmanVarshney01 changed the title aman/alchemy v2 core feat(cloudflare): migrate deployments to Alchemy v2 Aug 10, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 11

🧹 Nitpick comments (5)
packages/template-generator/src/processors/alchemy-plugins.ts (1)

84-95: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Both package.json edits bypass the VirtualFileSystem JSON helpers. Each site calls readFile and JSON.parse directly, which throws on malformed JSON. vfs.readJson and vfs.writeJson already handle a missing file and a parse failure.

  • packages/template-generator/src/processors/alchemy-plugins.ts#L84-L95: replace readFile plus JSON.parse with vfs.readJson, and replace the manual stringify with vfs.writeJson.
  • packages/template-generator/src/processors/alchemy-plugins.ts#L224-L233: apply the same replacement for the build:cloudflare script write.
packages/template-generator/templates/packages/infra/alchemy.run.ts.hbs (1)

79-133: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚖️ Poor tradeoff

Consider extracting the repeated env binding block into a partial.

The env maps for next, nuxt, svelte, and astro repeat the same database, auth, AI, payments, and MySQL entries, and the same blocks repeat again in the non-self branches at Lines 333-530. A shared Handlebars partial would remove the duplication and keep the branches in sync when a binding is added.

Also applies to: 134-179, 180-225, 226-271

packages/template-generator/src/post-process/package-configs.ts (1)

199-208: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

One "local D1 fullstack" predicate is duplicated across three processors. Each site re-derives the same condition from webDeploy, backend, dbSetup, and a hard-coded frontend list. The copies must stay in sync, otherwise the root script, the README step, and the wrangler dependency disagree for the same configuration.

  • packages/template-generator/src/post-process/package-configs.ts#L199-L208: replace the inline hasLocalD1 computation with a call to a shared helper.
  • packages/template-generator/src/processors/readme-generator.ts#L607-L610: replace the inline isFullstackStaticSite computation with the same shared helper.
  • packages/template-generator/src/processors/deploy-deps.ts#L117-L120: derive needsLocalD1 from the shared helper, and document why next is excluded from the frontend list here.
packages/template-generator/src/processors/deploy-deps.ts (1)

129-135: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Skip the dependency write when the list is empty.

When isBackendSelf is false, addPackageDependency receives empty lists and rewrites apps/web/package.json with no change. Guard the call instead.

♻️ Proposed refactor
-    } else if (frontend.includes("nuxt")) {
+    } else if (frontend.includes("nuxt") && isBackendSelf) {
       // wrangler powers the dev-time cloudflare:workers shim (getPlatformProxy)
       addPackageDependency({
         vfs,
         packagePath: webPkgPath,
-        devDependencies: isBackendSelf ? ["nitro-cloudflare-dev", "wrangler"] : [],
+        devDependencies: ["nitro-cloudflare-dev", "wrangler"],
       });
     } else if (frontend.includes("svelte")) {
packages/template-generator/src/utils/add-deps.ts (1)

162-166: 🩺 Stability & Availability | 🔵 Trivial

Schedule stable release pinning for the prerelease deps.

The pinned packages are published, alchemy@2.0.0-beta.67 accepts effect@4.0.0-beta.101 and the platform packages, and effect@4.0.0-beta.101 exposes the effect/Config and effect/Effect subpaths consumed by alchemy.run.ts.hbs. The remaining concern is that these generated Cloudflare projects depend on beta tags; plan a follow-up to move to stable releases before betas disappear.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 55f2fa64-2533-4d38-8726-f42951039926

📥 Commits

Reviewing files that changed from the base of the PR and between 89c03fb and 87796be.

⛔ Files ignored due to path filters (1)
  • packages/template-generator/src/templates.generated.ts is excluded by !**/*.generated.*
📒 Files selected for processing (44)
  • .codex/skills/openspec-apply-change/SKILL.md
  • .codex/skills/openspec-archive-change/SKILL.md
  • .codex/skills/openspec-explore/SKILL.md
  • .codex/skills/openspec-propose/SKILL.md
  • .codex/skills/openspec-sync-specs/SKILL.md
  • .codex/skills/openspec-update-change/SKILL.md
  • apps/cli/src/helpers/core/post-installation.ts
  • apps/cli/src/helpers/database-providers/d1-setup.ts
  • apps/cli/src/utils/compatibility-rules.ts
  • apps/cli/test/addons.test.ts
  • apps/cli/test/cloudflare-db-clients.test.ts
  • apps/cli/test/database-setup.test.ts
  • apps/cli/test/deployment.test.ts
  • apps/cli/test/post-installation.test.ts
  • apps/cli/test/vite-plus-generator.test.ts
  • docs/alchemy-v2-beta-findings.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/.openspec.yaml
  • openspec/changes/formalize-alchemy-cloudflare-deployment/README.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/design.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/proposal.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/specs/alchemy-cloudflare-deployment/spec.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/tasks.md
  • openspec/config.yaml
  • packages/template-generator/src/post-process/package-configs.ts
  • packages/template-generator/src/processors/alchemy-plugins.ts
  • packages/template-generator/src/processors/deploy-deps.ts
  • packages/template-generator/src/processors/env-vars.ts
  • packages/template-generator/src/processors/infra-deps.ts
  • packages/template-generator/src/processors/readme-generator.ts
  • packages/template-generator/src/processors/workspace-deps.ts
  • packages/template-generator/src/template-handlers/packages.ts
  • packages/template-generator/src/utils/add-deps.ts
  • packages/template-generator/src/utils/generated-ignore-patterns.ts
  • packages/template-generator/templates/api/orpc/server/src/context.ts.hbs
  • packages/template-generator/templates/backend/server/base/tsdown.config.ts.hbs
  • packages/template-generator/templates/extras/env.d.ts.hbs
  • packages/template-generator/templates/frontend/astro/astro.config.mjs.hbs
  • packages/template-generator/templates/frontend/nuxt/nuxt.config.ts.hbs
  • packages/template-generator/templates/frontend/react/react-router/vite.config.ts.hbs
  • packages/template-generator/templates/frontend/react/tanstack-start/vite.config.ts.hbs
  • packages/template-generator/templates/frontend/svelte/svelte.config.js.hbs
  • packages/template-generator/templates/packages/env/src/cloudflare-local.ts.hbs
  • packages/template-generator/templates/packages/env/src/server.ts.hbs
  • packages/template-generator/templates/packages/infra/alchemy.run.ts.hbs
💤 Files with no reviewable changes (3)
  • packages/template-generator/templates/packages/env/src/cloudflare-local.ts.hbs
  • packages/template-generator/src/template-handlers/packages.ts
  • packages/template-generator/src/processors/env-vars.ts

Comment thread apps/cli/test/post-installation.test.ts Resolved
Comment thread openspec/config.yaml Resolved
@coderabbitai

coderabbitai Bot commented Aug 10, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 54ac661c-f702-4282-b0c4-3610c30f0d56

📥 Commits

Reviewing files that changed from the base of the PR and between 34bdff9 and 1eb8295.

📒 Files selected for processing (2)
  • apps/cli/test/nx-generator.test.ts
  • packages/template-generator/src/processors/turbo-generator.ts

Walkthrough

The PR adds six OpenSpec workflow skills and formalizes Alchemy v2 Cloudflare deployment generation. It updates infrastructure resources, framework templates, D1 setup, dependency pins, post-install instructions, documentation, and CLI verification tests.

Changes

Alchemy Cloudflare deployment formalization

Layer / File(s) Summary
OpenSpec workflow skills
.codex/skills/openspec-*/SKILL.md
Adds workflows for exploring, proposing, applying, updating, synchronizing, and archiving OpenSpec changes.
Deployment contract and evidence model
openspec/config.yaml, openspec/changes/formalize-alchemy-cloudflare-deployment/*, docs/alchemy-v2-beta-findings.md
Defines exact Alchemy version pinning, supported Cloudflare topologies, compatibility safeguards, verification gates, cleanup rules, and upgrade evidence.
Alchemy resource generation
packages/template-generator/src/processors/alchemy-plugins.ts, packages/template-generator/templates/packages/infra/alchemy.run.ts.hbs
Replaces legacy Alchemy resources with Cloudflare D1, Worker, StaticSite, and Vite resources managed by an Effect-based Alchemy.Stack.
Template and dependency wiring
packages/template-generator/src/{post-process,processors,template-handlers,utils}/*, packages/template-generator/templates/**/*
Adds framework-specific Cloudflare configuration, D1 migration scripts, Prisma Workers WASM support, exact dependency pins, typed environment bindings, and updated deployment documentation.
CLI setup and deployment verification
apps/cli/src/**/*, apps/cli/test/*
Updates D1 database initialization, post-install command ordering, and Turbo task generation. Tests validate generated Cloudflare infrastructure, framework configuration, migrations, environment paths, ignore patterns, and interactive deployment tasks.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 11.76% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: migrating Cloudflare deployments from Alchemy v1 to Alchemy v2.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (2)
packages/template-generator/src/processors/alchemy-plugins.ts (1)

84-95: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Reuse the virtual filesystem JSON helpers.

Both blocks call JSON.parse directly on apps/web/package.json. VirtualFileSystem provides readJson and writeJson, which return undefined on invalid JSON instead of throwing. Using them removes the duplicated read/parse/serialize code and removes the unguarded parse.

Also applies to: 224-234

packages/template-generator/templates/packages/infra/alchemy.run.ts.hbs (1)

79-318: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚖️ Poor tradeoff

Consider extracting the repeated framework resource definitions.

Each framework resource is written twice: once at the top level for the backend=self path (Lines 79-318) and once inside Effect.gen for the web-only path (Lines 330-531). The cwd, command, memo, outdir, main, bundle, compatibility, and dev values are identical in both copies. A Handlebars partial per framework would keep the two paths in sync when a build path or compatibility flag changes.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 10166396-b084-4e10-8c26-a9c06963e8ae

📥 Commits

Reviewing files that changed from the base of the PR and between 89c03fb and 1a86ef7.

⛔ Files ignored due to path filters (1)
  • packages/template-generator/src/templates.generated.ts is excluded by !**/*.generated.*
📒 Files selected for processing (44)
  • .codex/skills/openspec-apply-change/SKILL.md
  • .codex/skills/openspec-archive-change/SKILL.md
  • .codex/skills/openspec-explore/SKILL.md
  • .codex/skills/openspec-propose/SKILL.md
  • .codex/skills/openspec-sync-specs/SKILL.md
  • .codex/skills/openspec-update-change/SKILL.md
  • apps/cli/src/helpers/core/post-installation.ts
  • apps/cli/src/helpers/database-providers/d1-setup.ts
  • apps/cli/src/utils/compatibility-rules.ts
  • apps/cli/test/addons.test.ts
  • apps/cli/test/cloudflare-db-clients.test.ts
  • apps/cli/test/database-setup.test.ts
  • apps/cli/test/deployment.test.ts
  • apps/cli/test/post-installation.test.ts
  • apps/cli/test/vite-plus-generator.test.ts
  • docs/alchemy-v2-beta-findings.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/.openspec.yaml
  • openspec/changes/formalize-alchemy-cloudflare-deployment/README.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/design.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/proposal.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/specs/alchemy-cloudflare-deployment/spec.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/tasks.md
  • openspec/config.yaml
  • packages/template-generator/src/post-process/package-configs.ts
  • packages/template-generator/src/processors/alchemy-plugins.ts
  • packages/template-generator/src/processors/deploy-deps.ts
  • packages/template-generator/src/processors/env-vars.ts
  • packages/template-generator/src/processors/infra-deps.ts
  • packages/template-generator/src/processors/readme-generator.ts
  • packages/template-generator/src/processors/workspace-deps.ts
  • packages/template-generator/src/template-handlers/packages.ts
  • packages/template-generator/src/utils/add-deps.ts
  • packages/template-generator/src/utils/generated-ignore-patterns.ts
  • packages/template-generator/templates/api/orpc/server/src/context.ts.hbs
  • packages/template-generator/templates/backend/server/base/tsdown.config.ts.hbs
  • packages/template-generator/templates/extras/env.d.ts.hbs
  • packages/template-generator/templates/frontend/astro/astro.config.mjs.hbs
  • packages/template-generator/templates/frontend/nuxt/nuxt.config.ts.hbs
  • packages/template-generator/templates/frontend/react/react-router/vite.config.ts.hbs
  • packages/template-generator/templates/frontend/react/tanstack-start/vite.config.ts.hbs
  • packages/template-generator/templates/frontend/svelte/svelte.config.js.hbs
  • packages/template-generator/templates/packages/env/src/cloudflare-local.ts.hbs
  • packages/template-generator/templates/packages/env/src/server.ts.hbs
  • packages/template-generator/templates/packages/infra/alchemy.run.ts.hbs
💤 Files with no reviewable changes (3)
  • packages/template-generator/src/template-handlers/packages.ts
  • packages/template-generator/templates/packages/env/src/cloudflare-local.ts.hbs
  • packages/template-generator/src/processors/env-vars.ts

Comment thread .codex/skills/openspec-explore/SKILL.md Resolved
Comment thread .codex/skills/openspec-propose/SKILL.md Resolved

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
.codex/skills/openspec-propose/SKILL.md (2)

4-4: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Replace unsupported tool calls in the Codex skill.

AskUserQuestion and TodoWrite are not Codex tools, and allowed-tools cannot authorize them. Replace these calls at lines 33-34, 60-63, and 89-91 with Codex-supported operations or runtime-neutral instructions.


25-25: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Pass --store only when a store is selected.

When no store is selected, omit --store from every affected command. Otherwise, the empty or undefined store ID overrides local root resolution and breaks the documented nearest-local-openspec/ behavior.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0640ce3f-4b3b-441b-8163-e20e9e680b5f

📥 Commits

Reviewing files that changed from the base of the PR and between 1a86ef7 and 55bcc11.

📒 Files selected for processing (7)
  • .codex/skills/openspec-apply-change/SKILL.md
  • .codex/skills/openspec-archive-change/SKILL.md
  • .codex/skills/openspec-explore/SKILL.md
  • .codex/skills/openspec-propose/SKILL.md
  • .codex/skills/openspec-sync-specs/SKILL.md
  • .codex/skills/openspec-update-change/SKILL.md
  • openspec/config.yaml
🚧 Files skipped from review as they are similar to previous changes (5)
  • .codex/skills/openspec-sync-specs/SKILL.md
  • .codex/skills/openspec-apply-change/SKILL.md
  • .codex/skills/openspec-explore/SKILL.md
  • .codex/skills/openspec-update-change/SKILL.md
  • .codex/skills/openspec-archive-change/SKILL.md

Comment thread .codex/skills/openspec-propose/SKILL.md Resolved

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)
.codex/skills/openspec-propose/SKILL.md (3)

85-88: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Align completion detection with the final status.

The loop stops when every artifact in applyRequires is done, but the output claims All artifacts created!. If other artifacts are not required by applyRequires, the skill can report an incomplete proposal as complete. Continue until every artifact is done, or report the remaining artifacts and state only that the change is apply-ready.

Also applies to: 101-106


44-45: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Make --store conditional.

If no store is selected, omit --store "<store-id>" from the commands in Steps 2–5. An explicit --store overrides nearest-root discovery and can prevent use of the local openspec/ root. Add the flag only after selecting a store with openspec store list --json.


41-48: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Check for an existing change before creating it.

Before openspec new change, run openspec list --json, adding --store "<store-id>" for store-scoped work. If the name exists, ask whether to continue it or choose a new name because duplicate names are rejected.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8938e6c8-6ba7-4afa-931f-fa1b278f8b58

📥 Commits

Reviewing files that changed from the base of the PR and between 7223bc5 and 34bdff9.

📒 Files selected for processing (3)
  • .codex/skills/openspec-propose/SKILL.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/design.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/tasks.md
🚧 Files skipped from review as they are similar to previous changes (2)
  • openspec/changes/formalize-alchemy-cloudflare-deployment/tasks.md
  • openspec/changes/formalize-alchemy-cloudflare-deployment/design.md

…Effects)

- rewrite packages/infra/alchemy.run.ts to the v2 Alchemy.Stack pattern:
  Website.Vite for SSR vite frameworks, StaticSite for nuxt/svelte/astro/
  next (OpenNext) and SPAs, Cloudflare.Worker for hono/elysia servers,
  Config.string/redacted for env, InferEnv-based typing via ServerEnv/WebEnv
- pin alchemy 2.0.0-beta.61 + effect 4.0.0-beta.94 exactly (caret ranges
  resolve to a broken npm prerelease tag under bun)
- drop the v1 alchemy/cloudflare/* plugin injection machinery and the
  cloudflare-local.ts shim; set framework adapters statically instead
- react-router: generate workers/app.ts, edge entry.server.tsx, and the
  ssr rollup input wiring (RR8 server-build has no default export)
- next: generate wrangler.jsonc + build:cloudflare script for OpenNext
- astro: dist/server entry + dist/client assets + SESSION KV binding
- svelte: bundle the adapter _worker.js shim; workerd-safe env layer
- workarounds for upstream beta.61 bugs, documented with repros in
  https://github.com/AmanVarshney01/alchemy-v2-beta-repros

Verified: 20,736-combo matrix sweep (8,436 valid, 892 unique infra
renderings, all typecheck clean against the published beta), live smoke
deploys of all 8 framework paths on Cloudflare (7/8 served 200; next
build verified, upload needs paid plan for >3MiB workers), and alchemy
dev for both the StaticSite and Website.Vite loops.
…local D1 dev, svelte asset hygiene

- nuxt/tanstack-start + self: externalize cloudflare:workers in node builds
  (nitro prerender dropped for self — it executes worker-only code in node)
- local D1 for fullstack StaticSite frameworks: apps/web/wrangler.jsonc with
  a d1_databases binding + db:migrate:local scripts; next uses the existing
  initOpenNextCloudflareForDev, nuxt gains nitro-cloudflare-dev, svelte/astro
  adapters read the config natively (all four verified with live sign-up
  writes through framework dev servers)
- svelte: ship static/.assetsignore so _worker.js/_routes.json stay out of
  the public asset upload
- react-router: clerk worker credentials (CLERK_SECRET_KEY +
  VITE_CLERK_PUBLISHABLE_KEY) and isbot-aware entry.server
- opennext wrangler config: compatibility_date 2025-05-05 +
  global_fetch_strictly_public
- README: correct staged-deploy default (dev_$USER) with explicit
  production command; drop stale v1 guide link; local D1 migration note
… astro images

- fix TS2345 in the three new frontend-array checks (as const); template
  generator typecheck is clean again
- root db:migrate:local now filters the actual workspace name (web)
- nuxt + self dev: page SSR runs under vite-node, which cannot resolve
  cloudflare:workers — alias it in $development to a getPlatformProxy
  shim (same miniflare state as nitro-cloudflare-dev); verified / and a
  sign-up write both 200 in dev
- prisma + d1: local wrangler config gains migrations_pattern for
  prisma's nested <timestamp>_<name>/migration.sql layout
- astro: bind IMAGES (adapter v14 defaults to the cloudflare-binding
  image service) alongside SESSION
- opennext: global_fetch_strictly_public now set on the deployed worker
  (infra compatibility flags), not just the build-time wrangler config
- orpc context: fix pre-existing ReferenceError for auth=none +
  cloudflare (destructured _env, returned env)
- README/post-install: local D1 migration step ordered after generate

This branch was successfully deployed

1 active deployment
Preview — 5963f141 Deployed Aug 12, 2026 by vercel[bot]
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